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

Add Support for monitoring Power Supply on Huawei VRP Devices

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • None

    Description

      Huawei has in newer Versions of their VRP OS an almost standardized oid to check the health of the Power Supplies. Can you please add support for this?

      There is already support for fan status, it should be very similar to this i think.

       

      The description is in the MIBS file HUAWEI-ENTITY-EXTENT-MIB:

      – 1.3.6.1.4.1.2011.5.25.31.1.1.18
      hwPwrStatusTable OBJECT-TYPE
      SYNTAX SEQUENCE OF HwPwrStatusEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
      "This table lists the status of powers. You can read the status of the powers on the device."
      ::= { hwEntityState 18 }

      Attachments

        Activity

          [OBS-3803] Add Support for monitoring Power Supply on Huawei VRP Devices

          Added in r11453.

          landy Mike Stupalov added a comment - Added in r11453.
          bachme+obs@gmail.com bachme added a comment -

          This is from a huawei 'cloudengine' device:

          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.1.1 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.1.2 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.1.1 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.1.2 = INTEGER: 2
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.3.1.1 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.3.1.2 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.4.1.1 = INTEGER: 3
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.4.1.2 = INTEGER: 3
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.5.1.1 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.5.1.2 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.1.1 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.1.2 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.7.1.1 = INTEGER: 5100
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.7.1.2 = INTEGER: 5500
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.8.1.1 = INTEGER: 12200
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.8.1.2 = INTEGER: 12300
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.9.1.1 = Hex-STRING: 73 6C 6F 74 31 2C 50 57 52 31
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.9.1.2 = Hex-STRING: 73 6C 6F 74 31 2C 50 57 52 32

          bachme+obs@gmail.com bachme added a comment - This is from a huawei 'cloudengine' device: .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.1.1 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.1.2 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.1.1 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.1.2 = INTEGER: 2 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.3.1.1 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.3.1.2 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.4.1.1 = INTEGER: 3 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.4.1.2 = INTEGER: 3 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.5.1.1 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.5.1.2 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.1.1 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.1.2 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.7.1.1 = INTEGER: 5100 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.7.1.2 = INTEGER: 5500 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.8.1.1 = INTEGER: 12200 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.8.1.2 = INTEGER: 12300 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.9.1.1 = Hex-STRING: 73 6C 6F 74 31 2C 50 57 52 31 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.9.1.2 = Hex-STRING: 73 6C 6F 74 31 2C 50 57 52 32
          bachme+obs@gmail.com bachme added a comment -

          The snmp looks like this if two power supplies are inserted and OK:

          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.0.5 = INTEGER: 0
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.0.6 = INTEGER: 0
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.0.5 = INTEGER: 5
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.0.6 = INTEGER: 6
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.0.5 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.0.6 = INTEGER: 1

           

          It looks like this if only one power supply is plugged in:

          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.0.5 = INTEGER: 0
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.0.6 = INTEGER: 0
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.0.5 = INTEGER: 5
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.0.6 = INTEGER: 6
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.0.5 = INTEGER: 1
          .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.0.6 = INTEGER: 2

           

          bachme+obs@gmail.com bachme added a comment - The snmp looks like this if two power supplies are inserted and OK: .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.0.5 = INTEGER: 0 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.0.6 = INTEGER: 0 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.0.5 = INTEGER: 5 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.0.6 = INTEGER: 6 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.0.5 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.0.6 = INTEGER: 1   It looks like this if only one power supply is plugged in: .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.0.5 = INTEGER: 0 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.1.0.6 = INTEGER: 0 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.0.5 = INTEGER: 5 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.2.0.6 = INTEGER: 6 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.0.5 = INTEGER: 1 .1.3.6.1.4.1.2011.5.25.31.1.1.18.1.6.0.6 = INTEGER: 2  

          Please make and attach additional information about the device:

          • full snmp dump from 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

            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

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from 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 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 Note, this comment is added automatically.

          People

            landy Mike Stupalov
            bachme+obs@gmail.com bachme
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: