WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Link bonding problem

To: Matthew Law <matt@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Link bonding problem
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 22 Mar 2010 15:11:29 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 22 Mar 2010 06:12:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <3e8b7ebe6f5f87e292c9750f67e2a560.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <3e8b7ebe6f5f87e292c9750f67e2a560.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Mar 22, 2010 at 12:39:20PM -0000, Matthew Law wrote:
> I have been trying to convert an existing CentOS 5.4 / Gitco Xen 3.4.1 box
> to use bonded interfaces and have run into some problems.
> 
> Before the change the box was a fairly standard config and had 2 x NICs,
> with eth0 being used by the Xen  network-bridge script.  I wanted to add a
> dual port NIC card and create two bonded interfaces:
> 
> bond0 (storage and management): eth0, eth1
> 
> bond1 (public interface): eth2, eth3
> 
> I shutdown the box, added the card and brought it up in with the normal,
> non-xen kernel in single user mode.  I added the bonds to modules.conf,
> added the interface and bond configs as required.  I opted to reboot and
> go back into a non-Xen kernel and test out the bonds in runlevel 2 - all
> working and no errors.
> 
> I edited the xend-config.sxp file and changed this line:
> 
> (network-script 'network-bridge netdev=eth0 antispoof=yes')
> 
> to this:
> 
> (network-script 'network-bridge netdev=bond1 antispoof=yes')
> 
> I then rebooted into the Xen dom0 kernel.
> 
> I immediately started to see errors regarding the bonds.  Something along
> the lines of "MAC address already in use".  After googling I saw this was
> an issue in the past but not any more in CentOS 5.4 with Xen 3.4.1.  The
> domUs started OK, but were not bridged to the external network (I could
> ping the dom0 address and other domUs, but the network gateway was
> unreachable).
> 
> I tried various things to no avail, so I removed the bonds and simply set
> the network-bridge script to use eth3 (this was the easiest thing to do
> since I had already changed the switches over and didn't want to remove
> the network card I had installed).
> 
> Can anybody give me some pointers as to what the issue is and how to
> resolve it? - I currently use antispoofing with iptables and ebtables
> which is driven by the xen scripts, so I would prefer to keep that feature
> regardless of how the bonds are handled.
> 
> 

I prefer disabling Xen network-script from xend-config.sxp (comment out the 
line),
and then set up the bonds/bridges using the distro default 
/etc/sysconfig/network-scripts/ifcfg* scripts.

-- Pasi


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>