LLDP broken?

RouterOS General
1

Hi all,

this applies to 7.4.2 as well as to 7.15beta9. I replaced a Cisco Catalyst 2960-L with a CRS326-24G-2S+IN running RouterOS. Switch OS was just too limited for my tastes, I run multiple LACP trunks and I use Observium to monitor all my systems with SNMP.

I currently have two systems connected to the Mikrotik switch that run LLDP. Both use an LACP trunk built from two ports and VLANs on top of that. Switching wise this is a great affordable and small device. Everything works. Except LLDP at the moment.
Bildschirmfoto 2024-04-08 um 18.49.27.png
The Mikrotik is not able to discover the two different interfaces of each device it is connected to.

From the OPNsense the connection looks like this:

root@opnsense:~ # lldpcli show neighbors
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface:    ax0, via: LLDP, RID: 1, Time: 0 day, 02:36:19
  Chassis:     
    ChassisID:    mac d4:01:c3:3a:fb:7f
    SysName:      MikroTik
    SysDescr:     MikroTik RouterOS 7.15beta9 (development) 2024-03-27 19:55:08 CRS326-24G-2S+
    MgmtIP:       192.168.1.8
    MgmtIface:    27
    MgmtIP:       fe80::d601:c3ff:fe3a:fb7f
    MgmtIface:    27
    MgmtIP:       2003:a:d59:3800:d601:c3ff:fe3a:fb7f
    MgmtIface:    27
    Capability:   Bridge, on
    Capability:   Router, on
  Port:        
    PortID:       ifname sfp-sfpplus1
    PortDescr:    bridge/bonding3/sfp-sfpplus1
    TTL:          120
-------------------------------------------------------------------------------
Interface:    ax1, via: LLDP, RID: 1, Time: 0 day, 02:36:19
  Chassis:     
    ChassisID:    mac d4:01:c3:3a:fb:7f
    SysName:      MikroTik
    SysDescr:     MikroTik RouterOS 7.15beta9 (development) 2024-03-27 19:55:08 CRS326-24G-2S+
    MgmtIP:       192.168.1.8
    MgmtIface:    27
    MgmtIP:       fe80::d601:c3ff:fe3a:fb7f
    MgmtIface:    27
    MgmtIP:       2003:a:d59:3800:d601:c3ff:fe3a:fb7f
    MgmtIface:    27
    Capability:   Bridge, on
    Capability:   Router, on
  Port:        
    PortID:       ifname sfp-sfpplus2
    PortDescr:    bridge/bonding3/sfp-sfpplus2
    TTL:          120
-------------------------------------------------------------------------------

From the TrueNAS it looks like this:

root@freenas[~]# ladvdc -L -f
Chassis id: d4:01:c3:3a:fb:7f
Port id: ether19
Time remaining: 93 seconds
System Name: MikroTik
System Description: MikroTik RouterOS 7.15beta9 (development) 2024-03-27 19:55:08 CRS326-24G-2S+
Management Address IPv4: 192.168.1.8
Management Address IPv6: fe80::d601:c3ff:fe3a:fb7f
Management Address IPv6: 2003:a:d59:3800:d601:c3ff:fe3a:fb7f
System Capabilities: BR
Enabled Capabilities: BR
Port Description: bridge/bonding2/ether19

Chassis id: d4:01:c3:3a:fb:7f
Port id: ether20
Time remaining: 93 seconds
System Name: MikroTik
System Description: MikroTik RouterOS 7.15beta9 (development) 2024-03-27 19:55:08 CRS326-24G-2S+
Management Address IPv4: 192.168.1.8
Management Address IPv6: fe80::d601:c3ff:fe3a:fb7f
Management Address IPv6: 2003:a:d59:3800:d601:c3ff:fe3a:fb7f
System Capabilities: BR
Enabled Capabilities: BR
Port Description: bridge/bonding2/ether20

I would like the Mikrotik to display full and correct information, too. This completely breaks the network map display in Observium for example.

Any hints welcome. I would have filed this as a bug right away but could not find a bug tracker for RouterOS - is there such a thing?

Kind regards,
Patrick
Bildschirmfoto 2024-04-08 um 18.49.39.png

2

Hi there,

There is a support portal: Support portal.

Regarding lldp and the sending interface, that should be the property interface-name.

[admin@********] > /ip/neighbor/print detail                           
 0 interface=wifi3,bridge mac-address=XX:XX:XX:XX:XX:XX identity="*****" platform="" version="" unpack=none age=3s interface-name="bridge/wifi3" system-description="MikroTik RouterOS 7.14.2 (stable) 2024-03-27 07:48:52 XXXXXXXXXXXXXXXX" system-caps=bridge,router system-caps-enabled=bridge,router discovered-by=lldp

Can you check in the terminal?

3

Testing with just OPNsense and the CRS326 it seems like the LLDP implementation is not to blame after all:

