Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
802.3ad info
LACP rate: slow
Active Aggregator Info:
Aggregator ID: 2
Number of ports: 4
Actor Key: 9
Partner Key: 112
Partner Mac Address: 00:1b:0d:66:04:00
Slave Interface: eth0
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:26:55:33:c1:5e
Aggregator ID: 3
Slave Interface: eth1
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:26:55:33:c1:60
Aggregator ID: 3
Slave Interface: eth2
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:26:55:33:c1:62
Aggregator ID: 3
Slave Interface: eth3
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:26:55:33:c1:64
Aggregator ID: 3
Slave Interface: eth4
MII Status: up
Link Failure Count: 7
Permanent HW addr: 00:26:55:d5:56:a8
Aggregator ID: 2
Slave Interface: eth5
MII Status: up
Link Failure Count: 7
Permanent HW addr: 00:26:55:d5:56:a9
Aggregator ID: 2
Slave Interface: eth6
MII Status: up
Link Failure Count: 9
Permanent HW addr: 00:26:55:d5:56:aa
Aggregator ID: 2
Slave Interface: eth7
MII Status: up
Link Failure Count: 5
Permanent HW addr: 00:26:55:d5:56:ab
Aggregator ID: 2
root@pr1lbackup1:/opt/nsr#
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
_
2010-04-21 11:00:35 PDT
Running CentOS 5.4 with bonding v3.4.0.
Setup bond0 with 8x 1GbE ports on two switches (4 ports on each switch) running mode 4 (802.3ad).
Wondering if it is possible to manually select active aggregator and how to do it._
No, there is no facility to manually select the active aggregator. There is some tuning available for the selection algorithm, though, via the ad_select option:
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 bandwidth and count selection policies permit failover of
802.3ad aggregations when partial failure of the active aggregator
occurs. This keeps the aggregator with the highest availability
(either in bandwidth or in number of ports) active at all times.
This option was added in bonding version 3.4.0.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Running CentOS 5.4 with bonding v3.4.0.
Setup bond0 with 8x 1GbE ports on two switches (4 ports on each switch) running mode 4 (802.3ad).
Wondering if it is possible to manually select active aggregator and how to do it.
root@pr1lbackup1:/opt/nsr# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
802.3ad info
LACP rate: slow
Active Aggregator Info:
Aggregator ID: 2
Number of ports: 4
Actor Key: 9
Partner Key: 112
Partner Mac Address: 00:1b:0d:66:04:00
Slave Interface: eth0
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:26:55:33:c1:5e
Aggregator ID: 3
Slave Interface: eth1
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:26:55:33:c1:60
Aggregator ID: 3
Slave Interface: eth2
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:26:55:33:c1:62
Aggregator ID: 3
Slave Interface: eth3
MII Status: up
Link Failure Count: 2
Permanent HW addr: 00:26:55:33:c1:64
Aggregator ID: 3
Slave Interface: eth4
MII Status: up
Link Failure Count: 7
Permanent HW addr: 00:26:55:d5:56:a8
Aggregator ID: 2
Slave Interface: eth5
MII Status: up
Link Failure Count: 7
Permanent HW addr: 00:26:55:d5:56:a9
Aggregator ID: 2
Slave Interface: eth6
MII Status: up
Link Failure Count: 9
Permanent HW addr: 00:26:55:d5:56:aa
Aggregator ID: 2
Slave Interface: eth7
MII Status: up
Link Failure Count: 5
Permanent HW addr: 00:26:55:d5:56:ab
Aggregator ID: 2
root@pr1lbackup1:/opt/nsr#
_
2010-04-21 11:00:35 PDT
Running CentOS 5.4 with bonding v3.4.0.
Setup bond0 with 8x 1GbE ports on two switches (4 ports on each switch) running mode 4 (802.3ad).
Wondering if it is possible to manually select active aggregator and how to do it._
No, there is no facility to manually select the active aggregator. There is some tuning available for the selection algorithm, though, via the ad_select option:
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 bandwidth and count selection policies permit failover of
802.3ad aggregations when partial failure of the active aggregator
occurs. This keeps the aggregator with the highest availability
(either in bandwidth or in number of ports) active at all times.
This option was added in bonding version 3.4.0.
It seems that ad_select is available on v3.5.0 but not available on v3.4.0.
On bonding v3.4.0 the failover will happen only when all ports in the active aggregator fails.
Also the failover take 10-20 seconds to finish.