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

Eaton UPS integration

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • None
    • Default
    • None

    Description

      Hello,

      prevously in ticket https://jira.observium.org/browse/OBS-4314 we've reported issue with Eation UPS. However when we upgraded to the latest SVN version the issue is still there.

       

      We are on revision 12421

       

       

      Attachments

        Issue Links

          relates to

          Add New Device / OS - User wants to add support for currently unsupported device or OS. OBS-4314 Eaton UPS integration

          • Major - Major loss of function.
          • Resolved

          Vendor Bug - This is vendor specific issue, not possible to be fixed inside our project. OBS-4458 Eaton UPS - still not displaying proper info

          • Major - Major loss of function.
          • Closed

          Activity

            [OBS-4383] Eaton UPS integration
            landy Mike Stupalov added a comment -

            Limits improved in r12489.

            landy Mike Stupalov added a comment - Limits improved in r12489.
            ymarinov Yavor Marinov added a comment -

            I've just attached the debug discovery.

            On svn status returns nothing, meaning that it's on last svn update

            ymarinov Yavor Marinov added a comment - I've just attached the debug discovery. On svn status returns nothing, meaning that it's on last svn update
            landy Mike Stupalov added a comment -

            It seems you mean limits (not values). But as I see in code for this sensors all should be correctly discover.

            Please make debug for discovery:

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

            and additionally show svn status:

            svn status /opt/observium

            landy Mike Stupalov added a comment - It seems you mean limits (not values). But as I see in code for this sensors all should be correctly discover. Please make debug for discovery: ./discovery.php -d -m sensors -h <device> and additionally show svn status: svn status /opt/observium
            ymarinov Yavor Marinov added a comment -

            The issue is that OBS doesn't show proper values for Input/Output voltage. SNMPwalks can be find in https://jira.observium.org/browse/OBS-4314

            ymarinov Yavor Marinov added a comment - The issue is that OBS doesn't show proper values for Input/Output voltage. SNMPwalks can be find in https://jira.observium.org/browse/OBS-4314
            ymarinov Yavor Marinov added a comment -

            Yes, device is discovered long time ago

            ymarinov Yavor Marinov added a comment - Yes, device is discovered long time ago
            landy Mike Stupalov added a comment -

            Which issue exactly you mean?

            Did you rediscover device?

            landy Mike Stupalov added a comment - Which issue exactly you mean? Did you rediscover device?
            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
              ymarinov Yavor Marinov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: