Details

    • Add New Device / OS
    • Resolution: Unresolved
    • Minor
    • None
    • None
    • Default
    • None

    Description

      From documentation

       

      Monitoring Devices with SNMP

      Simple Network Management Protocol (SNMP) is typically used to monitor network devices for conditions that may require action by systems administrators or other network personnel. RioRey devices support SNMP v1, v2c, and v3 using both standard and enterprise Management Information Bases (MIBs). The details of integrating RioRey devices vary depending on your SNMP manager, but the core concepts are the same across all platforms.

      Standard MIBs

      Currently we support the following standard MIBs:

      • IF-MIB
      • IP-MIB

      Standard MIBs are determined by RFC or other standards-based groups, and are not specific to device manufacturer or company. All devices which support a standard MIB will report the same information for the same Object Identifier (OID). Most SNMP Managers will already have the majority of industry standard MIBs loaded, but they can also be found by searching for the relevant RFC or standards group.

      Enterprise MIBs

      We provide the following enterprise MIBs (downloadable here):

      • RIOREY-RIOS-MIB.txt (Unix)
      • RIOREY-TC.txt (Unix)
      • RIOREY-SMI.txt (Unix)
      • RIOREY-RIOS-MIB.mib (Windows)
      • RIOREY-TC.mib (Windows)
      • RIOREY-SMI.mib (Windows)

      Enterprise MIBs are company dependent files that return information specific to the device supported from that company. The files you should load to access RioRey OIDs depend on which platform you are running your SNMP manager on. All three files (per platform) must be loaded for the manager to properly parse our MIBs.

      Attachments

        Activity

          [OBS-4916] Add riorey mitigation devices support

          Hi Mike, I send snmpwalk directly to your email.

          zidek@master.cz Martin Zídek added a comment - Hi Mike, I send snmpwalk directly to your email.

          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
            zidek@master.cz Martin Zídek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: