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

Mikrotik Bridge FDB Changes

Details

    • Vendor Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Poller
    • None

    Description

      Mikrotik has changed how the Bridge FDB is done, Observium does not show correct port for the FDB Table, as the FDB table via SNMP - instead of returning IfIndex, it returns a bridge port index, which needs to be translated into correct IfIndex as below

      • .1.3.6.1.2.1.17.4.3.1.2 MAC table
      • .1.3.6.1.2.1.17.1.4.1.2 BridgePortIndex to InterfaceIndex Mapping
      • .1.3.6.1.2.1.31.1.1.1.1 IfIndex - Interface name{}

      E.g:

      iso.3.6.1.2.1.17.4.3.1.2.244.146.191.240.164.151 = INTEGER: 1 (1 is the bridge port index for the mac address)

      iso.3.6.1.2.1.17.1.4.1.2.1 = INTEGER: 2 (this is bridge port matching 1 to index 2)

      iso.3.6.1.2.1.31.1.1.1.1.2 = STRING: "ether2" (ifindex 2 correct)

       

      Some info:

      https://forum.mikrotik.com/viewtopic.php?t=98246#p971102

      Attachments

        Activity

          [OBS-4373] Mikrotik Bridge FDB Changes
          landy Mike Stupalov added a comment -

          Improved in r12480.

          landy Mike Stupalov added a comment - Improved in r12480.
          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
            ali Ali D
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: