David,
I suggest you turn on tracing of snmpCollect with the -T switch if you do
not already have it on, and then look at the trace file snmpCol.trace,
which is in /usr/OV/log. Check what happens as you increase the number of
collection instances.
snmpCollect parameters are documented in the man page which is in
/usr/OV/man/man8. I had a quick look at a Solaris system here and it seems
to me the NetView environment script does not get the path right for the
man pages.
At 08:53 AM 11-01-05 +0000, Liu, David wrote:
Hi list,
I've been reading nv-l archives for quite some times and benefit from them.
Now I post my first question to get your advice/help.
We are collecting quite a lot data every 15 mins (supposed to), but till now
only part of the collection happened (everyday less than half i.e. 40
collections per definition per device, sometimes even null). My basic
question is: can NV handle that many collections? Because when I suspended
more than half of the collections (interface data). It seemed working fine.
If yes, how can I tune the NV? Where can I find the document for the tuning
(snmpCollect daemon settings)?
Here's some basic info.
NV 7.1.2 on Solaris 2.8.
Data collection of about 600 devices with
1) SysUptime for all of them
2) cpmCPUTotal5min for 400 devices (cisco)
3) ciscoMemoryPoolUsed for 400 devices
4) ciscoMemoryPoolFree for 400 devices
5) ifInUcastPkts, ifOutUcastPkts, ifInErrors, ifOutErrors, ifAdminStatus,
ifOperStatus, ifLastChange, ifInOctets, ifOutOctets, ifInDiscards,
ifOutDiscards, ifInNUcastPkts, ifOutNUcastPkts for about 200 devices with
lot of interfaces
6) Some latency data for 10 routers
Our current snmpCollect (daemon) settings:
Defer time: 60
Max PDU: 50
Config check interval: 1440
Max concurrent SNMP sessions: 50
Verbose trace mode : Yes
Polling interval for nvcold: 60
Thank you in advance.
Regards,
David
Joe Fernandez
Kardinia Software
jfernand@kardinia.com
http://www.kardinia.com
|