On Tue, 19 Mar 2013 16:24:56 -0300 Bruno Galindro da Costa <bruno.galindro@gmail.com> wrote:

>    Is Dlink DGS-3100 / DGS-3120 supported by NAV? If yes, why these errors
> are ocurring with ipdevpoll module?

Hello Bruno,

I have no experience with these devices; they should be supported as
long as they implement the proper IETF SNMP MIBs.

> 2013-03-19 19:52:30,376 [ERROR jobs.jobhandler] [inventory 10.10.25.110
> Job 'inventory' for 10.10.25.110 aborted: ('Job aborted due to plugin
> failure', TimeoutError('',))
> 2013-03-19 19:54:49,507 [ERROR jobs.jobhandler] [linkcheck 10.10.25.110]
> Job 'linkcheck' for 10.10.25.110 aborted: ('Job aborted due to plugin
> failure', TimeoutError('',))

These are timeout errors, i.e. the device didn't respond to SNMP
requests within the configured timeout value. They do not indicate lack
of support.

>    Is there a way to put ipdevpoll module in debug mode to see what is
> happening with more details?

Yes. Unless you have already been adjusting log levels in
`/etc/nav/logging.conf`, create that file (it doesn't come with NAV) and
add the following three lines:

[levels]
nav.ipdevpoll = INFO
nav.ipdevpoll.jobs.jobhandler = DEBUG

You can manually run e.g. the inventory job for the device in question
by running (preferably prefixed with a `sudo -u navcron`):

  /usr/lib/nav/ipdevpolld -J inventory -n 10.10.25.110

Running a single job like this will also log directly to the terminal.

This will at the very least identify which plugin timed out. The next
maintenance release will log the plugin name in the error so you won't
have to adjust the log levels down.


Some devices are just too slow to respond within the default timeout of
1.5 seconds. Some devices are slow at building responses for bulk
queries (SNMP GETBULK commands), and you might have to reduce the number
of max-repetitions used for bulk requests. Both of these settings can be
adjusted in `ipdevpoll.conf`.


--
Morten Brekkevold
UNINETT