Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3168

Read AP4430 Voltage, Current, and Power

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Poller
    • None

    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

        1. AP4430.Discovery.Debug
          92 kB
        2. AP4430.SNMPWalk.txt
          29 kB
        3. AP4430-Load.png
          AP4430-Load.png
          13 kB
        4. AP4430-Status.png
          AP4430-Status.png
          39 kB
        5. myagent.snmpwalk
          151 kB
        6. Observium-AP4430.png
          Observium-AP4430.png
          39 kB
        7. Observium - apc-ats2.test 2019-12-20 00-49-39.png
          Observium - apc-ats2.test 2019-12-20 00-49-39.png
          161 kB
        8. Screenshot from 2019-12-19 12-57-27.png
          Screenshot from 2019-12-19 12-57-27.png
          73 kB

        Activity

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

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

          Alain Alain Gyger added a comment - Thank you for your work, everything shows up correctly now.

          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.

          landy Mike Stupalov added a comment - 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.

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

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

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

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

          landy Mike Stupalov added a comment - This is really strange.. because see what I see based on your dump:

          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 Alain Gyger added a comment - 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:

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

          landy Mike Stupalov added a comment - Improved in r10207 (need device(s) rediscovery).

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

          Alain Alain Gyger added a comment - Here is the output of the two commands you sent: myagent.snmpwalk

          (your previous walk not include enterprise oid tree)

          landy Mike Stupalov added a comment - (your previous walk not include enterprise oid tree)

          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

          landy Mike Stupalov added a comment - 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

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

          Alain Alain Gyger added a comment - Sure thing, I've run the script and attached the output. AP4430.Discovery.Debug

          People

            landy Mike Stupalov
            Alain Alain Gyger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: