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

[Stéphane Graber]

Hmm, I don't seem to be able to reproduce your problem.

I currently use:

stgraber at halla:~$ cat /etc/network/interfaces 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto bond0
iface bond0 inet static
    address 10.145.15.20
    netmask 255.255.255.0
    gateway 10.145.15.1

    slaves eth0 eth1

    bond_mode 6
    bond_miimon 100
    bond_updelay 200
    bond_downdelay 200

and I get the following in my dmesg:

[    7.151348] Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008)
[    7.151354] bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
[    7.155412] bonding: bond0: setting mode to balance-alb (6).
[    7.155520] bonding: bond0: Setting MII monitoring interval to 100.
[    7.155610] bonding: bond0: Setting up delay to 200.
[    7.155686] bonding: bond0: Setting down delay to 200.
[    7.160557] bonding: bond0: doing slave updates when interface is down.
[    7.160568] bonding: bond0: Adding slave eth0.
[    7.160573] bonding bond0: master_dev is not up in bond_enslave
[    7.172556] bonding: bond0: enslaving eth0 as an active interface with a down link.
[    7.197647] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[    7.198734] bonding: bond0: doing slave updates when interface is down.
[    7.198741] bonding: bond0: Adding slave eth1.
[    7.198744] bonding bond0: master_dev is not up in bond_enslave
[    7.209650] bonding: bond0: enslaving eth1 as an active interface with a down link.
[    7.214369] bonding: bond0: link status up for interface eth0, enabling it in 0 ms.
[    7.214539] ADDRCONF(NETDEV_UP): bond0: link is not ready
[    7.214550] bonding: bond0: link status definitely up for interface eth0.
[    7.214556] bonding: bond0: making interface eth0 the new active one.
[    7.214956] bonding: bond0: first active interface up!
[    7.215301] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[   18.148005] bond0: no IPv6 routers present


Did I miss something ?

-- 
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:
  Fix Released
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/482419/+subscriptions