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

RE: [Xen-users] XCP: Networking, bridges and bondings


  • To: 'Pasi Kärkkäinen' <pasik@xxxxxx>, "Angel L. Mateo" <amateo@xxxxx>
  • From: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
  • Date: Wed, 24 Feb 2010 18:44:17 +0000
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 24 Feb 2010 10:45:33 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Acq0vYs4ngtccKsiT7qq94PKeVXsCwAwn4zg
  • Thread-topic: [Xen-users] XCP: Networking, bridges and bondings

Hi,

> >     I have configure it now XCP with bonding (as described in the
> > documentation), but it has a strange behaviour:
> >
> > * bond0 doesn't appear in /proc/net/bonding
> > * With brctl show I get:

As Pasi says, XCP is now using the openvswitch code rather than the linux 
bridging code.

The openvswitch handles bonding and VLAN tagging differently to the stock linux 
code. There is a small compatibility shim but it's incomplete (and will never 
be perfect). IIRC the vswitch represents bonds as an association of switch 
ports and considers VLANs to be a property of switch ports (with guest VIFs 
plugged into those). Rather than use the compatibility shim (brctl etc) I think 
you'd get a clearer picture if you used the openvswitch-specific commands. 
Check out the commands ovs-* in dom0. It's probably worth checking out the 
openvswitch mailing lists too, for low-level details.

Cheers,
Dave

> >
> > # brctl show
> > bridge name bridge id               STP enabled     interfaces
> > xapi1               0000.002481a6a178       no              bond0
> >                                                     eth0
> >                                                     eth3
> > xenbr1              0000.002481a6b1c6       no              eth1
> > xenbr2              0000.00237da6e658       no              eth2
> >
> >     that is, eth0, eth3 and bond0 are included in the bridge. I have
> tried
> > to manually remove eth0 (or eth3), but I can't:
> >
> > # brctl delif xapi1 eth0
> > can't delete eth0 from xapi1: Operation not supported
> >
> > * Another problem is the MAC associated with xapi1 (my management
> > interface) is discover from the other switches of my network in two
> > interfaces, that is, the one that connect them to the switch where I
> > have eth0 connected to, and the the switch where I have eth1
> connected
> > to. Is this correct?
> > * When I boot the machine (or when it has a lot of time of inactivity,
> > it's a test environment), I have the 3 o 4 first packages duplicated.
> Is
> > this correct?
> >
> >     When the same configuration, but with XenServer 5.0 (citrix), the
> bond0
> > appears at /proc/net/bonding, ethX interfaces are not included in
> > bridges and I don't have duplicate packages.
> >
> 
> Citrix XenServer 5.x uses Linux bridge support in dom0 kernel,
> but XCP uses OpenVswitch instead of Linux bridging..
> 
> -- Pasi
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
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®.