[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FW: [Xen-users] Bonding & xenbr0


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Geoff Wiener" <gwiener@xxxxxxxxxxxxxxx>
  • Date: Tue, 24 Jun 2008 13:13:14 +0100
  • Delivery-date: Tue, 24 Jun 2008 05:13:49 -0700
  • Importance: normal
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Priority: normal
  • Thread-index: AcjV6T4CGMimCzEES9meWxEnhm4bIQAB9bJAAACgeYA=
  • Thread-topic: [Xen-users] Bonding & xenbr0

Hi Gerhard;

I'm pretty new to this list too but I think this may be a bonding issue.  What 
bonding mode are you using in /etc/modprobe.conf?  You should have a couple of 
lines in there:

alias bond0 bonding
options bond0 miimon=x mode=x

What kind of switch are you connecting to and have you done any specific 
configuration to the switch to support your bonding mode? (depends on the 
mode).  Also can you provide /etc/sysconfig/network-scripts/ethx and bond0?

I have done some work recently with Bonding with Xen on Centos 5.1 and may be 
able to offer some advice.

Best Regards

G

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Gerhard Spiegl
Sent: 24 June 2008 11:58 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Bonding & xenbr0

Hi List!

This is my first post on this list so let me say hello to all here!

I'm trying to set up HA xen VMs on RHEL 5.2 with Red Hat Cluster Suite.
XEN version used is original Red Hat packaged xen-3.0.3-64.el5_2.1.

Setup is the following:

eth0 + eth1 ==> bond0  (public interface, connected to two core switches with 
one vlan)
eth2  (private interface connected to rack mounted 100Mbit switch for cluster 
interconnect)
      (this will be eth2 + eth3 ==> bond1 in future)

The xen network is working fine after adding "netdev=bond0" to the 
(network-script ...) line in xend-config.sxp - no other changes were made.

But: Yesterday the network administrator complained about error messages in the 
switch logs caused by multiple interfaces having MAC address FE:FF:FF:FF:FF:FF 
since XEN was set up.
The only public interface with a configured IP is bond0 with the MAC of 
enslaved eth0 so why is this strange MAC (FE:FF..) seen on the switch? We are 
also wondering why eth0 and eth1 do have this MAC. Is there an issue with 
bonding and xen bridging?

Output of ifconfig is attached, if you need more information, please let me 
know.

I would be pleased if anyone could point me to a right direction - google 
didn't help.

regards
Gerhard



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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.