Looking to see if there's actual support yet in RouterOS for ESI on an active/active LAG. It's odd looking in the official documentation and only seeing references to Arista which is a 3rd party vendor:
But this looks like AI slop or some secret sauce code as there is no CLI syntax for /interface ethernet-segment in RouterOS 7.25.1 stable.
So what is the conclusion here? No ESI-LAG support in RouterOS for dual-homed hosts? EVPN is limited to single-homed hosts in non-VNI deployment scenarios?
Currently ROS cannot be leaf node that forms ESI LAG, this feature is currently in development. Example in the manual shows an example that RouterOS can be used in setups where other vendors are used as ESI LAG nodes, receives their updates and uses them successfully.
It doesn’t support MPLS-EVPN signaling, lacks L3 support, and the BGP filters for this type of route still have a long way to go.
Up until version 7.25, it only handled EVPN Type 4 routes—essentially acting as a "pipe" to extend a VLAN as an overlay across an IP underlay.
Over time, the MAC-learning functionality has gradually improved...
VLAN-to-VXLAN bindings—even for Type 4 routes—are now supposedly supported [1].
Version 7.25 also introduced Type 2 routes, though I haven’t dared to try those out yet.
But there’s still no sign of Type 5 routes!
I’d be happy to see L3VPN over EVPN-VXLAN.
If anyone is expecting "anycast gateway" support in the near term, I’d suggest lowering those expectations.
And honestly, given all the reports of issues with standard MC-LAG (ICCP), I highly doubt that EVPN is mature enough to support ESI-LAG without running into some unpleasant surprises.
[1] I have an open support ticket, SUP-224431 – "VXLan not mapping remote MAC on one side." I haven’t even received an acknowledgment—not even a simple "ACK, we’ve received your ticket and will look into it."