RE: [nv-l] Windows Clusters

I am assuming the issue is you have is that SNMP discovery finds the second non-pingable interface. What is probably happening is you have more than one server with the 192 address (based on my experience it is 192.168.254.253 -seems to pop up a lot). You unmanage the interface on one box and when a second box is discovered also with the 192,168 interface it deletes the first one. The config polls suddenly find it again and delete it from the second box and add it to hte first box again - in a managed state not unmanaged.

I would recommend two things - first use SNMP polling not ping polling. This way, the status of the second interface can be obtained. Second, force your server administrators to put a different address on each of servers that have one of these interfaces. I am struggling with the same thing here with our Dell servers.

-----Original Message-----
From: owner-nv-l-digest AT lists.us.ibm DOT com [mailto:owner-nv-l-digest AT lists.us.ibm DOT com]On Behalf Of CMazon AT commercebankfl DOT com
Sent: Thursday, October 23, 2003 10:42 AM
To: nv-l AT lists.us.ibm DOT com
Subject: [nv-l] Windows Clusters

Win2k/Netview 7.1.3. FP1 / SQL2000,

Hi list,

Maybe someone can shed some light for me. We have 3 Microsoft clusters with several nic cards. One nic in each server is configured with an ip that are not pingable (192.168.X.X) for the cluster heartbeat. Is there a way to prevent Netview from discovering these interfaces? I have them in the exclude list of the seed file and I tried to unmanage them, but somehow Netview continues to manage these interfaces on its own.

Has anyone come accross this problem before?

Also, is there any consultant on this list located in Miami, FL please email me directly. (Sorry for posting this here.)

Carlos