nv-l
[Top] [All Lists]

[nv-l] NV tuning for Data collection

To: "'nv-l@lists.tivoli.com'" <nv-l@lists.tivoli.com>
Subject: [nv-l] NV tuning for Data collection
From: "Liu, David" <david.liu@eds.com>
Date: Tue, 11 Jan 2005 08:53:40 -0000
Delivery-date: Tue, 11 Jan 2005 08:54:45 +0000
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
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



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

Archive operated by Skills 1st Ltd

See also: The NetView Web