Bonds on a bridge acting like hub ports.

RouterOS General
1

I have two CRS326-24G-2S+ switches connected together to act as a core pair using MLAG. They are running 7.6 as it seems anything past this version is broken for MLAG.
On the bridges of each switch I have 8 bonds and 4 normal ports. The 4 normal ports are not lagged. They go to storage devices which use MPIO.
I have found that any inbound traffic on one bond egresses on all other bonds on that switch. Occasionally, LACP will switch over the egress port of one bond to the second switch, but the traffic will then flow through the ICCP link and out to through the bond on the other switch. Meanwhile the indpendent ports behave normally.

Here is a snapshot of the system. A server is doing a backup check from a device connected to the interface bond-to-E-SW01. The server is behind the interface bond-to-dell. However, the traffic is also egressing through all the other bonds. If the NAS switches to its second LACP port, the exact same scenario happens on the other Mikrotik switch.
Interfaces.png
Here is the bridge port layout.
bridge-port.png
and bridge vlan
bridge-vlan.png
The bridge is set to use rstp
LACP is working fine on all pairs. Remote swtiches (Cisco and Dell) are all reporting active LACP partnerships in normal status. The network is working, but performance is impacted by large traffic on one bond using up bandwidth on other bonds. I can’t see any errors, no stp log entries (stp logging is enabled), etc.

I would love to upgrade the routers, but I have not seen any information regarding MLAG which fails since 7.7

2

Why don’t you post your configuration export instead of stupid screenshots which are virtually useless to most people?

3

OK.

It’s a bit hard to show what is happening without “stupid screenshots” though.

