Hi!
Is Dlink DGS-3100 / DGS-3120 supported by NAV? If yes, why these errors are ocurring with ipdevpoll module?
2013-03-19 19:52:09,257 [WARNING plugins.typeoid.typeoid] [inventory 10.10.25.110] Netbox has changed type from unknown to unknown (sysObjectID 1.3.6.1.4.1.171.10.94.3) 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('',))
Is there a way to put ipdevpoll module in debug mode to see what is happening with more details?
The device is correctly configured with snmpv2c. See it:
# snmpwalk -v2c -c public 10.10.25.110 .1.3.6.1.2.1.2.2.1.2.40 iso.3.6.1.2.1.2.2.1.2.40 = STRING: "Ethernet Interface"
That command was executed from the same VM that NAV is installed.
I have another two monitored devices: Dlink DES-3028P and Dlink DES-3526. These two are correctly functional in NAV and those snmp configurations are set in the same way of Dlink DGS-3100.
Information about versions:
*NAV SERVER:*
root@nav:~# /usr/lib/nav/ipdevpolld --version NAV 3.13.1
root@nav:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 6.0.7 (squeeze) Release: 6.0.7 Codename: squeeze
*DEVICE:*
Device Type : DGS-3100-48 Gigabit stackable L2 Managed Switch MAC Address : f0:7d:68:b5:58:77 IP Address : 10.10.25.110 VLAN Name : v25Manager Subnet Mask : 255.255.255.0 Default Gateway : 10.10.25.1 Boot PROM Version : 1.0.1.05 Firmware Version : 3.60.28 Hardware Version : a2 Serial Number : F3XT1A7000009(unit 1) F3XT1A7000008(unit 2) F3XU1AC000016(unit 3) System Name : [110-4] System Location : System Contact : System Up Time : 56 days 7 hours 5 mins 47 seconds Spanning Tree : Enabled GVRP : Disabled IGMP Snooping : Enabled TELNET : Disabled WEB : Disabled
2013/3/19 Bruno Galindro da Costa bruno.galindro@gmail.com
Hi!
Is Dlink DGS-3100 / DGS-3120 supported by NAV? If yes, why these errors are ocurring with ipdevpoll module?
2013-03-19 19:52:09,257 [WARNING plugins.typeoid.typeoid] [inventory 10.10.25.110] Netbox has changed type from unknown to unknown (sysObjectID 1.3.6.1.4.1.171.10.94.3) 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('',))
Is there a way to put ipdevpoll module in debug mode to see what is happening with more details?
The device is correctly configured with snmpv2c. See it:
# snmpwalk -v2c -c public 10.10.25.110 .1.3.6.1.2.1.2.2.1.2.40 iso.3.6.1.2.1.2.2.1.2.40 = STRING: "Ethernet Interface"
That command was executed from the same VM that NAV is installed.
I have another two monitored devices: Dlink DES-3028P and Dlink DES-3526. These two are correctly functional in NAV and those snmp configurations are set in the same way of Dlink DGS-3100.
-- Att. Bruno Galindro da Costa
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`.
That's it! Worked!
For who that whant to know how snmp get-bulk works (max-repetitions), please read this:
http://docstore.mik.ua/orelly/networking_2ndEd/snmp/ch02_06.htm
max-repetitions ins't a exclusive parameter from NAV, but, a PDU's field.
2013/3/20 Morten Brekkevold morten.brekkevold@uninett.no
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
On Wed, 20 Mar 2013 11:23:53 -0300 Bruno Galindro da Costa bruno.galindro@gmail.com wrote:
That's it! Worked!
For who that whant to know how snmp get-bulk works (max-repetitions), please read this:
http://docstore.mik.ua/orelly/networking_2ndEd/snmp/ch02_06.htm
max-repetitions ins't a exclusive parameter from NAV, but, a PDU's field.
Correct. For that matter, I've even seen devices that will talk SNMP v2c, but _NOT_ respond at all to GET-BULK queries. That's just insane.
Glad you got it working! :)