[OBS-3168] Read AP4430 Voltage, Current, and Power - Observium

Details

Type: Improvement
Resolution: Fixed
Priority: Major
Fix Version/s: None
Affects Version/s: Professional Edition
Component/s: Poller
Labels:
None
Environment:

Hide
AP4430 details:
    Hardware Revision: R01
    Firmware Version: 4.1.9

Observium details:
    Version: 19.12.10195
    Powernet MIB Version: 4.3.1

Show
AP4430 details:     Hardware Revision: R01     Firmware Version: 4.1.9 Observium details:     Version: 19.12.10195     Powernet MIB Version: 4.3.1

Description

Observium displays 0V, 0A, 0W for respective sections of an APC AP4430's page. I've included a screenshot of the section, only the Source A, Source B, Hardware, and Switch Status Indicators are displaying correct data. I've also included a screenshot from the AP4430's webpage showing current values. I've also included an SNMPWalk of my AP4430

Is it possible to update Observium to report Voltage, Current, and Power?

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

AP4430.Discovery.Debug
92 kB
2019/12/12 04:44 PM
AP4430.SNMPWalk.txt
29 kB
2019/12/11 11:39 PM
AP4430-Load.png
13 kB
2019/12/11 11:28 PM
AP4430-Status.png
39 kB
2019/12/11 11:28 PM
myagent.snmpwalk
151 kB
2019/12/18 11:01 PM
Observium-AP4430.png
39 kB
2019/12/11 11:28 PM
Observium - apc-ats2.test 2019-12-20 00-49-39.png
161 kB
2019/12/19 09:56 PM
Screenshot from 2019-12-19 12-57-27.png
73 kB
2019/12/19 09:13 PM

Activity

[OBS-3168] Read AP4430 Voltage, Current, and Power

Alain Gyger added a comment - 2019/12/19 11:40 PM

Thank you for your work, everything shows up correctly now.

Alain Gyger added a comment - 2019/12/19 11:40 PM Thank you for your work, everything shows up correctly now.

Mike Stupalov added a comment - 2019/12/19 11:17 PM

Ok, I found trouble.
This devices really have problem with snmpget for specific Oids, example:

snmpget -v2c -c <community> -On <hostname> .1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.1.1.1

.1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.1.1.1 = No Such Instance currently exists at this OID

ws snmpwalk:

snmpwalk -v2c -c <community> -On <hostname> .1.3.6.1.4.1.318.1.1.8.5.3.3.1.3

.1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.1.1.1 = INTEGER: 225

.1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.2.1.1 = INTEGER: 228

I added workaround in r10208.
No need additional rediscovery, next poll after update will get the correct values.

Mike Stupalov added a comment - 2019/12/19 11:17 PM Ok, I found trouble. This devices really have problem with snmpget for specific Oids, example: snmpget -v2c -c <community> -On <hostname> .1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.1.1.1 .1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.1.1.1 = No Such Instance currently exists at this OID ws snmpwalk: snmpwalk -v2c -c <community> -On <hostname> .1.3.6.1.4.1.318.1.1.8.5.3.3.1.3 .1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.1.1.1 = INTEGER: 225 .1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.2.1.1 = INTEGER: 228 I added workaround in r10208. No need additional rediscovery, next poll after update will get the correct values.

Mike Stupalov added a comment - 2019/12/19 09:53 PM

Ok, please make than additional debug (probably this is some device specific trouble):

./poller.php -d -r -m sensors,status -h <device>

Mike Stupalov added a comment - 2019/12/19 09:53 PM Ok, please make than additional debug (probably this is some device specific trouble): ./poller.php -d -r -m sensors,status -h <device>

Mike Stupalov added a comment - 2019/12/19 09:51 PM

This is really strange.. because see what I see based on your dump:

Mike Stupalov added a comment - 2019/12/19 09:51 PM This is really strange.. because see what I see based on your dump:

Alain Gyger added a comment - 2019/12/19 09:13 PM

I updated to r10207 and did a rediscovery of my AP4430. I get more information under Status Indicators, but still no information on Voltage, Current, or Power.

I also tried deleting the device (including RRDs) and added it back to Observium, but got the same result.

I've attached a screen shot of what the information looks like now:

Alain Gyger added a comment - 2019/12/19 09:13 PM I updated to r10207 and did a rediscovery of my AP4430. I get more information under Status Indicators, but still no information on Voltage, Current, or Power. I also tried deleting the device (including RRDs) and added it back to Observium, but got the same result. I've attached a screen shot of what the information looks like now:

Mike Stupalov added a comment - 2019/12/19 06:08 PM

Improved in r10207 (need device(s) rediscovery).

Mike Stupalov added a comment - 2019/12/19 06:08 PM Improved in r10207 (need device(s) rediscovery).

Alain Gyger added a comment - 2019/12/18 11:01 PM

Here is the output of the two commands you sent: myagent.snmpwalk

Alain Gyger added a comment - 2019/12/18 11:01 PM Here is the output of the two commands you sent: myagent.snmpwalk

Mike Stupalov added a comment - 2019/12/18 10:19 PM

(your previous walk not include enterprise oid tree)

Mike Stupalov added a comment - 2019/12/18 10:19 PM (your previous walk not include enterprise oid tree)

Mike Stupalov added a comment - 2019/12/18 10:18 PM

Hrm, sure, wrong sensors discovery.

Please do one additional step, make full snmp dump for this device:

snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

Mike Stupalov added a comment - 2019/12/18 10:18 PM Hrm, sure, wrong sensors discovery. Please do one additional step, make full snmp dump for this device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

Alain Gyger added a comment - 2019/12/12 04:45 PM

Sure thing, I've run the script and attached the output. AP4430.Discovery.Debug

Alain Gyger added a comment - 2019/12/12 04:45 PM Sure thing, I've run the script and attached the output. AP4430.Discovery.Debug

People

Assignee:: Mike Stupalov

Reporter:: Alain Gyger

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2019/12/11 11:40 PM

Updated:: 2020/01/19 06:10 PM

Resolved:: 2019/12/19 06:08 PM