With the current package, I get the issue described in this bug report,
with the following output:
Switch:
sw06# show lacp port-channel 4
Port-Channel ch4
Port Type Gigabit Ethernet
Attached Lag id:
Actor
System Priority:1
MAC Address: 00:14:22:66:25:10
Admin Key: 28
Oper Key: 28
Partner
System Priority:0
MAC Address: 00:00:00:00:00:00
Oper Key: 0
sw06# show lacp ethernet g11
g11 LACP parameters:
Actor
system priority: 1
system mac addr: 00:14:22:66:25:10
port Admin key: 28
port Oper key: 28
port Oper number: 11
port Admin priority: 1
port Oper priority: 1
port Admin timeout: LONG
port Oper timeout: LONG
LACP Activity: ACTIVE
Aggregation: AGGREGATABLE
synchronization: FALSE
collecting: FALSE
distributing: FALSE
expired: FALSE
Partner
system priority: 65535
system mac addr: 00:c0:9f:3f:3b:2c
port Admin key: 0
port Oper key: 17
port Oper number: 2
port Admin priority: 0
port Oper priority: 255
port Oper timeout: SHORT
LACP Activity: ACTIVE
Aggregation: INDIVIDUAL
synchronization: FALSE
collecting: TRUE
distributing: TRUE
expired: FALSE
g11 LACP statistics:
LACP Pdus sent: 252
LACP Pdus received: 27
g11 LACP Protocol State:
LACP State Machines:
Receive FSM: Port Disabled State
Mux FSM: Detached State
Periodic Tx FSM: No Periodic State
Control Variables:
BEGIN: FALSE
LACP_Enabled: TRUE
Ready_N: FALSE
Selected: UNSELECTED
Port_moved: FALSE
NNT: FALSE
Port_enabled: FALSE
Timer counters:
periodic tx timer: 0
current while timer: 0
wait while timer: 0
sw06# show lacp ethernet g12
g12 LACP parameters:
Actor
system priority: 1
system mac addr: 00:14:22:66:25:10
port Admin key: 28
port Oper key: 28
port Oper number: 12
port Admin priority: 1
port Oper priority: 1
port Admin timeout: LONG
port Oper timeout: LONG
LACP Activity: ACTIVE
Aggregation: AGGREGATABLE
synchronization: TRUE
collecting: TRUE
distributing: TRUE
expired: FALSE
Partner
system priority: 0
system mac addr: 00:00:00:00:00:00
port Admin key: 0
port Oper key: 0
port Oper number: 0
port Admin priority: 0
port Oper priority: 0
port Oper timeout: LONG
LACP Activity: PASSIVE
Aggregation: AGGREGATABLE
synchronization: TRUE
collecting: FALSE
distributing: FALSE
expired: FALSE
g12 LACP statistics:
LACP Pdus sent: 816
LACP Pdus received: 55
g12 LACP Protocol State:
LACP State Machines:
Receive FSM: Defaulted State
Mux FSM: Collecting Distributing State
Periodic Tx FSM: Slow Periodic State
Control Variables:
BEGIN: FALSE
LACP_Enabled: TRUE
Ready_N: FALSE
Selected: SELECTED
Port_moved: FALSE
NNT: FALSE
Port_enabled: TRUE
Timer counters:
periodic tx timer: 5
current while timer: 0
wait while timer: 0
And on the server:
Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2+3 (2)
MII Status: down
MII Polling Interval (ms): 10
Up Delay (ms): 0
Down Delay (ms): 0
802.3ad info
LACP rate: fast
Aggregator selection policy (ad_select): stable
bond bond0 has no active aggregator
Slave Interface: eth0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:c0:9f:3f:3b:2c
Aggregator ID: N/A
Slave Interface: eth1
MII Status: down
Link Failure Count: 1
Permanent HW addr: 00:c0:9f:3f:3b:2d
Aggregator ID: N/A
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/482419
Title:
802.3ad interface bonding fails if started too early
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