/interface ethernet
set [ find default-name=ether2 ] name=ether2-bond-Aruba-Core
set [ find default-name=ether9 ] l2mtu=9092 mtu=9000 name=ether9-To-SAN
set [ find default-name=ether10 ] l2mtu=9092 mtu=9000 name=ether10-To-DRHV1
set [ find default-name=ether11 ] l2mtu=9092 mtu=9000 name=ether11-To-DRHV2
set [ find default-name=ether12 ] l2mtu=9092 mtu=9000 name=ether12-To-DR-HV3
set [ find default-name=ether13 ] name=ether13-To-ARM-SW2-13
set [ find default-name=ether14 ] name=ether14-To-ARM-SW2-14
set [ find default-name=ether17 ] name=ether17-bond-E-SW01
set [ find default-name=ether18 ] name=ether18-bond-E-SW02
set [ find default-name=ether19 ] name=ether19-bond-E-SW03
set [ find default-name=ether20 ] name=ether20-bond-E-SW04
set [ find default-name=ether21 ] name=ether21-bond-E-SW05
set [ find default-name=ether22 ] name=ether22-bond-E-SW06
set [ find default-name=sfp-sfpplus1 ] l2mtu=9092 mtu=9000 name=sfp-sfpplus1-ARM-SW2
set [ find default-name=sfp-sfpplus2 ] name=sfp-sfpplus2-Dell-SW2-Eth6
/interface bonding
add mlag-id=11 mode=802.3ad name=bond-to-Aruba-Core slaves=ether2-bond-Aruba-Core transmit-hash-policy=layer-2-and-3
add mlag-id=10 mode=802.3ad name=bond-to-Dell slaves=sfp-sfpplus2-Dell-SW2-Eth6 transmit-hash-policy=layer-3-and-4
add mlag-id=21 mode=802.3ad name=bond-to-E-SW01 slaves=ether17-bond-E-SW01
add mlag-id=22 mode=802.3ad name=bond-to-E-SW02 slaves=ether18-bond-E-SW02
add mlag-id=23 mode=802.3ad name=bond-to-E-SW03 slaves=ether19-bond-E-SW03
add mlag-id=24 mode=802.3ad name=bond-to-E-SW04 slaves=ether20-bond-E-SW04
add mlag-id=25 mode=802.3ad name=bond-to-E-SW05 slaves=ether21-bond-E-SW05
add mlag-id=26 mode=802.3ad name=bond-to-E-SW06 slaves=ether22-bond-E-SW06
set bridge=bridge-Mlag peer-port=sfp-sfpplus1-ARM-SW2
/interface bridge port
add bridge=bridge-Mlag interface=sfp-sfpplus1-ARM-SW2 pvid=99
add bridge=bridge-Mlag interface=bond-to-Dell
add bridge=bridge-Mlag interface=bond-to-Aruba-Core
add bridge=bridge-Mlag interface=bond-to-E-SW01
add bridge=bridge-Mlag interface=ether9-To-SAN pvid=50
add bridge=bridge-Mlag interface=ether10-To-DRHV1 pvid=50
add bridge=bridge-Mlag interface=ether11-To-DRHV2 pvid=50
add bridge=bridge-Mlag interface=ether12-To-DR-HV3 pvid=50
add bridge=bridge-Mlag interface=bond-to-E-SW02
add bridge=bridge-Mlag interface=bond-to-E-SW03
add bridge=bridge-Mlag interface=bond-to-E-SW04
add bridge=bridge-Mlag interface=bond-to-E-SW05
add bridge=bridge-Mlag interface=bond-to-E-SW06
/interface bridge vlan
add bridge=bridge-Mlag tagged=sfp-sfpplus1-ARM-SW2 vlan-ids=1
add bridge=bridge-Mlag tagged=“sfp-sfpplus1-ARM-SW2,bond-to-Dell,bond-to-Aruba-Core,*3A,*3D,*3C,bond-to-E-SW01,bond-to-E-S
W02,bond-to-E-SW03,bond-to-E-SW04,bond-to-E-SW05,bond-to-E-SW06” vlan-ids=62
add bridge=bridge-Mlag tagged=“sfp-sfpplus1-ARM-SW2,bond-to-Dell,bond-to-Aruba-Core,*3A,*3D,*3C,bond-to-E-SW01,bond-to-E-S
W02,bond-to-E-SW03,bond-to-E-SW04,bond-to-E-SW05,bond-to-E-SW06” vlan-ids=63
add bridge=bridge-Mlag tagged=“sfp-sfpplus1-ARM-SW2,bond-to-Dell,bond-to-Aruba-Core,*3A,*3D,*3C,bond-to-E-SW01,bond-to-E-S
W02,bond-to-E-SW03,bond-to-E-SW04,bond-to-E-SW05,bond-to-E-SW06” vlan-ids=64
add bridge=bridge-Mlag tagged=“sfp-sfpplus1-ARM-SW2,bond-to-Dell,bond-to-Aruba-Core,*3A,*3D,*3C,bond-to-E-SW01,bond-to-E-S
W02,bond-to-E-SW03,bond-to-E-SW04,bond-to-E-SW05,bond-to-E-SW06” vlan-ids=65
add bridge=bridge-Mlag tagged=“sfp-sfpplus1-ARM-SW2,bond-to-Dell,bond-to-Aruba-Core,*3A,*3D,*3C,bond-to-E-SW01,bond-to-E-S
W02,bond-to-E-SW03,bond-to-E-SW04,bond-to-E-SW05,bond-to-E-SW06” vlan-ids=66
add bridge=bridge-Mlag tagged=“sfp-sfpplus1-ARM-SW2,bond-to-Dell,bond-to-Aruba-Core,*3A,*3D,*3C,bond-to-E-SW01,bond-to-E-S
W02,bond-to-E-SW03,bond-to-E-SW04,bond-to-E-SW05,bond-to-E-SW06” vlan-ids=162
add bridge=bridge-Mlag tagged=“sfp-sfpplus1-ARM-SW2,bond-to-Dell,bond-to-Aruba-Core,*3A,*3C,*3D,bond-to-E-SW01,bond-to-E-S
W02,bond-to-E-SW03,bond-to-E-SW04,bond-to-E-SW05,bond-to-E-SW06” vlan-ids=50

4

The answer to this question was that there was a bug in the bridge software, which is fixed since 7.10.2