The larger switches from Aruba (HPE) can be interconnected to form a virtual switch, so that the failure of an entire switch is also compensated for when using LACP. Instead of just one link as usual. At HP the whole thing is called VFS, can the Mikrotik switches also do this?
Here is a short description of the whole thing.
Thanks.
Mikrotik supports MLAG. Would that fit at least minimum requirements?
BTW, this doesn’t seem to have anything to do with topic of this forum section (virtualization) which is running ROS on virtual machines.
Hi mkx,
for an minimal setup it will works, but not for critical setup’s, which needs 3 devices.
As the MLAG documentation mentions a limitation to 2 devices. But otherwise it is quite similar to VSF,
decentralised ports take over the data exchange between the devices and the end devices can be connected to the switches via LACP.
Unfortunately, virtualisation can be defined quite broadly.
In this case, the configuration no longer takes place on the physical switch but on the virtual switch which is spanned over the physical switch. (At least in the world of HPE/Aruba)
Therefore it is also a kind of virtualisation. The only difference is that the switch itself becomes virtual, not the operating systems.
This kind of virtualization doesn’t exist (yet) in MT world.
But for small applications where 1 out of 3 is not prescribed, I can certainly offer this to my customers.
In any case, I’ll keep an eye on whether the restrictions will be lifted one day.
Thanks for the information.
Do not expect this feature to arrive in the MT world “soon”. From the spec-sheets. This feature is only available in higher end $$$$ switches.
Of you can accept managing the switches individually. You can archive the required redundancy with a different architecture. – If LAG is required on the client host. This is probably not feasible. 
If you can do routing the client host. You have room for using a routed architecture (Layer 3 based) instead of a switched architecture (Layer 2 based).