Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • Enterprise Edition
    • Poller
    • None

    Description

      As you can see in the screenshot, the Eaton SC300 (site controller) is not detecting any "special" sensors. Do I need a specific MIB, such as the RPS-200-MIB?

      I have attached the output of the discovery command.

      Thank you very much!

      Attachments

        Activity

          [OBS-4998] Eaton SC300 sensor recognition

          Thank you! 

          maximus Jan Braitinger added a comment - Thank you! 

          Added support for this model in r13966.

          landy Mike Stupalov added a comment - Added support for this model in r13966.

          Oh, I am sry
          [^sc300-v117.mib]

          maximus Jan Braitinger added a comment - Oh, I am sry [^sc300-v117.mib]

          Nono, just give me (attach) this MIB file here.

          landy Mike Stupalov added a comment - Nono, just give me (attach) this MIB file here.

          I downloaded the MIB and placed it into the Eaton MIB folder. I also added it to eaton.inc.php (for device and OS).
          The MIB is displayed under Properties -> MIBs, but the background of that row appears to be red.
           
           
           
           
           

          maximus Jan Braitinger added a comment - I downloaded the MIB and placed it into the Eaton MIB folder. I also added it to eaton.inc.php (for device and OS). The MIB is displayed under Properties -> MIBs , but the background of that row appears to be red.          

          [^device.snmpwalk]

          maximus Jan Braitinger added a comment - [^device.snmpwalk]

          You need to make snmpdump and attach vendor specific MIB files.

          https://docs.observium.org/developing/add_device/

          landy Mike Stupalov added a comment - You need to make snmpdump and attach vendor specific MIB files. https://docs.observium.org/developing/add_device/

          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
            maximus Jan Braitinger
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: