Hey, Paul; Welcome Newcomer. We need to know what you're running since
there are various flavors of NetView and they vary in performance
depending on the underlying hardware and operating system.
I've usually found the default is well configured if you have sized and
configured the system according to the suggestions in the NetView books.
For Windows it's a twenty minute polling cycle and for Unix/Linux it's a
five minute default polling cycle. Performance can be affected by a
number of other configuration variables as well as the total load in
terms of objects.
In particular the number of devices shown by the "ovobjprint -S" and the
number shown for the "-n" value on the ovwdb line in the
/usr/OV/conf/ovsuf line are critical (Unix/Linux file notation). The -n
value MUST be a good percentage bigger. If NETMON (the poller) is so
heavily loaded you can't sneak in a demand poll there's something out of
kilter in the configuration and the ovwdb -n value is the usual first
suspect.
Bill Evans
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]
On Behalf Of Skokan, Paul
Sent: Monday, June 05, 2006 2:46 PM
To: nv-l@lists.us.ibm.com
Subject: [nv-l] Polling Question
I am fairly new to Netview and I need some advice on polling so that my
server can accomodate the # of devices I am monitoring...
I am primarly monitoring network devices (routers, switches, wireless,
etc). The workload on the poller is heavily loaded at all times and it
is preventing me to do demand polls efficiently when troubleshooting
problems. What is the best way to control the polling and SNMPcollect
scripts so that I can effectively monitor all devices at various levels?
Paul
|