RE: [nv-l] Failed ping stays green

["Zoeckler, Eric A." <Eric.Zoeckler@us.ngrid.com>]

Stephen,

Agreed, the two boxes are out of sync with regard to polling.  I was under the impression that when pinging a device from netview in which this device is known to be down, netview would make a status change to that node.  I'm sure I've seen this.  But, if I'm understanding you correctly, you're saying that it would require a demand poll and not a ping to simulate the scheduled polling action and thus invoke a status change to the node?  Analysis of my problem has ended as the node came back up on the network.  I have since removed and readded it to netview.

Thank you much for your input.

Eric

---------------------------------
Eric Zoeckler, IT Analyst, DCO/NCC
Niagara Mohawk-National Grid USA
Phone:  315-460-2519
Eric.Zoeckler@us.ngrid.com

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Stephen Hochstetler
Sent: Wednesday, May 18, 2005 6:12 PM
To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] Failed ping stays green

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.

Stephen Hochstetler shochste@us.ibm.com
International Technical Support Organization at IBM
Office - 512-838-6198 (t/l 678) FAX - 512-838-6931
http://www.redbooks.ibm.com

This e-mail and any files transmitted with it, are confidential to National Grid and are intended solely for the use of the individual or entity to whom they are addressed.  If you have received this e-mail in error, please reply to this message and let the sender know.