To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | [nv-l] Windows Clusters |
From: | CMazon@commercebankfl.com |
Date: | Thu, 23 Oct 2003 11:42:25 -0400 |
Delivery-date: | Thu, 23 Oct 2003 16:56:37 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l-digest@lists.us.ibm.com |
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 |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [nv-l] Authentication Failure Trap Argument interpretation, Joe Fernandez |
---|---|
Next by Date: | [nv-l] mib2trap utility, Brian Kraftchick |
Previous by Thread: | [nv-l] Mike Walsh/US/AMERICAS is out of the office., Mike Walsh |
Next by Thread: | Re: [nv-l] Windows Clusters, Paul |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web