...

...

...

Hi Flavio, As we know, if the bonding mode set to be 4(Dynamic link aggregation), it requires special switch configuration.

Not just that mode.

...

Do you mean that if we use libteam with teamd, we have to do some special switch configurations? That is what we plan to avoid.

Depending on the mode you choose, yes.  Active-backup mode, for instance, doesn't require switch config.

...

Because for some switch(eg, H3C S5120-52C- EI ), the number of aggregate ports has a upper limit, and there will be some ports can't be aggregated in the switch.

That's indeed a problem.  The only way to work around this but keeping the same mode is to use different switch to accomplish unique paths to the destination.

eth0 ---> switch 0 ----> eth0 System A  eth1 ---> switch 1 ----> eth1 System B          eth2 ---> switch 2 ----> eth2

The above setup doesn't care that system A's eth{0,1,2} have the same MAC address because they are in isolated physical paths. I never tried that myself though.

Hi Flavio, The net topo we have as below: The eth1-4 connect to the same one switch, and for teamd with loadbalance mode, p1/2 will have the same MAC(changed by libteam), and p3/4 will have the same MAC.

+------------------------------+ | switch | +------------------------------+ p1 p2 p3 p4 | | | | | | | | eth1 eth2 eth1 eth2 | | | | +-----+ +------+ A | | B +------+ +-------+

As we know, for bonding driver, the 802.3ad mode requires that the switch have the appropriate ports configured as an 802.3ad aggregation, what about libteam with loadbalance mode?

Can you show me some config to do for the switch with loadbalance mode? And what about lacp mode?

Thanks, Best Wishes, Wenhua