On Fri, 2006-12-22 at 18:08 +0200, Dimitar Dragoev wrote: > Hi > > I’m trying to setup network bonding active/backup linked to two > switches. Below are my configuration files: > > > > /etc/modprobe.conf > > alias bond0 bonding > > options bond0 mode=1 arp_interval=1000 arp_ip_target=192.168.000.161 > primary=eth0 > > > > /etc/sysconfig/network-scripts/ifcfg-bond0 > > DEVICE=bond0 > > IPADDR=192.168.0.164 > > NETWORK=192.168.0.160 > > NETMASK=255.255.255.224 > > USERCTL=no > > BOOTPROTO=none > > ONBOOT=yes > > > > /etc/sysconfig/network-scripts/ifcfg-eth0 > > # Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet > > DEVICE=eth0 > > USERCTL=no > > ONBOOT=yes > > MASTER=bond0 > > SLAVE=yes > > BOOTPROTO=none > > ETHTOOL_OPTS="speed 100 duplex full autoneg off" > > > > ETH1 almost same configuration. > > > > Now some outputs: > > Ethernet Channel Bonding Driver: v3.0.3 (March 23, 2006) > > > > Bonding Mode: fault-tolerance (active-backup) > > Primary Slave: eth0 > > Currently Active Slave: eth0 > > MII Status: up > > MII Polling Interval (ms): 0 > > Up Delay (ms): 0 > > Down Delay (ms): 0 > > ARP Polling Interval (ms): 1000 > > ARP IP target/s (n.n.n.n form): 192.168.0.161 > > > > Slave Interface: eth0 > > MII Status: up > > Link Failure Count: 2 > > Permanent HW addr: 00:0d:60:14:a7:a6 > > > > Slave Interface: eth1 > > MII Status: up > > Link Failure Count: 11 > > Permanent HW addr: 00:0d:60:14:a7:a7 > > > > > > bond0 Link encap:Ethernet HWaddr 00:0D:60:14:A7:A6 > > inet addr:192.168.0.164 Bcast:192.168.0.191 > Mask:255.255.255.224 > > inet6 addr: fe80::20d:60ff:fe14:a7a6/64 Scope:Link > > UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 > > RX packets:111363 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:44126 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:10541104 (10.0 MiB) TX bytes:4321353 (4.1 MiB) > > > > eth0 Link encap:Ethernet HWaddr 00:0D:60:14:A7:A6 > > inet6 addr: fe80::20d:60ff:fe14:a7a6/64 Scope:Link > > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 > > RX packets:66381 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:43098 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:6591933 (6.2 MiB) TX bytes:3847632 (3.6 MiB) > > Interrupt:185 > > > > eth1 Link encap:Ethernet HWaddr 00:0D:60:14:A7:A6 > > inet6 addr: fe80::20d:60ff:fe14:a7a6/64 Scope:Link > > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 > > RX packets:44982 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:1028 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:3949171 (3.7 MiB) TX bytes:473721 (462.6 KiB) > > Interrupt:193 > > > > > > > > Now here is my problem: > > When I physically disconnect eth0 everything works fine and all > traffic flow via eth1 > > Second case eth0 has link up but not have access to default gateway > 192.168.0.161 (for example access list or switch failure) eth0 goes > down and eth1 which is ok try’s to go up but w/o cusses. In the > message log I can see only this: > > bonding: bond0: backup interface eth1 is now down > > bonding: bond0: backup interface eth1 is now up > > bonding: bond0: backup interface eth1 is now down > > bonding: bond0: backup interface eth1 is now up > > bonding: bond0: backup interface eth1 is now down > > bonding: bond0: backup interface eth1 is now up > > > > However exactly same setup works fine with REL 4.2 > > > > I suppose this can be a bug in FC5? Possible, but judging from the "up-down-up-down" stuff on eth1, it looks more like there's still autonegotiation going on between eth1 and the switch it's plugged into (I'm assuming you're using two different switches). Since you didn't include the eth1 configuration yet say it's "almost identical", I have to assume that something's buggered in there or that THIS version of the driver for eth1 does autonegotiation in a different way than that on RHEL4.2 (not uncommon) You could try fixing the ports on the switches to the same settings as the NICs (100Mb, full duplex, no autosense) and see if that helps. ---------------------------------------------------------------------- - Rick Stevens, Senior Systems Engineer rstevens@xxxxxxxxxxxxxxx - - VitalStream, Inc. http://www.vitalstream.com - - - - I won't rise to the occasion, but I'll slide over to it. - ----------------------------------------------------------------------
