Hide Forgot
Description of problem: Bond cannot work OK under RHEL5.7 xen Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: . Load the BIOS optimized default. 2. Install OS RHEL5.4 64bit or RHEL5.7 64bit via PXE or USB DVD-ROM. 3. After installation completed, configure the environment of teaming(bonding) test. 4. After configuration, ping the IP of two client at the same time. 5. we can ping the two IPs of clients at the same time,when unplug eth0's cable. 6. So the bonding fail. 7.But when we do the same configuration at rhel5.4 and rhel5.7, no-xen mode, the bonding is OK. [Verification] 1. The teaming(bonding) test will always fail under RHEL5.4 xen 64bit. 2. The teaming(bonding) test will always fail under RHEL5.7 xen 64bit. 3. The teaming (bonding) test will pass under RHEL5.4 base 64bit. 4. The teaming (bonding) test will pass under RHEL5.7 base 64bit. Actual results: Expected results: Additional info: [1]Since eth0 is a bridge in Xen mode,and bridge peth0,but we focos on how to set bonding in RHEL5 Xen. [2]When bonding up, we try to ping the same client through a switch connect the 2 NICs, but fail (The connection between server to client interrupt) when unconnect nic0, according to bonding, unconnect any nic cable, the connection between server to client will not interrupt. [3] For further show the base steps as we had, I list the steps as below: I upload teaming steps as we had: 1. #touch /etc/sysconfig/network-scripts/ifcfg-bond0 #cd /etc/sysconfig/network-scripts #vi ifcfg-bond0 DEVICE=bond0 BOOTPROTO=none ONBOOT=yes NETWORK=192.168.0.0 NETMASK=255.255.255.0 IPADDR=192.168.0.100 USERCTL=no 2.Modify the 2 nics' configuration files #vim ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no #vim ifcfg-eth1 DEVICE=eth1 BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no 3. #vi /etc/modprobe.conf alias bond0 bonding 4. #ifup bond0
Sorry, update the steps 5 5. we cann't ping the two IPs of clients at the same time,when unplug eth0's cable. So the bonding fail.
(In reply to comment #0) > Description of problem: > Bond cannot work OK under RHEL5.7 xen > Version-Release number of selected component (if applicable): > How reproducible: > Steps to Reproduce: > . Load the BIOS optimized default. > 2. Install OS RHEL5.4 64bit or RHEL5.7 64bit via PXE or USB DVD-ROM. > 3. After installation completed, configure the environment of teaming(bonding) > test. > 4. After configuration, ping the IP of two client at the same time. > 5. we cannot ping the two IPs of clients at the same time,when unplug eth0's > cable. > 6. So the bonding fail. > 7.But when we do the same configuration at rhel5.4 and rhel5.7, no-xen mode, > the bonding is OK. > [Verification] > 1. The teaming(bonding) test will always fail under RHEL5.4 xen 64bit. > 2. The teaming(bonding) test will always fail under RHEL5.7 xen 64bit. > 3. The teaming (bonding) test will pass under RHEL5.4 base 64bit. > 4. The teaming (bonding) test will pass under RHEL5.7 base 64bit. > Actual results: > Expected results: > Additional info: > [1]Since eth0 is a bridge in Xen mode,and bridge peth0,but we focos on how to > set bonding in RHEL5 Xen. > [2]When bonding up, we try to ping the same client through a switch connect the > 2 NICs, but fail (The connection between server to client interrupt) when > unconnect nic0, according to bonding, unconnect any nic cable, the connection > between server to client will not interrupt. > [3] For further show the base steps as we had, I list the steps as below: > I upload teaming steps as we had: > 1. #touch /etc/sysconfig/network-scripts/ifcfg-bond0 > #cd /etc/sysconfig/network-scripts > #vi ifcfg-bond0 > DEVICE=bond0 > BOOTPROTO=none > ONBOOT=yes > NETWORK=192.168.0.0 > NETMASK=255.255.255.0 > IPADDR=192.168.0.100 > USERCTL=no > 2.Modify the 2 nics' configuration files > #vim ifcfg-eth0 > DEVICE=eth0 > BOOTPROTO=none > ONBOOT=yes > MASTER=bond0 > SLAVE=yes > USERCTL=no > #vim ifcfg-eth1 > DEVICE=eth1 > BOOTPROTO=none > ONBOOT=yes > MASTER=bond0 > SLAVE=yes > USERCTL=no > 3. #vi /etc/modprobe.conf > alias bond0 bonding > 4. #ifup bond0
Hi Chris, what xen network script do you use? There's special bonding script network-bridge-bonding that has to be used instead of default network-bridge. Also you need to restart xend to properly re-setup network.
I'm closing this as not-a-bug. There's a chance that default network-bridge scripts will work in the future as a side-effect of fixes for other bugs, but for now, as it has always been, the special scripts are required.