On 08. 08. 2019 11:42, Strahil wrote:
LACP supports works with 2 switches, but if you wish to aggregate all links - you need switch support (high-end hardware).
Best Regards, Strahil Nikolov
I am aware of that. That's why my idea was to use bond1 (LACP) on eth1+2 on switch1 and bond2 (LACP) on eth3+4 on switch2 and then team together bond1 + bond2. With this config theoretically I should get bonding spanned over two switches. Technically it worked, redundancy and aggregation. The problem was deploying self-hosted engine, because the script was unable to configure management network. If I use bonding spanned over two switches as you suggest, based on documentation https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/htm... my options are: - Mode 2 (XOR policy) - Mode 5 (adaptive transmit load-balancing policy): no use of bridges - Mode 6 (adaptive load-balancing policy): same limitation of mode 5 Basically only Mode 2 looks usable for us. Regards, Mitja