|Subject:||Re: [nv-l] Pinging a device to add it to the map|
|From:||James Shanks <email@example.com>|
|Date:||Wed, 3 Dec 2003 17:46:29 -0500|
|Delivery-date:||Wed, 03 Dec 2003 22:54:41 +0000|
Right. netmon is a complex animal and I cannot explain how he works in detail but suffice it to say that netmon is listening for unexpected ping responses. Those are ones that are going back to you, not ones that netmon is waiting for.
When he sees one of yours, he puts it on his list of nodes to check. When he gets around to that, activity, if the node isn't in the database, netmon will try to contact it by SNMP as well as by ping (one he sends), and if he is successful, then he'll add the node and you see it pop up
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
oddly it seems though now that i have taken care of my timing issue on the ping timeouts, It it picking up devices where it was not able to before. Discovery is moving much quicker now.
and it does seem though that right after I ping a device from the Netview box I can see in the event log that the deivce I just ping'd was added to netview.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [nv-l] loadhost not working, James Shanks|
|Next by Date:||Re: [nv-l] Netmon on NT, James Shanks|
|Previous by Thread:||Re: [nv-l] Pinging a device to add it to the map, Christopher J Petrina|
|Next by Thread:||Re: [nv-l] Pinging a device to add it to the map, Christopher J Petrina|
|Indexes:||[Date] [Thread] [Top] [All Lists]|
Archive operated by Skills 1st Ltd
See also: The NetView Web