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

Eaton PDU

Details

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

    Description

      I have some Eaton G3 Managed PDUs that have a couple of data munging issues:

      • Current outlet sensors seem to always be in alarm state (as per attached picture)
      • Load outlset sensors are reporting as -1% (as per attached picture)
      • There's a value for 'crest factor' monitored, but it seems to be very out (e.g. 3984 for an outlet that's barely doing anything - as per attached picture). There's no crest factor value exposed in the device's management web UI so unless obs is calculating this itself, it may be an erroenous value.
      • These units support metering, but they don't get an entry in the counters list.

      Latest manufacturer MIB is attached along with snmp and debug outs.

       

      Thanks!

       

      Attachments

        Activity

          [OBS-4229] Eaton PDU
          landy Mike Stupalov added a comment -

          Should be fixed after r12275.

          landy Mike Stupalov added a comment - Should be fixed after r12275.
          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
            kingtrw Tom King
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: