On 5/23/19 5:31 PM, Jay Vosburgh wrote:
However, the logic in LACP will attach every slave of the bond
to an aggregator. If one or more slaves are connected to a specific
LACP peer, they will aggregate together. If any slave is connected to a
non-LACP peer, it will aggregate as an "individual" port.
When bonding's LACP mode selects the best aggregator to use,
"non-individual" (i.e., connected to a LACP peer) ports are preferred,
but if no such ports are available, an individual port is selected as
the active aggregator. The precise logic is found in the
ad_agg_selection_test() function [1].
If what you've got works for you, then that's great, but I
suspect it would still work if all of the interfaces were in a single
802.3ad bond without the nesting.
-J
Ah, hadn't considered LACP mode would accept non-LACP interfaces. I'll
chase this.
Thanks.
