ad_select Specifies the 802.3ad aggregation selection logic to use. The possible values and their effects are: stable or 0 The active aggregator is chosen by largest aggregate bandwidth. Reselection of the active aggregator occurs only when all slaves of the active aggregator are down or the active aggregator has no slaves. This is the default value. bandwidth or 1 The active aggregator is chosen by largest aggregate bandwidth. Reselection occurs if: - A slave is added to or removed from the bond - Any slave's link state changes - Any slave's 802.3ad association state changes - The bond's administrative state changes to up count or 2 The active aggregator is chosen by the largest number of ports (slaves). Reselection occurs as described under the "bandwidth" setting, above.
The way this is written, I can't tell if a single bond can contain more than one aggregator, or not! If the bonding module is smart enough to sort out more than one aggregation within a bond, I'm golden!
Let me simplify my drawing from over there:
____________ eth1 ________ eth2 ____________ | switch 1 |========| host |--------| switch 2 | ------------ eth3 -------- ------------
These switches do not do 802.3ad across switches. So, if I put all three interfaces into a single 802.3ad bond, do I get two aggregators? One containing eth1 & eth3, the other just holding eth2? Conceivably, the LACP signals between the host and the switches would be enough to do that. I just don't know if that capability is actually built in.
Anyone? Anyone? Can I get two aggregators out of a single interface bond?