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

Eaton EATS16N discovery fails with newer firmware (LD/LE)

Details

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

    Description

      Eaton ATS EATS16N works perfectly fine in observium with firmware LB. When we upgrade to firmware version LD or version LE the device is not recognised correctly as an Eaton device but MGE with no sensors detected.

      I am happy to walk the three different firmware version in any format you prefer.

      Discovery snippet:

      Firmware: LB

              1.  Module Start: sensors  #####

       o EATON-ATS2-MIB       ats2InputVoltage [..] ats2InputFrequency [..] ats2OutputVoltage [.] ats2OutputCurrent [.] ats2EnvRemoteTemp [] ats2EnvRemote
       o EATON-ATS2-MIB       ats2OperationMode [.] ats2InputStatusGood [] ats2InputStatusUsed [] ats2StatusInternalFailure [.] ats2StatusOutput [.] ats2S
       o ENTITY-SENSOR-MIB

      Firmware: LD / LE

              1.  Module Start: sensors  #####

       o XUPS-MIB             xupsContactState []
       o MG-SNMP-UPS-MIB       upsmgBattery  upsmgConfigEnvironmentTable upsmgEnvironmentSensorTable
       o XUPS-MIB
       o ENTITY-SENSOR-MIB

      Attachments

        Activity

          [OBS-4328] Eaton EATS16N discovery fails with newer firmware (LD/LE)
          landy Mike Stupalov made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          Fixed in r12396.

          Rediscovery devices after update.
          Currently only in Rolling updates:
          https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

          landy Mike Stupalov added a comment - Fixed in r12396. Rediscovery devices after update. Currently only in Rolling updates: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: In Progress [ 3 ]

          I have attached 3 snmpwalk outputs.

          Firmware LD and LE that currently have problems and Firmware LB for comparison that is working great currently.

           

          Thank you

          bdonovan Ben Donovan added a comment - I have attached 3 snmpwalk outputs. Firmware LD and LE that currently have problems and Firmware LB for comparison that is working great currently.   Thank you
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          bdonovan Ben Donovan made changes -
          Attachment New: myagent.snmpwalk-lb [ 20288 ]
          Attachment New: myagent.snmpwalk-le [ 20289 ]
          Attachment New: myagent.snmpwalk-ld [ 20290 ]
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          bdonovan Ben Donovan created issue -

          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
            bdonovan Ben Donovan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: