[collectd] Unable to SNMP collect two-dimensional(?) table

[Bill Schwanitz]

On Oct 15, 2012, at 5:32 AM, Stian Øvrevåge <sovrevage at gmail.com> wrote:

> The data is stored in 4 OID's, low and high minor and major values
> with indexes 1 through 4 for each sensor.
> 
> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1067.1 = INTEGER: 900
> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1067.2 = INTEGER: 800
> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1067.3 = INTEGER: 40
> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1067.4 = INTEGER: 20
> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1068.1 = INTEGER: -60
> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1068.2 = INTEGER: -70
> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1068.3 = INTEGER: -150
> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1068.4 = INTEGER: -160

That is kind of odd with the extra .1-4 etc in the oid. What product is this from? I'm monitoring Catalyst and Nexus gear and I don't recall seeing this.

Here is the config I'm using today though looking at your snmpwalk output I'm not sure it'll help

  <Data "CISCO-ENTITY-SENSOR-MIB">
    Type "temperature"
    Table true
    #Instance ".1.3.6.1.2.1.47.1.1.1.1.2"
    Instance "ENTITY-MIB::entPhysicalDescr"
    #Values ".1.3.6.1.4.1.9.9.91.1.1.1.1.4"
    Values "CISCO-ENTITY-SENSOR-MIB::entSensorValue"
  </Data>

$ snmpwalk -v2c -c foo foo CISCO-ENTITY-SENSOR-MIB::entSensorValue
CISCO-ENTITY-SENSOR-MIB::entSensorValue.21590 = INTEGER: 27
CISCO-ENTITY-SENSOR-MIB::entSensorValue.21591 = INTEGER: 27
CISCO-ENTITY-SENSOR-MIB::entSensorValue.21592 = INTEGER: 15
CISCO-ENTITY-SENSOR-MIB::entSensorValue.21593 = INTEGER: 15
CISCO-ENTITY-SENSOR-MIB::entSensorValue.21594 = INTEGER: 15
CISCO-ENTITY-SENSOR-MIB::entSensorValue.21595 = INTEGER: 15
CISCO-ENTITY-SENSOR-MIB::entSensorValue.21596 = INTEGER: 23
CISCO-ENTITY-SENSOR-MIB::entSensorValue.21597 = INTEGER: 21
CISCO-ENTITY-SENSOR-MIB::entSensorValue.101021590 = INTEGER: 27
CISCO-ENTITY-SENSOR-MIB::entSensorValue.101021593 = INTEGER: 45
CISCO-ENTITY-SENSOR-MIB::entSensorValue.102021590 = INTEGER: 26
CISCO-ENTITY-SENSOR-MIB::entSensorValue.102021593 = INTEGER: 40
CISCO-ENTITY-SENSOR-MIB::entSensorValue.103021590 = INTEGER: 25
CISCO-ENTITY-SENSOR-MIB::entSensorValue.103021593 = INTEGER: 38
CISCO-ENTITY-SENSOR-MIB::entSensorValue.104021590 = INTEGER: 23
CISCO-ENTITY-SENSOR-MIB::entSensorValue.104021593 = INTEGER: 37

$ snmpwalk -v2c -c foo foo ENTITY-MIB::entPhysicalDescr
ENTITY-MIB::entPhysicalDescr.21590 = STRING: Module-1, Outlet-1
ENTITY-MIB::entPhysicalDescr.21591 = STRING: Module-1, Outlet-2
ENTITY-MIB::entPhysicalDescr.21592 = STRING: Module-1, Intake-1
ENTITY-MIB::entPhysicalDescr.21593 = STRING: Module-1, Intake-2
ENTITY-MIB::entPhysicalDescr.21594 = STRING: Module-1, Intake-3
ENTITY-MIB::entPhysicalDescr.21595 = STRING: Module-1, Intake-4
ENTITY-MIB::entPhysicalDescr.21596 = STRING: PowerSupply-1 Sensor-1

ENTITY-MIB::entPhysicalDescr.21597 = STRING: PowerSupply-2 Sensor-1

( Yes, those are new-lines from the sensor value! )

$ snmpwalk -v2c -c foo foo ENTITY-MIB::entPhysicalDescr | grep 10102159
ENTITY-MIB::entPhysicalDescr.101021590 = STRING: Fex-101 Module-1 Outlet-1
ENTITY-MIB::entPhysicalDescr.101021593 = STRING: Fex-101 Module-1 Die-1

Notice the funky numbering on the instance - thats some goofy stuff they are doing in the nexus but the description and value always line up which does not appear to be your case…

What does your config look like. I assume the sensor values you posted were from snmpwalk yes?

Bill