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

PowerWalker NMC card misidentified as Eaton

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery, OS, Poller
    • None

    Description

      Changes in r12393 resulted in following regression:

      PowerWalker UPS with PowerWalker NMC Card is identified incorrectly as Eaton hardware:

      https://powerwalker.com/product/10120517/

       

      In our case the NMC Card is connected to PowerWalker VFI 10000 TCP 3/1 BI -model, but the card can be connected to any of the PowerWalker VI RT, VFI RT, VFI T, VFI PRT, VFI TCP, VFI TP 3/1 models.

      Attachments

        1. outputv-missing.png
          outputv-missing.png
          413 kB
        2. pw-to-eaton.png
          pw-to-eaton.png
          54 kB
        3. ups-discovery-debug.log
          138 kB
        4. ups-poller-debug.log
          172 kB

        Issue Links

          Activity

            [OBS-4369] PowerWalker NMC card misidentified as Eaton

            Attached latest vendor MIB

            They have not updated the changelog in MIB header, but they fixed incorrectly labeled bypass power sensor:

            493c493
            < 		DESCRIPTION		"The measured input real power in watts."
            ---
            > 		DESCRIPTION		"The measured bypass input real power in watts." 

            nodefield Ilkka Myller added a comment - Attached latest vendor MIB They have not updated the changelog in MIB header, but they fixed incorrectly labeled bypass power sensor: 493c493 < DESCRIPTION "The measured input real power in watts." --- > DESCRIPTION "The measured bypass input real power in watts."

            Attached discovery and poller debug logs

            nodefield Ilkka Myller added a comment - Attached discovery and poller debug logs

            Not really related to this issue, but:

            Just noticed that the NMC Card vendor PowerWalker has made minor description/documentation revision to the latest EPPC UPS MIB.

            Change is one-liner so EPPC MIB shipped with Observium is mostly ok but bypass voltages are mislabeled as input/output voltages.

            I can open separate issue for this minor MIB update if required.

            nodefield Ilkka Myller added a comment - Not really related to this issue, but: Just noticed that the NMC Card vendor PowerWalker has made minor description/documentation revision to the latest EPPC UPS MIB. Change is one-liner so EPPC MIB shipped with Observium is mostly ok but bypass voltages are mislabeled as input/output voltages. I can open separate issue for this minor MIB update if required.

            Already did rediscovery when vendor and sensor value issues occurred (did it again just now to be sure). Running r12458 right now.

            All of the sensors provided by the UPS are correctly discovered and polled, but the polling fails to log/graph the UPS output voltage (@ .1.3.6.1.4.1.935.10.1.1.2.18.1.3)

            Meanwhile output voltage continues to be reported by the SNMP correctly:

            # snmpwalk -c public -v2c <redacted fqdn for the UPS> .1.3.6.1.4.1.935.10.1.1.2.18.1.3
            iso.3.6.1.4.1.935.10.1.1.2.18.1.3.1 = INTEGER: 2297 

             

            I can provide you SNMP dumps, debug output logs etc. and test code changes if required.

             

             

            nodefield Ilkka Myller added a comment - Already did rediscovery when vendor and sensor value issues occurred (did it again just now to be sure). Running r12458 right now. All of the sensors provided by the UPS are correctly discovered and polled, but the polling fails to log/graph the UPS output voltage (@ .1.3.6.1.4.1.935.10.1.1.2.18.1.3) Meanwhile output voltage continues to be reported by the SNMP correctly: # snmpwalk -c public -v2c <redacted fqdn for the UPS> . 1.3 . 6.1 . 4.1 . 935.10 . 1.1 . 2.18 . 1.3 iso. 3.6 . 1.4 . 1.935 . 10.1 . 1.2 . 18.1 . 3.1 = INTEGER: 2297   I can provide you SNMP dumps, debug output logs etc. and test code changes if required.    

            Please make discovery debug as Bot written:

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

            It's should be correctly detect sensors (after rediscovery)..
            And vendor really not possible detect correctly, while same card can used on both UPSes (Eaton and PowerWalker)

            landy Mike Stupalov added a comment - Please make discovery debug as Bot written: ./discovery.php -d -h <device> It's should be correctly detect sensors (after rediscovery).. And vendor really not possible detect correctly, while same card can used on both UPSes (Eaton and PowerWalker)

            Also some change near r12393 caused us to lose all input readings from:

            Output (Phase 1)    EPPC-MIB::upsESystemOutputVoltage.1

            nodefield Ilkka Myller added a comment - Also some change near r12393 caused us to lose all input readings from: Output (Phase 1)    EPPC-MIB::upsESystemOutputVoltage.1

            Attached snmpwalk output (using instructed snmpwalk parameters) as powerwalker-nmc.snmpwalk

            This dump is from Powerwalker NMC Card (https://powerwalker.com/product/10120517/)  attached to PowerWalker VFI 10000 TCP 3/1 BI (https://powerwalker.com/product/10120161/)

             

            nodefield Ilkka Myller added a comment - Attached snmpwalk output (using instructed snmpwalk parameters) as powerwalker-nmc.snmpwalk This dump is from Powerwalker NMC Card ( https://powerwalker.com/product/10120517/ )  attached to PowerWalker VFI 10000 TCP 3/1 BI ( https://powerwalker.com/product/10120161/ )  

            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
              nodefield Ilkka Myller
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: