thr3ads.net - Xen users - [Xen-users] Bonding...again [Aug 2009]

If this information is useful, please help other people find it:
Share via:

Adam Wead

2009-Aug-04 21:21 UTC

[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@lists.xensource.com
http://lists.xensource.com/xen-users

Jonathan Bayles

2009-Aug-05 04:18 UTC

head link

RE: [Xen-users] Bonding...again

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@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Adam Wead
Sent: Tuesday, August 04, 2009 5:22 PM
To: Xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-users

Christian Fischer

2009-Aug-05 06:58 UTC

head link

Re: [Xen-users] Bonding...again

On Tuesday 04 August 2009, Adam Wead wrote:> 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
That''s quite simple.

- create the bond interface bond0
- bring it up, assign no ip
- create the bridge br0, bridge interfaces: bond0, bring it up
- assign the dom0 ip to br0, set up the default route
- create domU

replace the network-bridge script with a network-bridge-dummy script which 
does nothing and ever returns 0

configure domUs vif like
vif = [ ''mac=xx:xx:xx:xx:xx:xx, bridge=br0'' ]

I don''t know how networking is configureed with Red Hat EL5, as sample
for
better understanding (i hope) all the stuff for gentoo:

# file /etc/conf.d/net
slaves_bond0="eth0 eth1"
config_bond0=("null")
bridge_br0="bond0"
config_br0=("192.168.x.x/23 brd 192.168.x.x")
routes_br0=("default via 192.168.x.x")
dns_domain_br0="<your domain>"
dns_servers_br0="192.168.x.x"


# file /etc/xen/config/domU_xxx
[snip]
vif = [ ''mac=xx:xx:xx:xx:xx:xx, bridge=br0'' ]
[snip]


# file /etc/xen/xend-config.sxp
[snip]
(network-script network-bridge-dummy)
[snip]


# file /etx/xen/scripts/networ-bridge-dummy

#!/bin/bash
# dummy xen bridge script

exit 0
# EOF


run
# /etc/init.d/net.bond0 start
# /etc/init.d/net.br0 start
# xm create /etc/xen/config/domU_xxx


If you have any questions about my bond configuration i''ll share it
with you,
of course.


Hope that helps a bit.
Christian
-- 
"Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid."
        --- Frank Vincent Zappa

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

Adam Wead

2009-Aug-06 20:02 UTC

head link

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@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com
> ] On Behalf Of Adam Wead
> Sent: Tuesday, August 04, 2009 5:22 PM
> To: Xen-users@lists.xensource.com
> 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@lists.xensource.com
> http://lists.xensource.com/xen-users


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

Christian Fischer

2009-Aug-07 08:33 UTC

head link

Re: [Xen-users] Bonding...again

On Thursday 06 August 2009, Adam Wead wrote:> 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
Adam,

this is a simple setup you can do without any RHEL network init scripts.

I suggest writing your own with simple ip, brctl and ifenslave commands.
This is IMHO the shortest way.

Christian
>
> 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@lists.xensource.com
> > [mailto:xen-users-bounces@lists.xensource.com ] On Behalf Of Adam Wead
> > Sent: Tuesday, August 04, 2009 5:22 PM
> > To: Xen-users@lists.xensource.com
> > 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@lists.xensource.com
> > http://lists.xensource.com/xen-users


-- 
"Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid."
        --- Frank Vincent Zappa

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

Dustin Black

2009-Aug-07 14:52 UTC

head link

Re: [Xen-users] Bonding...again

Below is a working configuration in the form of ifcfg files, Xen network
scripts, /etc/modprobe.conf, and /etc/rc.d/rc.local.  This is bonding
without VLANs on a CentOS 5.2 x86-64 box.

ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:A2:19:11:D1:58
ONBOOT=yes
MASTER=bond0
SLAVE=yes

ifcfg-eth1:
DEVICE=eth1
BOOTPROTO=none
HWADDR=00:A2:19:11:D1:59
ONBOOT=yes
MASTER=bond0
SLAVE=yes

ifcfg-bond0:
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
TYPE=ethernet
BONDING_OPTS="mode=4 miimon=100"

ifcfg-bond0:0:
DEVICE=bond0:0
BOOTPROTO=static
ONBOOT=yes
TYPE=ethernet
IPADDR=10.1.1.5
NETMASK=255.255.255.0
DNS1=10.1.1.8
DNS2=10.1.1.9
DOMAIN="domain.com domain"
# Gateway is set in /etc/rc.d/rc.local

/etc/xen/xend-config.sxp (snippet):
(network-script network-multi-bridge)

/etc/xen/scripts/network-multi-bridge (this is actually a relic; I''m
not
sure why we''re still using it):
#!/bin/sh
# network-multi-bridge
# Exit if anything goes wrong
set -e
# First arg is operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge
case ${OP} in
start)
$script start vifnum=0 bridge=xenbr0 netdev=bond0
;;
stop)
$script stop vifnum=0 bridge=xenbr0 netdev=bond0
;;
status)
$script status vifnum=0 bridge=xenbr0 netdev=bond0
;;
*)
echo ''Unknown command: '' ${OP}
echo ''Valid commands are: start, stop, status''
exit 1
esac

/etc/modprobe.conf (snippet):
alias bond0 bonding

/etc/rc.d/rc.local (snippet):
# Default gateway doesn''t get set properly after the xend startup, so
we''ll
set it here
route add -net default gw 10.1.1.1





On Fri, Aug 7, 2009 at 4:33 AM, Christian Fischer <
Christian.Fischer@fischundfischer.com> wrote:
> On Thursday 06 August 2009, Adam Wead wrote:
> > 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
>
> Adam,
>
> this is a simple setup you can do without any RHEL network init scripts.
>
> I suggest writing your own with simple ip, brctl and ifenslave commands.
> This is IMHO the shortest way.
>
> Christian
>
> >
> > 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@lists.xensource.com
> > > [mailto:xen-users-bounces@lists.xensource.com ] On Behalf Of Adam
Wead
> > > Sent: Tuesday, August 04, 2009 5:22 PM
> > > To: Xen-users@lists.xensource.com
> > > 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@lists.xensource.com
> > > http://lists.xensource.com/xen-users
>
>
>
> --
> "Without music to decorate it, time is just a bunch of boring
production
>  deadlines or dates by which bills must be paid."
>        --- Frank Vincent Zappa
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Adam Wead

2009-Aug-17 20:38 UTC

head link

Re: [Xen-users] Bonding...again

Thanks, Dustin.

I used your script and it seems to work... I couldn''t get my setup to  
work with the alias that''s off of the bond devices, but it works when  
I used the bond device directly.

best,

...adam




On Aug 7, 2009, at 10:52 AM, Dustin Black wrote:
> Below is a working configuration in the form of ifcfg files, Xen  
> network scripts, /etc/modprobe.conf, and /etc/rc.d/rc.local.  This  
> is bonding without VLANs on a CentOS 5.2 x86-64 box.
>
> ifcfg-eth0:
> DEVICE=eth0
> BOOTPROTO=none
> HWADDR=00:A2:19:11:D1:58
> ONBOOT=yes
> MASTER=bond0
> SLAVE=yes
>
> ifcfg-eth1:
> DEVICE=eth1
> BOOTPROTO=none
> HWADDR=00:A2:19:11:D1:59
> ONBOOT=yes
> MASTER=bond0
> SLAVE=yes
>
> ifcfg-bond0:
> DEVICE=bond0
> BOOTPROTO=none
> ONBOOT=yes
> TYPE=ethernet
> BONDING_OPTS="mode=4 miimon=100"
>
> ifcfg-bond0:0:
> DEVICE=bond0:0
> BOOTPROTO=static
> ONBOOT=yes
> TYPE=ethernet
> IPADDR=10.1.1.5
> NETMASK=255.255.255.0
> DNS1=10.1.1.8
> DNS2=10.1.1.9
> DOMAIN="domain.com domain"
> # Gateway is set in /etc/rc.d/rc.local
>
> /etc/xen/xend-config.sxp (snippet):
> (network-script network-multi-bridge)
>
> /etc/xen/scripts/network-multi-bridge (this is actually a relic;
I''m
> not sure why we''re still using it):
> #!/bin/sh
> # network-multi-bridge
> # Exit if anything goes wrong
> set -e
> # First arg is operation.
> OP=$1
> shift
> script=/etc/xen/scripts/network-bridge
> case ${OP} in
> start)
> $script start vifnum=0 bridge=xenbr0 netdev=bond0
> ;;
> stop)
> $script stop vifnum=0 bridge=xenbr0 netdev=bond0
> ;;
> status)
> $script status vifnum=0 bridge=xenbr0 netdev=bond0
> ;;
> *)
> echo ''Unknown command: '' ${OP}
> echo ''Valid commands are: start, stop, status''
> exit 1
> esac
>
> /etc/modprobe.conf (snippet):
> alias bond0 bonding
>
> /etc/rc.d/rc.local (snippet):
> # Default gateway doesn''t get set properly after the xend startup,
> so we''ll set it here
> route add -net default gw 10.1.1.1
>
>
>
>
>
> On Fri, Aug 7, 2009 at 4:33 AM, Christian Fischer
<Christian.Fischer@fischundfischer.com
> > wrote:
> On Thursday 06 August 2009, Adam Wead wrote:
> > 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
>
> Adam,
>
> this is a simple setup you can do without any RHEL network init  
> scripts.
>
> I suggest writing your own with simple ip, brctl and ifenslave  
> commands.
> This is IMHO the shortest way.
>
> Christian
>
> >
> > 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@lists.xensource.com
> > > [mailto:xen-users-bounces@lists.xensource.com ] On Behalf Of  
> Adam Wead
> > > Sent: Tuesday, August 04, 2009 5:22 PM
> > > To: Xen-users@lists.xensource.com
> > > 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@lists.xensource.com
> > > http://lists.xensource.com/xen-users
>
>
>
> --
> "Without music to decorate it, time is just a bunch of boring  
> production
>  deadlines or dates by which bills must be paid."
>        --- Frank Vincent Zappa
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
> <ATT00001.txt>



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

Fajar A. Nugraha

2009-Aug-18 03:05 UTC

head link

Re: [Xen-users] Bonding...again

On Tue, Aug 18, 2009 at 3:38 AM, Adam Wead<awead@indiana.edu>
wrote:> Thanks, Dustin.
> I used your script and it seems to work... I couldn''t get my setup
to work
> with the alias that''s off of the bond devices, but it works when I
used the
> bond device directly.
> best,
Glad to hear it. So all is working for you now?
>> > > 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?
I usually say "when using bridged setup, treat dom0 like a L2 or L3
switch. Get help from your networking guys if you''re not familiar with
vlans and switches". So if your dom0 IP is also located on vlan2, then
you need to put the ip address on xenbr0 (or whatever bridge bond0.2
is located). This is similar to L3 switch setup.

For other vlans, if you don''t need dom0 to have logical access to it,
you don''t need to put IP address on the bridge. It can be up with no
IP address on dom0. This is similar to L2 switch setup.

On my implementations I usually use a separate interface for dom0
management IP, with bonding/vlan/bridges on other interfaces similar
to L2 switch setup.

-- 
Fajar

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

Wead, Adam G

2009-Aug-19 13:05 UTC

head link

RE: [Xen-users] Bonding...again

Hi Fajar,

Thanks... yes, I think it is.  Dustin''s script seems to do the trick. 
I''ve got another machine that I''ll experiment with the VLAN
options.  I''d like to figure that out just for my own understanding.

Thanks again (everyone) for all the help.

...adam

________________________________________
From: Fajar A. Nugraha [fajar@fajar.net]
Sent: Monday, August 17, 2009 11:05 PM
To: Wead, Adam G
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Bonding...again

On Tue, Aug 18, 2009 at 3:38 AM, Adam Wead<awead@indiana.edu>
wrote:> Thanks, Dustin.
> I used your script and it seems to work... I couldn''t get my setup
to work
> with the alias that''s off of the bond devices, but it works when I
used the
> bond device directly.
> best,
Glad to hear it. So all is working for you now?
>> > > 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?
I usually say "when using bridged setup, treat dom0 like a L2 or L3
switch. Get help from your networking guys if you''re not familiar with
vlans and switches". So if your dom0 IP is also located on vlan2, then
you need to put the ip address on xenbr0 (or whatever bridge bond0.2
is located). This is similar to L3 switch setup.

For other vlans, if you don''t need dom0 to have logical access to it,
you don''t need to put IP address on the bridge. It can be up with no
IP address on dom0. This is similar to L2 switch setup.

On my implementations I usually use a separate interface for dom0
management IP, with bonding/vlan/bridges on other interfaces similar
to L2 switch setup.

--
Fajar

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

Xen users - Aug 2009 - Bonding...again

[Xen-users] Bonding...again

RE: [Xen-users] Bonding...again

Re: [Xen-users] Bonding...again

Re: [Xen-users] Bonding...again

Re: [Xen-users] Bonding...again

Re: [Xen-users] Bonding...again

Re: [Xen-users] Bonding...again

Re: [Xen-users] Bonding...again

RE: [Xen-users] Bonding...again