SNMP fails while accessing a Dell/Avocent 2161DS KVM Device

Description

(FW version for the KVM: 2161DS 03.01.00)

Hello,

All I can get to prove a DELL/Avocent KVM is a "timeout" regardless of the time I give it to complete. SNMP-walking the whole set (on 1.6.3.1.2.1 for example) takes a fraction of a second by hand.

All I can see in the logs (including turning to DEBUG output) is:

Timeout retrieving SnmpCollectors for X.X.X.X

The firmware is rather old. The traps are working correctly, I just can't collect in read-mode. Is this device famously failing to implement a standard SNMP agent?

Regards,
Julien

Environment

Operating System: Windows Vista / 2008 Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Julien Wilk November 3, 2010 at 12:21 AM

Found the problem... This KVM seems to refuse SNMPv2 commands.

I modified snmp-config.xml to force a downgrade to SNMPv1 for this single IP and it resumed working normally.

Hope this will help someone else!

$ snmpwalk -c [...] -v 2c [...] system
Timeout: No Response from flow-eqx-kvm1

$ snmpwalk -c [...] -v 1 [...] system
SNMPv2-MIB::sysDescr.0 = STRING: 2161DS 03.01.00
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.10418.3.1.8
SNMPv2-MIB::sysUpTime.0 = Timeticks: (62408100) 7 days, 5:21:21.00
SNMPv2-MIB::sysContact.0 = STRING: xxx
SNMPv2-MIB::sysName.0 = STRING: xxx
SNMPv2-MIB::sysLocation.0 = STRING:
SNMPv2-MIB::sysServices.0 = INTEGER: 72

Julien Wilk October 29, 2010 at 7:04 PM

Took me a little while to get net-snmp to compile snmpwalk on Cygwin but I got it.

> snmpwalk -c [comm] -v 2c [target] system
Timeout: No Response from [target]

Using SNMPUTIL.exe

Variable = system.sysDescr.0
Value = String 2161DS 03.01.00

Variable = system.sysObjectID.0
Value = ObjectID 1.3.6.1.4.1.10418.3.1.8

Variable = system.sysUpTime.0
Value = TimeTicks 26026100

Variable = system.sysContact.0
Value = String [...]

Variable = system.sysName.0
Value = String [...]

Variable = system.sysLocation.0
Value = String [...]

Variable = system.sysServices.0
Value = Integer32 72

David Hustace October 29, 2010 at 8:04 AM

Can you walk the system, interfaces, ifx, and ip tables independently?

snmpwalk -c public -v 2c <hostname> system
snmpwalk -c public -v 2c <hostname> interfaces
snmpwalk -c public -v 2c <hostname> ip
snmpwalk -c public -v 2c <hostname> ifx

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created October 28, 2010 at 1:34 AM
Updated January 27, 2017 at 4:20 PM
Resolved November 3, 2010 at 12:21 AM