[Bug 482419] Re: 802.3ad interface bonding fails if started too early
Stéphane Graber
stgraber at stgraber.org
Tue Jun 7 18:25:46 UTC 2011
With the fix applied, I now get:
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:65535
MAC Address: 00:c0:9f:3f:3b:2c
Oper Key: 17
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: 65535
system mac addr: 00:c0:9f:3f:3b:2c
port Admin key: 0
port Oper key: 17
port Oper number: 1
port Admin priority: 0
port Oper priority: 255
port Oper timeout: SHORT
LACP Activity: ACTIVE
Aggregation: AGGREGATABLE
synchronization: TRUE
collecting: TRUE
distributing: TRUE
expired: FALSE
g12 LACP statistics:
LACP Pdus sent: 1055
LACP Pdus received: 77
g12 LACP Protocol State:
LACP State Machines:
Receive FSM: Current State
Mux FSM: Collecting Distributing State
Periodic Tx FSM: Fast 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: 1
current while timer: 79
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: up
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
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 17
Partner Key: 28
Partner Mac Address: 00:14:22:66:25:10
Slave Interface: eth0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:c0:9f:3f:3b:2c
Aggregator ID: 1
Slave Interface: eth1
MII Status: down
Link Failure Count: 0
Permanent HW addr: 00:c0:9f:3f:3b:2d
Aggregator ID: 2
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifenslave-2.6 in Ubuntu.
https://bugs.launchpad.net/bugs/482419
Title:
802.3ad interface bonding fails if started too early
Status in “ifenslave-2.6” package in Ubuntu:
Fix Released
Status in “ifenslave-2.6” source package in Lucid:
Triaged
Status in “ifenslave-2.6” package in Debian:
Unknown
Bug description:
Impact: see original report below
How the patch fixes it: pre-up sets up master before attempting to enslave and setup slaves
Patch: https://bugs.edge.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/482419/+attachment/1455658/+files/ifenslave-2.6-sru.diff
Reproducing: http://ubuntuforums.org/showpost.php?p=8285696&postcount=3
Regression potential: none known
== Original report ==
802.3ad bonding configurations that formerly worked on jaunty are now failing on startup under karmic. After the system has started, restarting networking will bring the bond up correctly. This only applies to bond_mode 4 / 802.3ad, I've tested that switching to bond_mode 0 corrects the issue, and other users experiencing this bug all were using bond_mode 4 as well.
dmesg output fills with "bonding: bond0: Warning: Found an
uninitialized port", even after the system starts up and the port
should be "initialized"
It appears to occur on multiple drivers (bnx2, e1000 confirmed).
One initially wants to blame the startup ordering due to the switch to
upstart, but I believe it is an edge case that hasn't been seen before
because we haven't been starting up so quickly that the hardware
hasn't had time to fully initialized.
Configuration and output from multiple users is in this thread:
http://ubuntuforums.org/showthread.php?p=8311572
More information about the foundations-bugs
mailing list