[Bug 889423] Re: 802.3ad bonding not configured correctly
Albert Chin
889423 at bugs.launchpad.net
Fri Dec 2 02:58:59 UTC 2011
Looking at the boot sequence:
Begin: Running /[ 40.126206] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
[about 1 minute delay]
fsck from util-linux 2.19.1
fsck from util-linux 2.19.1
/dev/mapper/trunks-lv_root: clean, 356330/1954064 files, 2538052/7812096 blocks
/dev/sdb1 has been mounted 27 times without being checked, check forced.
/dev/sdb1: 237/62248 files (0.8% non-contiguous), 73465/248832 blocks
* Starting configure network device security [ OK ]
* Starting configure network device [ OK ]
...
Ubuntu 11.10 trunks ttyS0
trunks login:
When I log in:
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000000000000 no
virbr0 8000.000000000000 yes
I don't see any noticeable errors on boot. I see a few of the following entries:
* Starting configure network device [ OK ]
I sometimes also see:
Waiting for network configuration...
Waiting up to 60 more seconds for network configuration...
Looking at kern.log, I see:
Dec 2 02:50:52 trunks kernel: [ 45.113211] device bond0 entered promiscuous mode
Dec 2 02:50:52 trunks kernel: [ 45.113221] device bond0 left promiscuous mode
Dec 2 02:50:52 trunks kernel: [ 45.113224] device bond0 entered promiscuous m ode
Dec 2 02:50:52 trunks kernel: [ 45.113226] device bond0 left promiscuous mode
Dec 2 02:50:52 trunks kernel: [ 45.115598] ADDRCONF(NETDEV_UP): br0: link is not ready
...
Dec 2 02:50:52 trunks kernel: [ 45.235355] FS-Cache: Loaded
Dec 2 02:50:52 trunks kernel: [ 45.258321] FS-Cache: Netfs 'nfs' registered for caching
Dec 2 02:50:52 trunks kernel: [ 45.378114] bonding: bond0: Setting MII monitoring interval to 100.
Dec 2 02:50:52 trunks kernel: [ 45.378143] bonding: bond0: Setting up delay to 200.
Dec 2 02:50:52 trunks kernel: [ 45.379966] bonding: bond0: setting mode to 802.3ad (4).
Dec 2 02:50:52 trunks kernel: [ 45.380734] bonding: bond0: Setting LACP rate to slow (0).
Dec 2 02:50:52 trunks kernel: [ 45.382597] ADDRCONF(NETDEV_UP): bond0: link is not ready
Dec 2 02:50:52 trunks kernel: [ 45.408253] bonding: bond0: Adding slave eth3.
Dec 2 02:50:52 trunks kernel: [ 45.490835] bonding: bond0: enslaving eth3 as a backup interface with a down link.
Dec 2 02:50:52 trunks kernel: [ 45.491929] bonding: bond0: Adding slave eth2.
Dec 2 02:50:52 trunks kernel: [ 45.493123] init: udev-fallback-graphics main process (1634) terminated with status 1
Dec 2 02:50:52 trunks kernel: [ 45.574310] bonding: bond0: enslaving eth2 as a backup interface with a down link.
Dec 2 02:50:54 trunks kernel: [ 47.293867] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Dec 2 02:50:54 trunks kernel: [ 47.294899] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Dec 2 02:50:55 trunks kernel: [ 47.944385] igb: eth3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Dec 2 02:50:55 trunks kernel: [ 47.987913] bonding: bond0: link status up for interface eth3, enabling it in 0 ms.
Dec 2 02:50:55 trunks kernel: [ 47.987917] bonding: bond0: link status definitely up for interface eth3, 1000 Mbps full duplex.
Dec 2 02:50:55 trunks kernel: [ 47.988804] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
...
Dec 2 02:50:55 trunks kernel: [ 48.571065] igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Dec 2 02:50:55 trunks kernel: [ 48.586656] bonding: bond0: link status up for interface eth2, enabling it in 200 ms.
Dec 2 02:50:55 trunks kernel: [ 48.786228] bonding: bond0: link status definitely up for interface eth2, 1000 Mbps full duplex.
...
Dec 2 02:51:56 trunks kernel: [ 108.607424] ADDRCONF(NETDEV_UP): virbr0: link is not ready
I am attaching a copy of kern.log
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
Status in “ifupdown” package in Ubuntu:
Confirmed
Bug description:
Configuring an 802.3ad bond doesn't appear to work correctly. The following entry in /etc/network/interfaces should configure an 802.3ad bond between interfaces eth2 and eth3:
#auto bond0
iface bond0 inet static
address 10.191.62.2
netmask 255.255.255.0
broadcast 10.191.62.255
bond-slaves eth2 eth3
bond-primary eth2 eth3
bond-mode 802.3ad
bond-lacp_rate fast
bond-miimon 100
However, after booting the system, we have:
# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:1b:21:b7:21:ea
inet addr:10.191.62.2 Bcast:10.191.62.255 Mask:255.255.255.0
inet6 addr: fe80::21b:21ff:feb7:21ea/64 Scope:Link
UP BROADCAST MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth2 Link encap:Ethernet HWaddr 00:1b:21:b7:21:ea
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Memory:b2420000-b2440000
eth3 Link encap:Ethernet HWaddr 00:1b:21:b7:21:ea
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Memory:b2400000-b2420000
# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: down
MII Polling Interval (ms): 100
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: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:1b:21:b7:21:ea
Aggregator ID: N/A
Slave queue ID: 0
Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:1b:21:b7:21:eb
Aggregator ID: N/A
Slave queue ID: 0
If I do the following:
# ip link set dev bond0 up
# ifenslave bond0 eth2 eth3
# ifconfig bond0 10.191.62.2 netmask 255.255.255.0
I get:
# ifconfig bond0
bond0 Link encap:Ethernet HWaddr 00:1b:21:b7:21:ea
inet addr:10.191.62.2 Bcast:10.191.62.255 Mask:255.255.255.0
inet6 addr: fe80::21b:21ff:feb7:21ea/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:17 errors:0 dropped:17 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2108 (2.1 KB) TX bytes:3126 (3.1 KB)
# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
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: 2
Actor Key: 17
Partner Key: 24
Partner Mac Address: 00:04:96:18:54:d5
Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:1b:21:b7:21:ea
Aggregator ID: 1
Slave queue ID: 0
Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:1b:21:b7:21:eb
Aggregator ID: 1
Slave queue ID: 0
I can ping 10.191.62.2 after making the above changes. So, either I am
configuring /etc/network/interfaces incorrectly or ifupdown/ifenslave
is doing the wrong thing.
Note also the number of dropped packages on bond0. Why should I see
any dropped packages on the bond0 interface?
DistroRelease: Ubuntu 11.10
Package: ifupdown 0.7~alpha5.1ubuntu5
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.0.0-12.20-server 3.0.4
SourcePackage: ifupdown
Uname: Linux 3.0.0-12-server x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/889423/+subscriptions
More information about the foundations-bugs
mailing list