[Bug 482419] Re: 802.3ad interface bonding fails if started too early

[nutznboltz]

@Pete Ashdown yes, there is a workaround.

First one of the things that goes wrong is that ethernet media
autoconfiguration takes up time and causes network interfaces to take so
long to come up there is the possibility that that will interfere with
bonding configuring.  You can hardcode the media speed/duplex/etc on the
switch and in /etc/network/interfaces

auto eth0
    iface eth0 inet manual
    media 1000baseTx-FD

for each eth0 device to be bonded.

Next you can get bonding to work by using pre-up, etc. in
/etc/network/interfaces like this:

auto bond0
iface bond0 inet manual
    pre-up modprobe bonding mode=802.3ad ad_select=bandwidth downdelay=400 miimon=100 lacp_rate=0 max_bonds=2 ; ifconfig bond0 up ;  ifconfig eth0 up ; ifconfig eth1 up
    post-up ifenslave bond0 eth0 eth1
    pre-down ifenslave -d bond0 eth0 eth1
    post-down ifconfig eth0 down ; ifconfig eth1 down ; ifconfig bond0 down

-- 
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