To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | RE: [nv-l] Failed ping stays green |
From: | Stephen Hochstetler <shochste@us.ibm.com> |
Date: | Wed, 18 May 2005 17:11:43 -0500 |
Delivery-date: | Wed, 18 May 2005 23:12:11 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <1AED1BD3D4BD804A8245B80EF9A9C25F02AABE4D@ex2k.bankofamerica.com> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
In the past when a particular interface is green on one server, and red on another, it is due to the timing of the polling intervals. Pinging a down device will not get NetView that it is down. If your polling is 5 minute cycles, then within 5 minutes both of your servers should agree. To speed that up, you can go to the server with the green icon and do a NetView demand poll that just checks status of all the interfaces on that device. You should then see the interface icon go red if it is unavailable. |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] Failed ping stays green, Stringfellow, William |
---|---|
Next by Date: | RE: [nv-l] Web Console, Glen Warn |
Previous by Thread: | RE: [nv-l] Failed ping stays green, Stringfellow, William |
Next by Thread: | RE: [nv-l] Failed ping stays green, Zoeckler, Eric A. |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web