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

Huawei UPS reporting wrong battery runtime remaining

Details

    • Vendor Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Poller
    • None

    Description

      We have recently installed a new UPS from Huawei: UPS5000-E.

      The device was discovered without any problems. However I have just noticed that the remaining battery life is reported too high by a factor of 60. So I assume that the SNMP provides the value in seconds and Observium incorrectly gives the value in minutes.

      snmpwalk is attached.

      Attachments

        Activity

          [OBS-4112] Huawei UPS reporting wrong battery runtime remaining
          swfeldkirch Siegfried Gumilar added a comment -

          Hi Mike,

          we now have all the values we need - thank you! However the power values are still too large by a power of ten. Observium, for example, shows 34 kW or kVA while in reality it is 3.4 kW or kVA.

          swfeldkirch Siegfried Gumilar added a comment - Hi Mike, we now have all the values we need - thank you! However the power values are still too large by a power of ten. Observium, for example, shows 34 kW or kVA while in reality it is 3.4 kW or kVA.
          landy Mike Stupalov added a comment -

          Improved in r12022.

          landy Mike Stupalov added a comment - Improved in r12022.
          landy Mike Stupalov added a comment -

          Will see

          landy Mike Stupalov added a comment - Will see
          swfeldkirch Siegfried Gumilar added a comment -

          Hi Mike,

          as always thank you for your quick support! It seems that I should have taken a closer look at all the values right at the beginning. The frequency of our UPS is currently also displayed at approx. 500Hz. In addition, the values for current, voltage, power, frequency and load are only displayed for phase 1, although it is a 3-phase UPS. Could you please also fix this?

          swfeldkirch Siegfried Gumilar added a comment - Hi Mike, as always thank you for your quick support! It seems that I should have taken a closer look at all the values right at the beginning. The frequency of our UPS is currently also displayed at approx. 500Hz. In addition, the values for current, voltage, power, frequency and load are only displayed for phase 1, although it is a 3-phase UPS. Could you please also fix this?
          landy Mike Stupalov added a comment -

          Should be fixed in r12019.

          landy Mike Stupalov added a comment - Should be fixed in r12019.
          swfeldkirch Siegfried Gumilar added a comment -

          done

          swfeldkirch Siegfried Gumilar added a comment - done
          landy Mike Stupalov added a comment -

          swfeldkirch Can you get and attach latest UPS MIB by this instruction?
          https://support.huawei.com/enterprise/en/doc/EDOC1100207210/5bad1c22/installing-the-ups-mib-library

          landy Mike Stupalov added a comment - swfeldkirch Can you get and attach latest UPS MIB by this instruction? https://support.huawei.com/enterprise/en/doc/EDOC1100207210/5bad1c22/installing-the-ups-mib-library
          landy Mike Stupalov added a comment -

          As I see it's show in dump it incorrectly report time as seconds (but here should be minutes):

          UPS-MIB::upsEstimatedMinutesRemaining.0 = INTEGER: 8760 minutes

          in own mib seconds:

          HUAWEI-UPS-MIB::hwUpsBatteryBackupTime.1 = Gauge32: 8820 S

          I will switch to Huawei own MIB.

          landy Mike Stupalov added a comment - As I see it's show in dump it incorrectly report time as seconds (but here should be minutes): UPS-MIB::upsEstimatedMinutesRemaining.0 = INTEGER: 8760 minutes in own mib seconds: HUAWEI-UPS-MIB::hwUpsBatteryBackupTime.1 = Gauge32: 8820 S I will switch to Huawei own MIB.
          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
            swfeldkirch Siegfried Gumilar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: