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] Bonding...again

Thanks for the help...

I've tried this method, as well as Christian's method which does not use a VLAN. In both cases, I can get all interfaces to come up but can't get the guests to make network connections to the outside. I should also note that under RedHat EL5.3, if you don't use a VLAN and bridge directly off of the bond, you run into this problem:

https://bugzilla.redhat.com/show_bug.cgi?id=463014

Which has been discussed on this list before.

I think I'm getting hung up on the routing. If we use your VLAN example, I configure bond0 with the public IP for dom0 (yes?), then I configure the VLAN with it's own network like 10.0.X.X or 192.168.X.X, then I create a route from the VLAN to bond0... yes? If I understand bridging correctly, I won't need to add any routes from VLAN to bridge...

Let me know if I've got that straight or not...

Thanks again for the help...

...adam




On Aug 5, 2009, at 12:18 AM, Jonathan Bayles wrote:

Take a look at these configs and the brctl command...(XXXX = vlan tag)

[root@pnode006 /]# cat /etc/sysconfig/network-scripts/ifcfg-eth0.XXXX
DEVICE=eth0.XXXX
BOOTPROTO=static
ONBOOT=yes
VLAN=yes
BRIDGE=brXXXX

[root@pnode006 /]# cat /etc/sysconfig/network-scripts/ifcfg-brXXXX
DEVICE=brXXXX
TYPE=Bridge
BOOTPROTO=static
ONBOOT=YES
DELAY=0
STP=off

[root@pnode006 /]# brctl show
bridge name     bridge id               STP enabled     interfaces
brXXXX          8000.001ec9fd2360       no              vif3.0
eth0.XXXX vif = [ "mac=YY:YY:YY:YY:YY:YY,bridge=brXXXX" ]

Basically,

Create a sub interface off your bond, configure it to do the tagging, create a bridge for the tagged traffic, add the interface onto a "port" on the bridge. Add the guest onto the bridge using a vif.

Subint <---- brctl bridge ----> guest vif

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx ] On Behalf Of Adam Wead
Sent: Tuesday, August 04, 2009 5:22 PM
To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Bonding...again

Hi all,

I know this topic has been discussed a lot on this list, and I've been
going over some posts from months past trying to get things to work on
my end, but I need another appeal for help.  I'm setting up a dom0
under Red Hat EL5, with 2 NICs.  From looking over the old posts, it
looks like the best way to do this is to create bonds, vlans and
bridges under Red Hat and bypass Xen's initial network-bridge script.
I looked at what Fajar had said:

http://lists.xensource.com/archives/html/xen-users/2009-05/msg00992.html

And I tried duplicating this, mind you, without the patched ifup
script and setup something like this:

- (eth1 + eth2) = bond0 with mode 2
- create VLAN bond0.2 to bond0
- attach bridge xenbr0 to bond0.2
- modified xend-config file: (vif-script 'vif-bridge bridge=xenbr0')

This appears to work, but when I create guests and attach them to the
xenbr0, no dice.  My question is, is the above correct and where to
the IPs go?  Dom0 has it's own IP address, but what interface/bond/
VLAN does that go under?  Should the other items have IPs as well?

My network kung fu is limited, so I apologize in advance if these are
stupid questions.

many thanks,

...adam





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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>