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

Trip Lite PDU metrics not displaying

Details

    • Vendor Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Poller
    • None
    • Trip Lite PDUMV15NET, latest observium professional

    Description

      Values for the PDU mentioned above have some issues, as follows.

      Apparent Power: shows 0VA all the time.
      Capacity: shows 0% all the time
      Current Input - shows 0A all the time
      Frequency - off by an order of magnitude, shows 599Hz when it should be showing 59.9Hz
      Power Input - shows 0W all the time
      Voltage Output - shows 0V all the time.
      Network traffic - "Error drawing graph" all the time

      The latest MIB is located here:
      http://www.tripplite.com/shared/software/Firmware/Tripp-Lite-MIB-Definitions.txt

      Let me know what other kind of data (snmpwalk, etc) I can provide to help with troubleshooting.

      Attachments

        Issue Links

          Activity

            [OBS-1432] Trip Lite PDU metrics not displaying

            Hello Mike,

            Thank you for taking the time to reply. This is a 24-plug PDU connected to our lab, one of 8 we have. That one has 5 servers and around 19 appliances attached to it. One of the things we had hoped for was the ability to see all of the plugs and their status in Observium, but it's a big ask for such a niche with an already excellent product

            The AMP reading is correct, that unit is one of two that's almost at max load, so we need to keep a close eye on it. For now we have the alarm set at '1.7 amps' – Also! I should mention we love your product and will be purchasing a few copies soon. Observium is excellent.

            ciro Ciro Martinez added a comment - Hello Mike, Thank you for taking the time to reply. This is a 24-plug PDU connected to our lab, one of 8 we have. That one has 5 servers and around 19 appliances attached to it. One of the things we had hoped for was the ability to see all of the plugs and their status in Observium, but it's a big ask for such a niche with an already excellent product The AMP reading is correct, that unit is one of two that's almost at max load, so we need to keep a close eye on it. For now we have the alarm set at '1.7 amps' – Also! I should mention we love your product and will be purchasing a few copies soon. Observium is excellent.

            We see the amps reported as 1.7 AMP when the actual load out of SNMP is 17 amps

            Ciro, why you think that real output for your ups/pdu is 17 amps?
            How many devices currently connected to this pdu/ups?

            17 amps is too many is currently connected 1-2 power devices.

            landy Mike Stupalov added a comment - We see the amps reported as 1.7 AMP when the actual load out of SNMP is 17 amps Ciro, why you think that real output for your ups/pdu is 17 amps? How many devices currently connected to this pdu/ups? 17 amps is too many is currently connected 1-2 power devices.

            This is still vendor issue!
            This value must be scaled as 0.1 after get by snmp from device. You can see this as unit description in output (0.1 RMS Amp).
            This as described in mib, this do all other vendors.

            I not know good way for detect if device return correct or incorrect data.

            landy Mike Stupalov added a comment - This is still vendor issue! This value must be scaled as 0.1 after get by snmp from device. You can see this as unit description in output (0.1 RMS Amp). This as described in mib, this do all other vendors. I not know good way for detect if device return correct or incorrect data.
            rickheil Rick Heil added a comment -

            Ok, similar. I have contacted Mike offline again to provide him access to our unit. Stay tuned.

            rickheil Rick Heil added a comment - Ok, similar. I have contacted Mike offline again to provide him access to our unit. Stay tuned.

            Hi Rick,

            We are seeing this error on: Engine Version=12.06.0067, Driver Version=12.06.0067.8625.8624 - When I run the snmpwalk I get the correct hz and current report out of it, but observium is pulling in Current / 10. I was looking through the poller to see if I could adjust that.

            ciro Ciro Martinez added a comment - Hi Rick, We are seeing this error on: Engine Version=12.06.0067, Driver Version=12.06.0067.8625.8624 - When I run the snmpwalk I get the correct hz and current report out of it, but observium is pulling in Current / 10. I was looking through the poller to see if I could adjust that.
            rickheil Rick Heil added a comment -

            Ciro - which version of the SNMPWEBCARD firmware are you using? I just updated to 12.06.0067.8624 and it fixed the frequency, voltage, and input decimal placement. Loading it up now and will test against output next.

            rickheil Rick Heil added a comment - Ciro - which version of the SNMPWEBCARD firmware are you using? I just updated to 12.06.0067.8624 and it fixed the frequency, voltage, and input decimal placement. Loading it up now and will test against output next.
            ciro Ciro Martinez added a comment - - edited

            Hello Mike,

            Do you still need information or direct access to a tripplite unit? I've noticed that the AMP report is an order of magnitude off. We see the amps reported as 1.7 AMP when the actual load out of SNMP is 17 amps:

            $ snmpwalk -v2c -c XXX 172.16.7.52 UPS-MIB:upsOutputCurrent.1
            UPS-MIB::upsOutputCurrent.1 = INTEGER: 16 0.1 RMS Amp

            Here's the Observium Amp Reading

            ciro Ciro Martinez added a comment - - edited Hello Mike, Do you still need information or direct access to a tripplite unit? I've noticed that the AMP report is an order of magnitude off. We see the amps reported as 1.7 AMP when the actual load out of SNMP is 17 amps: $ snmpwalk -v2c -c XXX 172.16.7.52 UPS-MIB:upsOutputCurrent.1 UPS-MIB::upsOutputCurrent.1 = INTEGER: 16 0.1 RMS Amp Here's the Observium Amp Reading
            rickheil Rick Heil added a comment -

            Coordinated access via email.

            rickheil Rick Heil added a comment - Coordinated access via email.

            Seems as this device incorrectly support for UPS-MIB.

            CMD[/usr/bin/snmpwalk -v1 -c *** -Pu -OQUs -m UPS-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'pdu.partnersandsimons.com':'161' upsInput]
             
            STDOUT[
            upsInputNumLines.0 = 1
            upsInputLineIndex.1 = 1
            upsInputFrequency.1 = 5990
            upsInputVoltage.1 = 1101
            ]
             
            CMD[/usr/bin/snmpwalk -v1 -c *** -Pu -OQUs -m UPS-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'pdu.partnersandsimons.com':'161' upsOutput]
             
            STDOUT[
            upsOutputSource.0 = normal
            upsOutputNumLines.0 = 1
            upsOutputLineIndex.1 = 1
            upsOutputCurrent.1 = 0
            ]
            

            I can try to add basic support by vendor MIB, but required snmp access to device.
            If possible, write me to mike@observium.org

            landy Mike Stupalov added a comment - Seems as this device incorrectly support for UPS-MIB. CMD[/usr/bin/snmpwalk -v1 -c *** -Pu -OQUs -m UPS-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'pdu.partnersandsimons.com':'161' upsInput]   STDOUT[ upsInputNumLines.0 = 1 upsInputLineIndex.1 = 1 upsInputFrequency.1 = 5990 upsInputVoltage.1 = 1101 ]   CMD[/usr/bin/snmpwalk -v1 -c *** -Pu -OQUs -m UPS-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'pdu.partnersandsimons.com':'161' upsOutput]   STDOUT[ upsOutputSource.0 = normal upsOutputNumLines.0 = 1 upsOutputLineIndex.1 = 1 upsOutputCurrent.1 = 0 ] I can try to add basic support by vendor MIB, but required snmp access to device. If possible, write me to mike@observium.org
            rickheil Rick Heil added a comment -

            Bump - attached output of discovery and sensors polling. Fix likely has to do with the sensor_multiplier value for frequency and voltage?

            discovery-output.txt poller-output.txt

            rickheil Rick Heil added a comment - Bump - attached output of discovery and sensors polling. Fix likely has to do with the sensor_multiplier value for frequency and voltage? discovery-output.txt poller-output.txt
            rickheil Rick Heil added a comment -

            Bump, this is still an issue.

            rickheil Rick Heil added a comment - Bump, this is still an issue.

            People

              landy Mike Stupalov
              rickheil Rick Heil
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: