search for: iemstatusprobenam

Hi Dmitry and the list, would you (or anyone owning such a device) be able to validate the below patch: https://alioth.debian.org/tracker/index.php?func=detail&aid=310613&group_id=30602&atid=411542 Most notably, it's about the paths changes: -#define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.0" -#define APCC_OID_IEM_TEMP_UNIT

...ce code the temp value is obtained by querying the following OID: #define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.0" notice that the OID ends with .0 (index zero). Well, looking at the snmpwalk below: PowerNet-MIB::iemStatusProbeNumber.1 = INTEGER: 1 PowerNet-MIB::iemStatusProbeName.1 = STRING: "Int Sensor" PowerNet-MIB::iemStatusProbeStatus.1 = INTEGER: connected(2) PowerNet-MIB::iemStatusProbeCurrentTemp.1 = INTEGER: 32 I see that the index is 1 and not 0, which is why we don't see the temperature probe's values. Fixing the underlying problem is much ha...

Hi Paul, > I have another NUT client for your client-projects[1] page: MonAMI[2]. > > MonAMI aims to be a "universal sensor framework". The data gathered from > MonAMI's NUT plugin can be sent to any of the output plugins. Currently, > these include Ganglia, Nagios, KSysguard and a file-logger (amongst others). interesting though I've not had time to