Re: 802.3ad bonding aggregator reselection

Veli-Matti Lintu wrote: [...] >> I don't see an issue with the above behavior when ad_select is >> set to the default value of "stable"; bonding does reselect a new >> aggregator when all links fail, and it appears to follow the standard. > >In my testing

Re: 802.3ad bonding aggregator reselection

2016-06-22 3:49 GMT+03:00 Jay Vosburgh : > > Veli-Matti Lintu wrote: > [...] The ports are configured in switch settings (HP Procurve 2530-48G) in same trunk group (TrkX) and trunk group type is set as LACP.

Re: 802.3ad bonding aggregator reselection

Veli-Matti Lintu wrote: [...] >>>The ports are configured in switch settings (HP Procurve 2530-48G) in >>>same trunk group (TrkX) and trunk group type is set as LACP. >>>/proc/net/bonding/bond0 also shows that the three ports belong to same >>>aggregator and

Re: 802.3ad bonding aggregator reselection

2016-06-21 18:46 GMT+03:00 Jay Vosburgh : > Veli-Matti Lintu wrote: > >>2016-06-20 17:11 GMT+03:00 zhuyj : >>> 5. Switch Configuration >>> === >>> >>> For this section, "switch" refers to

Re: 802.3ad bonding aggregator reselection

Veli-Matti Lintu wrote: >2016-06-20 17:11 GMT+03:00 zhuyj : >> 5. Switch Configuration >> === >> >> For this section, "switch" refers to whatever system the >> bonded devices are directly connected to (i.e., where the

Re: 802.3ad bonding aggregator reselection

2016-06-20 17:11 GMT+03:00 zhuyj : > 5. Switch Configuration > === > > For this section, "switch" refers to whatever system the > bonded devices are directly connected to (i.e., where the other end of > the cable plugs into). This may be an actual

Fwd: 802.3ad bonding aggregator reselection

Hello, I have been trying to get the bonding driver working with multiple aggregators with two switches in mode=802.3ad to handle failing links properly. The goal is to have always the best possible bonded link in use if one or physical links fail. The bonding documentation describes that