[Top] [All Lists]

RE: [nv-l] Polling Question

To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] Polling Question
From: Stephen Hochstetler <shochste@us.ibm.com>
Date: Mon, 5 Jun 2006 17:17:36 -0500
Delivery-date: Mon, 05 Jun 2006 23:18:30 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <OF4A182AD1.8B2B9B3D-ON85257184.00741E30-85257184.0076B1D2@us.ibm.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

I am wondering about this "managing" 900 items and having 24K items in the database. Is this really true? Does those 900 network devices translate to 6000 interfaces? I always thought that I got about 4 objects per interface I was managing.

A demandpoll is handled via SNMP. Do you have SNMP polling as the default? Do you have to? It is 'lighter' to both the network and also the NetView server if you are using ICMP for polling. Then for devices that really need SNMP polling to move those to that type of polling. This would relieve the SNMP workload that netmon is currently doing and potentially let it respond to a demandpoll request quicker.

Question -- do you have some nodes that respond slowly? Netmon will only send out so many 'snmp' requests and wait for responses before continuing. The symptoms of this is the SNMP queue in netmon gets backed up but the CPU usage of the NetView server decreases. This is best looked by by running a netmon trace into a large file, then analyzing it later. The slow response can be either due to network latency, or a slowly responding router. At the routers, if they are running high CPU it will cause a very slow SNMP response because SNMP gets a very low priority within the router. To these devices doing 'ping' polling can make a huge difference to NetView.

Stephen Hochstetler shochste@us.ibm.com
International Technical Support Organization at IBM
Office - 512-838-6198 (t/l 678) FAX - 512-838-6931

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

Archive operated by Skills 1st Ltd

See also: The NetView Web