Hi Mortan
I have made the patch to TwistedSNMP library but i still receiving the timeout.
Increasing the verbosity of the logs i receive:
2011-07-27 12:56:31,538 [DEBUG jobs.jobhandler] [profiling SWITCH] Job 'profiling' initialized with plugins: ['oidprofiler'] 2011-07-27 12:56:31,538 [DEBUG jobs.jobhandler] [profiling SWITCH] AgentProxy created for SWITCH: AgentProxy(SWITCH_IP,161,community,v2c,<twistedsnmp.snmpprotocol.SNMPProtoco l instance at 0xa9c760c>) 2011-07-27 12:56:31,539 [DEBUG jobs.jobhandler] [profiling SWITCH] Plugin oidprofiler wouldn't handle SWITCH 2011-07-27 12:56:31,539 [DEBUG jobs.jobhandler] [profiling SWITCH] No plugins for this job 2011-07-27 12:56:31,539 [INFO schedule.netboxjobscheduler] [profiling SWITCH] Next 'profiling' job for SWITCH will be in 299 seconds (2011-07-27 13:01:31.539127)
Apparently the oidprofiler not recognize the router OID.
-----Original Message----- From: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sent: quarta-feira, 27 de Julho de 2011 08:08 To: Duarte Franco Cc: nav-users@itea.ntnu.no Subject: Re: Switch information Nortel Networks Layer 2-3 GBE Switch Module(Copper)
On Tue, 26 Jul 2011 11:15:18 +0000 (UTC) Duarte Franco duarte.franco@fccn.pt wrote:
Hi Mortan
Im running version 3.8.6
In the ipdevpoll.log i only have this error:
[ERROR jobs.jobhandler] [inventory se03bc05sw02.priv.fccn.pt] Job
'inventory'
for se03bc05sw02.priv.fccn.pt aborted: SNMP request timed out
But the switch respond to snmp querys perfectly from the console:
There a are a few known issues with SNMP timeouts when using ipdevpoll:
1. Your device may be slow at generating responses for GetBulk requests. This has at least been demonstrated to be problem with some devices from other vendors.
2. You may want to patch your TwistedSNMP library as described in NAV's NOTES file. We submitted a patch to TwistedSNMP to fix a problem with the timeout not increasing as it should between retries, but we've never received a response. The patch can be found in NAV's contrib directory.
If you've applied the patch and are still getting timeouts, you can set up some more logging in ipdevpoll so we can at least see which plugin times out. Create a file in NAV's config directory called `logging.conf`, and add the following three lines:
[levels] nav.ipdevpoll = INFO nav.ipdevpoll.jobs.jobhandler = DEBUG
-- Morten Brekkevold UNINETT