Yes, you are right. The incorrect behavior is due to we don't setup the
lacpdu of switch correctly.
The bonding driver is correct. Thanks for your comment!
I do not believe so.
IEEE 802.3 section 43.3.9 states, in part,
"Links that are not successful candidates for aggregation (e.g.,
links th
>After the setting, I cat the proc entry and got the following information
[...]
>802.3ad info
>LACP rate: slow
>Active Aggregator Info:
>Aggregator ID: 1
>Number of ports: 2
>Actor Key: 17
>Partner Key: 1
>Partner Mac Address: 00:00:00:00:00:00
[...]
>The b
I wish to be personally CC'ed the answers/comments posted to the list in
response to my posting.
I have 2 ports(eth0, eth1) in my device. I use kernel(2.6.23) bonding driver
v3.1.3 (June 13, 2007) to bond 2 ports to one aggregator and use the
following commands to setup the environment:
insmo
3 matches
Mail list logo