Bonding still broken for bnx2 in Jaunty

[Robstarusa]

My config is as follows (eth0 is onboard/bnx2)
My /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.1.13.163
  netmask 255.255.255.0
  gateway 10.1.13.1
  post-up ifenslave bond0 eth1 eth2
  pre-down ifenslave -d bond0 eth1 eth2
=================================
When eth1/eth2 are pro/1000 MT nics, everything works great
When eth1/eth2 are 2 bnx2 nics, I can't pass any traffic.

System Info:
=================================
lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
=================================
apt-cache policy linux
linux:
  Installed: (none)
  Candidate: 2.6.28.11.15
  Version table:
     2.6.28.11.15 0
        500 http://us.archive.ubuntu.com jaunty/restricted Packages
=================================

[cmeiklejohn (cmeik)]

I'm having the same issue with Intrepid and Jaunty.

I was having the issue with Intrepid, so I disabled bonding and upgraded to Jaunty with a using a single NIC, and now I have the same issue when attempting to bond.

[cmeiklejohn (cmeik)]

Actually, this was not working for me with the following config:

auto bond0
iface bond0 inet static
    address 10.0.1.27
    netmask 255.255.0.0
    network 10.0.0.0
    gateway 10.0.1.1
    slaves eth0 eth1

But, by adding these additional options, and rebooting, now the link is up for me:

auto bond0
iface bond0 inet static
    address 10.0.1.27
    netmask 255.255.0.0
    network 10.0.0.0
    gateway 10.0.1.1
    broadcast 10.0.255.255
    bond_mode 4
    bond_miimon 100
    bond_downdelay 200
    bond_updelay 200
    slaves eth0 eth1

Maybe the bond_updelay is necessary for this to work correctly?

[Jeremy Foshee (jeremyfoshee)]

Hi Robstarusa,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 366177

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Robstarusa (rob-naseca)]

I have tried Lucid on my laptop and after the first update I was left at a black scren....when Lucid finalizes, I'll try it again & then be able to report if this is still an issue.

[Øystein Viggen (oysteivi)]

With bnx2 interfaces on Ubuntu 10.04 64-bit:

In a file called /etc/modprobe.d/ip-failover (that we put there ourselves):

Does not work:
options bonding mode=6 miimon=100 downdelay=200 updelay=200 max_bonds=2

Works:
options bonding mode=1 miimon=100 downdelay=200 updelay=200 max_bonds=2

mode=6 works on Ubuntu 8.04 32-bit on the same hardware and RHEL 5.5 64-bit on the same hardware.

..so for people with this problem, swapping to mode=1 (active-backup) should be a functional workaround if you just use bonding for redundancy and don't really need the extra throughput from many interfaces.

(Where I work we have 52 fairly new DELL-servers that all use bnx2, so I'll venture a guess that this network controller is fairly common).

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]