Hi, I'll do my best to describe the problem. I tested the config manually by running following commands:
# insmod bonding mode=1 arp_interval=100 arp_ip_targets=10.0.3.1,10.0.3.2 primary=eth1 # insmod 8021q # insmod e100 # insmod e1000 The module load order doesn't affect the problem here. It is now heavily tested and the above is the recommended one in bonding documentation. # ip addr add 10.0.3.3/24 dev bond0 # ip link set bond0 up # ip link set eth0 up # ip link set eth1 up # ifenslave bond0 eth0 Now ip link shows eth0 as slave and # cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v2.6.0 (January 14, 2004) Bonding Mode: fault-tolerance (active-backup) Primary Slave: eth1 Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms): 200 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth0 MII Status: up Link Failure Count: 1 Permanent HW addr: 00:09:6b:b1:ad:53 Running ping from 10.0.3.1 to 10.0.3.3 runs smoothly. Adding second interface to the bond interface works fine. # ifenslave bond0 eth1 # cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v2.6.0 (January 14, 2004) Bonding Mode: fault-tolerance (active-backup) Primary Slave: eth1 Currently Active Slave: eth1 MII Status: up MII Polling Interval (ms): 200 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth0 MII Status: up Link Failure Count: 1 Permanent HW addr: 00:09:6b:b1:ad:53 Slave Interface: eth1 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:1b:21:14:37:c3 Disabling and enabling peer interfaces on the switches confirms that the bond works as expected. When I add an vlan onto the bond interface: # vconfig set_name_type VLAN_PLUS_VID_NO_PAD # vconfig add bond0 3 "3" is the VLAN tag ID, ie. from 1 to 4096, in practice some switches and/or switch vendors restrict available ID space ie. either you can have say max 8 vlans defined in one switch but the switch should not retrict 4096 IDs flowing through it or some vendors reserve IDs for some special purposes. This way "600" is valid VLAN ID. Now disabling the primary interface's (ie. eth1) peer on the switch also halts ping from 10.0.3.1 to 10.0.3.3, BUT when # ip addr add 10.0.4.1/24 dev vlan3 # ip link set vlan3 up ping from 10.0.4.2 to 10.0.4.1 flows smoothly. Enabling the peer interface of eth1 restores ping from 10.0.3.1 to 10.0.3.3 again. In other words the active backup interface (eth0 in this setup) becomes active and the bond interface has vlans, the vlans continue to work but the native non-vlan traffic blocks. The similar setup on latest kernels with bonding 3.5.x work fine with the same switches. The peer swiches are ProCurve 2650 and ProCurve 3400. Best regards, Erkki on 5/9/08 3:00 PM Charles Steinkuehler wrote: > Erkki Lintunen wrote: > | Hi, > | > | can anybody point me where to look at because I'm running out of ideas > | with my bond setup? > | > | I have a test b-u 3.1 system with two physical network interfaces (100 > | Mbps and GbE). I load bonding miimon=100 mode=1, then vlan tagging > | driver 8021q and after that network card drivers. bond0 is brought up > | with simple iface definition in interfaces plus a slaves line. A > | neighboring systems runs ping -r to the ip of the bond interface and > | after command ifup bond0 is run, pings flow nicely. > > I'm confused...exactly what are you bonding if you don't have network > card drivers loaded yet? > > | But when I add first vlan-interface onto bond0, pings stop. tcpdump > | shows no traffic either. Nothing more than command "vconfig add bond0 > | 600" is needed, no "ip link set bond0.600 up" or such is needed. Traffic > | on the vlan interface flows nicely, but the untagged bond0 interface > dies. > > Please post dumps of your configuration with bond setup, then with the > vlan added. It's pretty hard to say what's going wrong with the limited > information above. Also, what's with the 600 for the vlan ID? I > thought these only went to 64 or so... > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
