Details

    • Improvement
    • Resolution: Unresolved
    • Trivial
    • None
    • Professional Edition
    • Poller
    • None

    Description

      I'm trying to add MikroTik 60Ghz devices via SNMP to Observium for P2P link monitoring. Appears SNMP doesnt properly SNMP Walk or able to poll.

      Can you be sure Observium has the proper MikroTik MIB / SNMP values?

       

      https://help.mikrotik.com/docs/display/ROS/W60G

      SNMP OIDs for monitoring

      From RouterOS>=6.42rc6 SNMP support for W60G interface monitoring is added

      For main interfaces:

      1.3.6.1.4.1.14988.1.1.1.8.1.2.1 integer Mode
      1.3.6.1.4.1.14988.1.1.1.8.1.3.1 string SSID
      1.3.6.1.4.1.14988.1.1.1.8.1.4.1 integer Connected status
      1.3.6.1.4.1.14988.1.1.1.8.1.5.1 string Remote MAC
      1.3.6.1.4.1.14988.1.1.1.8.1.6.1 integer Frequency
      1.3.6.1.4.1.14988.1.1.1.8.1.7.1 integer MCS
      1.3.6.1.4.1.14988.1.1.1.8.1.8.1 integer Signal quality
      1.3.6.1.4.1.14988.1.1.1.8.1.9.1 integer tx-sector
      1.3.6.1.4.1.14988.1.1.1.8.1.11.1 string Sector info
      1.3.6.1.4.1.14988.1.1.1.8.1.12.1 integer RSSI
      1.3.6.1.4.1.14988.1.1.1.8.1.13.1 gauge32 PHY rate

      station interfaces will be numbered under different table:

      1.3.6.1.4.1.14988.1.1.1.9.1.2.(interfaceID) = integer Connected status
      1.3.6.1.4.1.14988.1.1.1.9.1.3.(interfaceID) = Hex-STRING mac-address
      1.3.6.1.4.1.14988.1.1.1.9.1.4.(interfaceID) = INTEGER: MCS
      1.3.6.1.4.1.14988.1.1.1.9.1.5.(interfaceID) = INTEGER: Signal Quality Index
      1.3.6.1.4.1.14988.1.1.1.9.1.6.(interfaceID) = INTEGER: tx-sector
      1.3.6.1.4.1.14988.1.1.1.9.1.8.(interfaceID) = Gauge32: data-rate [Mbps]
      1.3.6.1.4.1.14988.1.1.1.9.1.9.(interfaceID) = INTEGER: RSSI
      1.3.6.1.4.1.14988.1.1.1.9.1.10.(interfaceID) = INTEGER: distance [cm]

      Attachments

        Activity

          [OBS-4684] MikroTik 60Ghz SNMP MIBs

          You need make and attach snmpdump (as bot requested) for device support improvements.

           

          landy Mike Stupalov added a comment - You need make and attach snmpdump (as bot requested) for device support improvements.  

          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
            toxicfusion Anthony Armstrong (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: