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

Eaton Powermate 9130 - not discovered correctly / identified as "Generic device"

Details

    • Vendor Bug
    • Resolution: Fixed
    • Major
    • None
    • Community Edition
    • Discovery

    Description

      Hi,

      I try to add an Eaton Powermate 9130 to my devices. Observium does connect, but can not identify the device as "power" and there is no sensors shown.

      Using the attached MIBs I could get the data with an SNMP browser, but even if I copy them into the correct mib folder, nothing changes.

      After copying the new MIBs to the correct folder, I have tried to run the command:

      /opt/observium/discovery.php -h all

      That took 61s but the UPS is still identified as "Generic device".

      Observium reads the contact, System name, location, System descrition correctly, …, but it can not identify which MIBs should it use to read the usable data.

       

      Attachments

        1. discovery.txt
          59 kB
        2. myagent.snmpwalk
          71 kB
        3. obs_eaton.jpg
          obs_eaton.jpg
          525 kB
        4. poller.txt
          93 kB
        5. ups_poll_debug.txt
          158 kB

        Activity

          [OBS-3362] Eaton Powermate 9130 - not discovered correctly / identified as "Generic device"

          Excellent

          kentbjoh Kent Johannessen added a comment - Excellent

          Try with r10542.

          landy Mike Stupalov added a comment - Try with r10542.

          Hi,

          Great work around the memory leak. We had a few of these, which now have their sensors back
          However we still have problem with the ifDescr on every poll. Could that be fixed? I saw there was a commit for it, but didnt seems to fix for us.
          I am attaching a poller debug for one of our devices

          kentbjoh Kent Johannessen added a comment - Hi, Great work around the memory leak. We had a few of these, which now have their sensors back However we still have problem with the ifDescr on every poll. Could that be fixed? I saw there was a commit for it, but didnt seems to fix for us. I am attaching a poller debug for one of our devices

          Fixed in r10487.

          landy Mike Stupalov added a comment - Fixed in r10487.
          landy Mike Stupalov added a comment - - edited

          wow, wow.. what is interface names :O

          Memory leak..

          SNMPv2-MIB::sysObjectID.0 = OID: .2.1060362971.858861873.858992945.3006477235.3073587135.825373491.858993459
          ...
          IF-MIB::ifDescr.1 = STRING: ........................
          IF-MIB::ifDescr.2 = STRING: 232#373.s3.?333?3333332.3ss33{;s13303330333?337s332331.333733;73.3..332127s3777.2333302S333733333.#332.33.3.33;.2303332333..3.77333#3#3#33;333w73333#03137.77..3333.333.33..S.733333233333.733w;32232332.37.;37313133331;33;3;.;33113.3333;...3w2.3233227;73s33s#3132;3333;3333w333233 .3.3.333;331\"332233.?337s.3113.3313;33.7.\"3.'3313333333;;33313.33333;7w;3333.333\"3s33;33;33\"3333.33s7333.131#1#0333.7737.3333333233?w3;.;2.21333!33q33?3733233\"..3{;373;7331.3322w33{;.373311#332333#33;7333\"31#33;33333332..331#33333;6;.333333\"3ss{.7.73.3323#1;33?33.;31.33312337..73333#33112;;7s3s?;313.33.33.;.33732#.333333333333333#2#33#333{3;;7312333 .3373?3;331113311.33..37.12333333s37.337. 333333 33{.33332.3.1332w3ss3s7s3132132.?s33w3?33.131#3333333.;33\"33#2!.333;3373
          

          landy Mike Stupalov added a comment - - edited wow, wow.. what is interface names :O Memory leak.. SNMPv2-MIB::sysObjectID.0 = OID: .2.1060362971.858861873.858992945.3006477235.3073587135.825373491.858993459 ... IF-MIB::ifDescr.1 = STRING: ........................ IF-MIB::ifDescr.2 = STRING: 232#373.s3.?333?3333332.3ss33{;s13303330333?337s332331.333733;73.3..332127s3777.2333302S333733333.#332.33.3.33;.2303332333..3.77333#3#3#33;333w73333#03137.77..3333.333.33..S.733333233333.733w;32232332.37.;37313133331;33;3;.;33113.3333;...3w2.3233227;73s33s#3132;3333;3333w333233 .3.3.333;331\"332233.?337s.3113.3313;33.7.\"3.'3313333333;;33313.33333;7w;3333.333\"3s33;33;33\"3333.33s7333.131#1#0333.7737.3333333233?w3;.;2.21333!33q33?3733233\"..3{;373;7331.3322w33{;.373311#332333#33;7333\"31#33;33333332..331#33333;6;.333333\"3ss{.7.73.3323#1;33?33.;31.33312337..73333#33112;;7s3s?;313.33.33.;.33732#.333333333333333#2#33#333{3;;7312333 .3373?3;331113311.33..37.12333333s37.337. 333333 33{.33332.3.1332w3ss3s7s3132132.?s33w3?33.131#3333333.;33\"33#2!.333;3373

          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
            bzahalka Bence Zahalka
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: