We have a number of Avocent PM3000 series PDUs and external sensors (models both with and without humidity sensors) for environmental monitoring. We use snmp software (eg. RPTG by Paessler) to track values (eg. power, temperature, humidity) from each PDU. When there is only 1 external sensor connected to a PDU sensor port, all behaves as it should. But when external sensors are chained (and perhaps particularly with the temperature+humidity version), the order of some of the sensors in the various snmp tables change over time (though remain internally consistent). If we have correct setup one day to track values, later it may swap, making the readings worthless. Eg. external temp may swap with external humidity, for the same index in to the sensors table. It's as if the external sensors "re-boot" periodically (not real pattern though), and when they do, the order they are assigned in the snmp MIB tables are somewhat random. Example: 2 PDUs, 1st one with 2 external sensors chained off 1 port, and a 2nd PDU with 1 senor Object ID: .1.3.6.1.4.1.10418.17.2.5.13.1.4 - "Name of the sensor." .iso.org.dod.internet.private.enterprises.enterprises-10418.pm.pmManagement.pmPowerMgmt.pmPowerMgmtSensorsTable.pmPowerMgmtSensorsTableEntry.pmPowerMgmtSensorsTableName Over time, this gives the following example: Hardware: Avocent PM3000, Firmware: 2.0.1.13 (Sep 14 2011 - 04:19:54); Manual states max of 3 sensors a chain & 6 per PDU. Any help appreciated, as we cannot work with this as it is, and would like to be able to chain sensors, as advertised. Apologies if this is posted in the wrong forum group
↧