Hi,
I'm actually hitting this problém with slow answering devices. Unfortunately they form the backbone...
I'm trying these new settings and I will see if it helped: max_concurrent_jobs = 300 timeout = 20 max-repetitions = 5
and topology job scheduled only once an hour: [job_topo] interval: 60m plugins: cam lldp cdp description: The topo job collects data necessary for detecting the network topology, like switch forwarding tables (CAM) and LLDP and CDP neighboring data
I will let you know, if it helped.
Brgds
Mat
-----Original Message----- From: nav-users-request@uninett.no [mailto:nav-users-request@uninett.no] On Behalf Of Morten Brekkevold Sent: Wednesday, April 02, 2014 9:34 AM To: JABUREK Martin Cc: nav-users@uninett.no Subject: Re: Problem retrieving port statistics
On Fri, 28 Mar 2014 12:38:18 +0000 "Martin.Jaburek@cah.cz" Martin.Jaburek@cah.cz wrote:
Gaps are only in port metrics graphs - they are at exactly the same time on all ports on given device.
Systém metrics are just fine on this device.
I checked the 5min graph of ipdevpoll systém metrics and it shows 100 at peak times, what I assume are only nearly 2 minutes.
The gaps in your graphs appear to happen every 6 hours, which seems to correlate with the inventory job interval. You might want to check your ipdevpoll.log for timeout errors.
You may do well to adjust the SNMP parameters in ipdevpoll.conf. On several installations, we've experienced that the default timeout is too low and the default max-repetitions value is too high (some devices tend to freak out and slow down when they get a GET-BULK request for 50 values). Often, we end up setting max-repetitions at or below 10.
You could also reduce the max_concurrent_jobs option, so ipdevpoll won't try to talk to all your devices at the exact same time.
Since then I can also see attached errors. They were not there when I was on version 4.0b5.
It happens only on cisco catalyst 4500/6500 and one type of 3560E. (I have many 3750 but, there is no problém at all) and causes inventory jobs to fail.
[snip]
File "/usr/local/nav/lib/python/nav/mibs/entity_mib.py", line 163, in get_chassis if self.is_chassis(entity)] File "/usr/local/nav/lib/python/nav/mibs/entity_mib.py", line 125, in is_chassis return e['entPhysicalClass'] == 'chassis' exceptions.KeyError: 'entPhysicalClass'
It's this bug: https://bugs.launchpad.net/nav/+bug/1300117
The fix has been patched into the Debian packages already, but this is serious enough to warrant new official releases tomorrow.
-- Morten Brekkevold UNINETT