I used the information at http://linux-net.osdl.org/index.php/Bonding#Configuration_with_sysconfig_support to configure my system for bonding. I am enslaving eth0 and eth1 to bond0. The interface config files are as follows: ifcfg-bond0: BOOTPROTO=''dhcp'' BROADCAST='''' ETHTOOL_OPTIONS='''' IFPLUGD_PRIORITY=''20'' IPADDR='''' MTU='''' NAME=''Bond 0'' NETMASK='''' NETWORK='''' REMOTE_IPADDR='''' STARTMODE=''auto'' USERCONTROL=''no'' BONDING_MASTER=''yes'' BONDING_MODULE_OPTS=''mode=active-backup miimon=100'' BONDING_SLAVE0=''eth0'' BONDING_SLAVE1=''eth1'' ifcfg-eth-id-00:0e:0c:72:5f:f9 for eth0: BOOTPROTO=''none'' NAME=''Intel PRO/1000 MT Desktop Adapter'' STARTMODE=''off'' UNIQUE=''JNkJ.Wcsi8V4ddI5'' _nm_name=''bus-pci-0000:01:04.0'' ifcfg-eth-id-00:e0:81:54:b1:b9 for eth1 BOOTPROTO=''none'' NAME=''Tyan CK804 Ethernet Controller'' STARTMODE=''off'' UNIQUE=''mY_N.C86myLJQAC7'' _nm_name=''bus-pci-0000:80:0a.0'' If I boot the box with the native Linux kernel, everything comes up and works as expected. When I boot with the Xen kernel, I see the bond0 interface come up with eth0 and eth1 being enslaved to bond0. But then after xend starts, bond0 is down and eth0 has been associated with peth0. So things don''t work. I changed xend-config.sxp to use the line (network-script ''network-bridge netdev=bond0). But this did not work either. network-bridge errors out and does not complete. Any help to get this working would be greatly appreciated. Kirk Allan kallan@novell.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Apr-06 15:36 UTC
Re: [Xen-users] Bonding not working with network-bridge
Kirk Allan wrote:> I used the information at > > http://linux-net.osdl.org/index.php/Bonding#Configuration_with_sysconfig_support > > to configure my system for bonding. I am enslaving eth0 and eth1 to bond0. The interface config files are as follows:...> > Any help to get this working would be greatly appreciated. >I use bonding with success, but I had to write my own version of the network-bridge script. I''ve attached the script. Keep in mind that I make a second bridge for a private network. You might not need that. -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>>> On Thu, Apr 6, 2006 at 9:36 AM, in message<4435356D.5080903@ldsys.net>, "Christopher G. Stach II" <cgs@ldsys.net> wrote:> Kirk Allan wrote: >> I used the information at >> >> > http://linux-net.osdl.org/index.php/Bonding#Configuration_with_sysconfig_suppo> rt >> >> to configure my system for bonding. I am enslaving eth0 and eth1 tobond0.> The interface config files are as follows: > ... >> >> Any help to get this working would be greatly appreciated. >> > > I use bonding with success, but I had to write my own version of the > network- bridge script. I''ve attached the script. Keep in mind thatI> make a second bridge for a private network. You might not needthat. Thanks for the info. I was able to get the the domU up and it received a dhcp address for eth0. I could ping dom0 fine but not any other address. I did a packet trace on dom0 and could see the arps going out from domU and the responses coming back but domU couldn''t see them. If I just left the ping going, sometimes after a minute or two, the ping would start working in domU. If I stopped the ping and let the domU sit idle for a while, starting the pings up again would fail. Another way I could get the pings working was to unplug the cable from one of the enslaved interfaces. Starting the ping in domU would then work. I could then plug the cable back in and the ping would continued. It seems like I''m almost there, but I''m still missing something. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Apr-06 22:02 UTC
Re: [Xen-users] Bonding not working with network-bridge
Kirk Allan wrote:> I did a packet trace on dom0 and could see the arps going out from domU > and the responses coming back but domU couldn''t see them. If I just > left the ping going, sometimes after a minute or two, the ping would > start working in domU. If I stopped the ping and let the domU sit idle > for a while, starting the pings up again would fail. > > Another way I could get the pings working was to unplug the cable from > one of the enslaved interfaces. Starting the ping in domU would then > work. I could then plug the cable back in and the ping would continued. > > > It seems like I''m almost there, but I''m still missing something.Are you getting checksum errors on your packets, too? :) -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>>> On Thu, Apr 6, 2006 at 4:02 PM, in message <44359007.1000007@ldsys.net>,"Christopher G. Stach II" <cgs@ldsys.net> wrote:> Kirk Allan wrote: >> I did a packet trace on dom0 and could see the arps going out from domU >> and the responses coming back but domU couldn''t see them. If I just >> left the ping going, sometimes after a minute or two, the ping would >> start working in domU. If I stopped the ping and let the domU sit idle >> for a while, starting the pings up again would fail. >> >> Another way I could get the pings working was to unplug the cable from >> one of the enslaved interfaces. Starting the ping in domU would then >> work. I could then plug the cable back in and the ping would continued. >> >> >> It seems like I''m almost there, but I''m still missing something. > > Are you getting checksum errors on your packets, too? :)There are no checksum errors when the pings are working. One thing I noticed, when the ping originates from domU, the arp makes it to the destination, the destination responds, dom0 can see the arp, but it never makes it back to domU. However, if the external box starts the ping, the arp gets to dom0, gets bridged to domU, domU replies to the arp, the external box receives the arp response, and successful pings continue. But as soon as the arp entry in domU gets removed/times out, new pings from domU fail again. Kirk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users