[Top] [All Lists]

[nv-l] how does netmon interact with the ARP cache?

To: <nv-l@lists.us.ibm.com>
Subject: [nv-l] how does netmon interact with the ARP cache?
From: "Freeman, Michael" <mfreeman@netcogov.com>
Date: Thu, 7 Oct 2004 12:25:05 -0500
Delivery-date: Thu, 07 Oct 2004 18:36:22 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Thread-index: AcSskpldVTUlm4JuQ1WPInztROJaBQ==
Thread-topic: how does netmon interact with the ARP cache?

I have noticed that if a device goes down, and then comes back up before netmon “magically notices it”, if you ping the device, the object status will change in NetView. I assume this is because NetView is somehow monitoring the arp tables? We are using NetView 7.1.3 on Solaris and I am kind of curious to know how netmon and the arp cache works. It seemed like in my tests with my network simulator, If I took down 200 nodes, and then brought them up before netmon’s polling cycle kicked in, that if I pinged every one of them (with a script of course), about only 10 or so nodes would immediately have their object status changed in NetView. How does netmon divvy up the workload? Helper threads? Timeslicing ?


*** Note new e-mail address


Michael J. Freeman

Netco Government Services




<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web