Details

    • Add New Device / OS
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Discovery

    Description

      Hello,

      I work at an ISP and we are using Observium Professional edition for monitoring our nodes and hubs and we need to monitoring our UPS to ckeck the electric range.

      Please your help to add the iStars UPS MIB. In the past we were using PRTG and it had the MIB.

       

      If you need additional information, please let me know.

       

      Thank you in advance!

      Attachments

        Activity

          [OBS-3939] MIB for iStar UPS

          Support added in r11818.

          landy Mike Stupalov added a comment - Support added in r11818.

          To solve this case I'm using generic OIDs, I have created them in "Custom OID" to measure the "charge remaining" and "output load", I tested them with two different UPS-network-card vendors (istars and APC) and it works.

          ftipiani Fernando Tipiani added a comment - To solve this case I'm using generic OIDs, I have created them in "Custom OID" to measure the "charge remaining" and "output load", I tested them with two different UPS-network-card vendors (istars and APC) and it works.

          Hello, thank you for your answer, I have uploaded the snmp dump.

          [^myagent.snmpwalk]

          ftipiani Fernando Tipiani added a comment - Hello, thank you for your answer, I have uploaded the snmp dump. [^myagent.snmpwalk]

          required snmp dump as bot requested.

          landy Mike Stupalov added a comment - required snmp dump as bot requested.
          ftipiani Fernando Tipiani added a comment - - edited

          Maybe this MIB could be useful

          http://www.oidview.com/mibs/0/UPS-MIB.html]

          ftipiani Fernando Tipiani added a comment - - edited Maybe this MIB could be useful http://www.oidview.com/mibs/0/UPS-MIB.html ]

          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
            ftipiani Fernando Tipiani
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: