Thank you, this is a useful suggestion.
All four MLAG bridges currently have:
mlag-lacp-fallback=yes
mlag-init-delay=1m
We will test mlag-lacp-fallback=no on all four switches during the maintenance window on Saturday.
Our issue is not limited to a primary reboot. It can also be triggered by disabling or enabling one member interface while both MLAG peers remain operational.
The environment is relatively small:
- 4x CRS326-24S+2Q+RM;
- approximately 360-500 FDB entries;
- approximately 11 VLANs;
- no large VLAN ranges;
- L3 hardware offloading disabled;
- bridge hardware offload active.
During one controlled test, the FDB count changed as follows:
499 -> 493 -> 417 -> 395 -> 84
Unrelated MAC entries moved to the MLAG peer-port, one peer reached 100% CPU, and the entire Layer 2 domain experienced severe packet loss.
After upgrading to RouterOS 7.25.1, AE1_Interconnect was initially correctly detected as non-edge on all four nodes. However, after multiple member link disable/enable operations, the interconnect on one node was again operationally detected as edge=yes, although its configured value remained edge=auto.
This was followed by severe packet loss and network instability.
We have stopped further testing during production hours. During the maintenance window on Saturday, we will:
- test mlag-lacp-fallback=no on all four switches;
- reproduce the issue using controlled member link changes and switch reboots;
- collect /tool profile output;
- monitor bridge, RSTP, LACP and FDB state on both peers;
- generate supout.rif files while the issue is active.
At this point, we cannot confirm whether mlag-lacp-fallback is related to the incorrect edge-port state or whether these are two separate symptoms.
I will report back after the Saturday maintenance window.
UPDATE
Additional historical information:
A similar stability problem was also present on an earlier RouterOS release 7.24 or 7.25, but the behaviour was different.
On the earlier version, CPU usage increased to approximately 40% on all four switches. None of the switches reached 100% CPU, but RSTP appeared to be continuously reconverging and the entire Layer 2 domain experienced severe instability and packet loss.
Interestingly, disabling and enabling a seemingly random aggregation interface would sometimes restore normal operation.
At that time, the problem did not look like CPU exhaustion. It appeared more closely related to RSTP state, forwarding behaviour or MAC learning across the MLAG topology.
On RouterOS 7.25.1, the BPDU and edge-port behaviour initially improved, but the failure now appears more CPU-intensive: one MLAG peer can reach 100% CPU while the FDB is globally flushed and rebuilt.
We do not yet know whether this is the same underlying MLAG reconvergence issue presenting differently between RouterOS versions, or two separate problems.
To clarify, this is not a temporary CPU spike during FDB reconstruction. Once the failure is triggered, one MLAG peer reaches 100% CPU and remains at 100%, while the network stays severely degraded. Flapping an aggregation interface may restore normal operation, but this is inconsistent and does not always work.