Stian,<br> Octo has been working on a patch that he wrote for the SNMP plugin that I believe will fix this. I ran into the same issue anytime I was trying to collect SNMP data from dynamically created MIB entries. The SNMP plugin expects MIBs to increment sequentially at the last "octet" of data. This isn't always the case with tables - especially when the table entry itself may contain other table entries. His patch fixes this.<br>
<br>Mark<br><br><div class="gmail_quote">On Mon, Oct 15, 2012 at 11:45 AM, Stian Øvrevåge <span dir="ltr"><<a href="mailto:sovrevage@gmail.com" target="_blank">sovrevage@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thank you Bill, but notice that I'm not trying to collect the actual<br>
sensor data (I'm doing that without problems) but the threshold values<br>
for the various sensors, hence the 1-4 index.<br>
<br>
The equipment is mainly Cisco ME3400 switches.<br>
<br>
Brgds,<br>
Stian Øvrevåge<br>
<div class="HOEnZb"><div class="h5"><br>
On Mon, Oct 15, 2012 at 1:17 PM, Bill Schwanitz <<a href="mailto:bilsch@gmail.com">bilsch@gmail.com</a>> wrote:<br>
><br>
> On Oct 15, 2012, at 5:32 AM, Stian Øvrevåge <<a href="mailto:sovrevage@gmail.com">sovrevage@gmail.com</a>> wrote:<br>
><br>
>> The data is stored in 4 OID's, low and high minor and major values<br>
>> with indexes 1 through 4 for each sensor.<br>
>><br>
>> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1067.1 = INTEGER: 900<br>
>> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1067.2 = INTEGER: 800<br>
>> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1067.3 = INTEGER: 40<br>
>> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1067.4 = INTEGER: 20<br>
>> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1068.1 = INTEGER: -60<br>
>> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1068.2 = INTEGER: -70<br>
>> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1068.3 = INTEGER: -150<br>
>> CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1068.4 = INTEGER: -160<br>
><br>
> 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.<br>
><br>
> Here is the config I'm using today though looking at your snmpwalk output I'm not sure it'll help<br>
><br>
> <Data "CISCO-ENTITY-SENSOR-MIB"><br>
> Type "temperature"<br>
> Table true<br>
> #Instance ".1.3.6.1.2.1.47.1.1.1.1.2"<br>
> Instance "ENTITY-MIB::entPhysicalDescr"<br>
> #Values ".1.3.6.1.4.1.9.9.91.1.1.1.1.4"<br>
> Values "CISCO-ENTITY-SENSOR-MIB::entSensorValue"<br>
> </Data><br>
><br>
> $ snmpwalk -v2c -c foo foo CISCO-ENTITY-SENSOR-MIB::entSensorValue<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.21590 = INTEGER: 27<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.21591 = INTEGER: 27<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.21592 = INTEGER: 15<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.21593 = INTEGER: 15<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.21594 = INTEGER: 15<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.21595 = INTEGER: 15<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.21596 = INTEGER: 23<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.21597 = INTEGER: 21<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.101021590 = INTEGER: 27<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.101021593 = INTEGER: 45<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.102021590 = INTEGER: 26<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.102021593 = INTEGER: 40<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.103021590 = INTEGER: 25<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.103021593 = INTEGER: 38<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.104021590 = INTEGER: 23<br>
> CISCO-ENTITY-SENSOR-MIB::entSensorValue.104021593 = INTEGER: 37<br>
><br>
> $ snmpwalk -v2c -c foo foo ENTITY-MIB::entPhysicalDescr<br>
> ENTITY-MIB::entPhysicalDescr.21590 = STRING: Module-1, Outlet-1<br>
> ENTITY-MIB::entPhysicalDescr.21591 = STRING: Module-1, Outlet-2<br>
> ENTITY-MIB::entPhysicalDescr.21592 = STRING: Module-1, Intake-1<br>
> ENTITY-MIB::entPhysicalDescr.21593 = STRING: Module-1, Intake-2<br>
> ENTITY-MIB::entPhysicalDescr.21594 = STRING: Module-1, Intake-3<br>
> ENTITY-MIB::entPhysicalDescr.21595 = STRING: Module-1, Intake-4<br>
> ENTITY-MIB::entPhysicalDescr.21596 = STRING: PowerSupply-1 Sensor-1<br>
><br>
> ENTITY-MIB::entPhysicalDescr.21597 = STRING: PowerSupply-2 Sensor-1<br>
><br>
> ( Yes, those are new-lines from the sensor value! )<br>
><br>
> $ snmpwalk -v2c -c foo foo ENTITY-MIB::entPhysicalDescr | grep 10102159<br>
> ENTITY-MIB::entPhysicalDescr.101021590 = STRING: Fex-101 Module-1 Outlet-1<br>
> ENTITY-MIB::entPhysicalDescr.101021593 = STRING: Fex-101 Module-1 Die-1<br>
><br>
> 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…<br>
><br>
> What does your config look like. I assume the sensor values you posted were from snmpwalk yes?<br>
><br>
> Bill<br>
> _______________________________________________<br>
> collectd mailing list<br>
> <a href="mailto:collectd@verplant.org">collectd@verplant.org</a><br>
> <a href="http://mailman.verplant.org/listinfo/collectd" target="_blank">http://mailman.verplant.org/listinfo/collectd</a><br>
<br>
_______________________________________________<br>
collectd mailing list<br>
<a href="mailto:collectd@verplant.org">collectd@verplant.org</a><br>
<a href="http://mailman.verplant.org/listinfo/collectd" target="_blank">http://mailman.verplant.org/listinfo/collectd</a><br>
</div></div></blockquote></div><br>