State in the Mikrotik:

[admin@MikroTik] > /ip/neighbor/print detail  
 0 interface=sfp-sfpplus1,bonding3,bridge address=192.168.1.1 address4=192.168.1.1 address6=2003:a:d59:3800::1 mac-address=F6:90:EA:00:CA:6A identity="opnsense" platform="" version="" 
   unpack=none age=21s ipv6=yes interface-name="ax0" system-description=" FreeBSD 13.2-RELEASE-p11 FreeBSD 13.2-RELEASE-p11 stable/24.1-n255007-1d6e165fb40 SMP amd64" 
   system-caps=bridge,wlan-ap,router,station-only system-caps-enabled=router discovered-by=lldp 

 1 interface=sfp-sfpplus2,bonding3,bridge address=192.168.1.1 address4=192.168.1.1 address6=2003:a:d59:3800::1 mac-address=F6:90:EA:00:CA:6A identity="opnsense" platform="" version="" 
   unpack=none age=21s ipv6=yes interface-name="ax1" system-description=" FreeBSD 13.2-RELEASE-p11 FreeBSD 13.2-RELEASE-p11 stable/24.1-n255007-1d6e165fb40 SMP amd64" 
   system-caps=bridge,wlan-ap,router,station-only system-caps-enabled=router discovered-by=lldp

It correctly identifies the two different peer interfaces, namely ax0 and ax1 on the OPNsense side. Great.

On OPNsense I get this:

-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface:    ax0, via: LLDP, RID: 1, Time: 0 day, 00:03:49
  Chassis:     
    ChassisID:    mac d4:01:c3:3a:fb:7f
    SysName:      MikroTik
    SysDescr:     MikroTik RouterOS 7.15beta9 (development) 2024-03-27 19:55:08 CRS326-24G-2S+
    MgmtIP:       192.168.1.8
    MgmtIface:    26
    MgmtIP:       fe80::d601:c3ff:fe3a:fb7f
    MgmtIface:    26
    MgmtIP:       2003:a:d59:3800:d601:c3ff:fe3a:fb7f
    MgmtIface:    26
    Capability:   Bridge, on
    Capability:   Router, on
  Port:        
    PortID:       ifname sfp-sfpplus1
    PortDescr:    bridge/bonding3/sfp-sfpplus1
    TTL:          120
-------------------------------------------------------------------------------
Interface:    ax1, via: LLDP, RID: 1, Time: 0 day, 00:03:50
  Chassis:     
    ChassisID:    mac d4:01:c3:3a:fb:7f
    SysName:      MikroTik
    SysDescr:     MikroTik RouterOS 7.15beta9 (development) 2024-03-27 19:55:08 CRS326-24G-2S+
    MgmtIP:       192.168.1.8
    MgmtIface:    26
    MgmtIP:       fe80::d601:c3ff:fe3a:fb7f
    MgmtIface:    26
    MgmtIP:       2003:a:d59:3800:d601:c3ff:fe3a:fb7f
    MgmtIface:    26
    Capability:   Bridge, on
    Capability:   Router, on
  Port:        
    PortID:       ifname sfp-sfpplus2
    PortDescr:    bridge/bonding3/sfp-sfpplus2
    TTL:          120
-------------------------------------------------------------------------------

So ax0 (OPNsense) is connected to sfp-sfpplus1 (Mikrotik) and ax1 to sfp-sfpplus2, respectively.

Then it’s probably the UI that is to blame for not delivering much useful information. The point of LLDP is of course “please tell me the ID of the port on the remote side”, so you can fix switched wirings and the like. The UI should at least report the remote port as the CLI does.

For some reason I cannot place inline attachments at the points in the text flow I want to place them in this forum software. So please refer to the attached images for the web UI neighbour display and the result via SNMP in Observium. The RouterOS is clearly not reporting the same information via SNMP compared to the one I get with /ip/neighbor/print detail.

Any ideas on how to proceed? The expected result is a true map of all low level layer 2 connections like e.g. a Cisco IOS switch would deliver.

Thanks and kind regards,
Patrick
Bildschirmfoto 2024-04-09 um 23.05.00.png
Bildschirmfoto 2024-04-09 um 23.05.10.png
Bildschirmfoto 2024-04-09 um 22.46.48.png

4

I tried a snmpwalk with the top of the LLDP OID tree and I get the info.

snmpwalk [...] -m MIKROTIK-MIB -m LLDP-MIB 192.168.2.1 1.0.8802.1.1.2

If you haven’t, can you download the Mikrotik MIB and add it to your tool?

https://mikrotik.com/download

5

Works the same here - I’ll take it to the Observium guys.

Thanks a lot, take care,
Patrick

6

Fixed in Observium. Thanks for your support.

7

Glad to hear it! Please mark this as solved if you get a chance.