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
mfreeman@netcogov.com
--