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

Wrong PDU reading

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • CE-22.5
    • Poller
    • None

    Description

      On some Raritan PDUs ( Raritan PX3-1085I2U-V2) the "balancing" of power phases is reported as "Humidity"

      ie: if the 3 power phases don't have the same load, the PDU is "unbalanced" with a % value

      The 'inlet' value is also a pointer that the data should be power related, not humidity

       

      Attachments

        1. Capture.PNG
          Capture.PNG
          7 kB
        2. debug output.txt
          100 kB

        Activity

          [OBS-4490] Wrong PDU reading
          kmorin Karl Morin added a comment -

          Hello,

          Correct, reported as "Unbalanced Current" from 0 to 200%

          Best,

          kmorin Karl Morin added a comment - Hello, Correct, reported as "Unbalanced Current" from 0 to 200% Best,
          landy Mike Stupalov added a comment -

          Should be fixed in r12748.

          landy Mike Stupalov added a comment - Should be fixed in r12748.
          landy Mike Stupalov added a comment - - edited

          I correctly understand, that this sensor should be "load" class?
          It reported as percent unit.

          landy Mike Stupalov added a comment - - edited I correctly understand, that this sensor should be "load" class? It reported as percent unit.
          kmorin Karl Morin added a comment -

          debug output.txt attached

          Thanks for your help,

          kmorin Karl Morin added a comment - debug output.txt attached Thanks for your help,
          landy Mike Stupalov added a comment -

          please attach debug discovery output, as Bot requested.

          landy Mike Stupalov added a comment - please attach debug discovery output, as Bot requested.
          kmorin Karl Morin added a comment -

          The MIB Object is  .1.1.3

          kmorin Karl Morin added a comment - The MIB Object is  .1.1.3
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            kmorin Karl Morin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: