Re: [Xen-users] CentOS 5.3 bond0 and xen 3.3.0

[jonr@xxxxxxxxxx]

Quoting Mike Brady <mike.brady@xxxxxxxxxxxxxx>:

> That would be because both Xen and RHEL/Centos are broken when it comes
> to bonded bridged interfaces.
>
> There are various approaches to making it work.  My notes on how I am
> currently doing it are below.  Change interfaces, addresses and
> BONDING_OPTS for your local requirements.
>
> Bonding/Trunking
> Bonding/Trunking is supported out of the box on RHEL/Centos, but it does
> not work when combined with a bridge for Xen as of RHEL/Centos 5.3. This
> has been reported as bug 463014
> (https://bugzilla.redhat.com/show_bug.cgi?id=463014) which has a simple
> patch for /etc/sysconfig/network-scripts/ifup-eth.
>
> The standard Xen network-script does not support bonded interfaces at
> all as it takes the interface down, which breaks the bond.
>
> Note that the instructions below use the Red Hat init scripts to setup
> xenbr0. The Xen script that normally does this is disabled.
>
> Apply the patch from https://bugzilla.redhat.com/show_bug.cgi?id=463014
>
> Configure Bond on RHEL/Centos
> /etc/modprobe.conf
> alias bond0 bonding
>
> /etc/sysconfig/network-srcipt/ifcfg-xenbr0
> DEVICE=xenbr0
> BOOTPROTO=none
> ONBOOT=yes
> TYPE=Bridge
> NETMASK=255.255.255.0
> NETWORK=192.168.42.0
> IPADDR=192.168.42.41
>
> /etc/sysconfig/network-srcipt/ifcfg-bond0
> DEVICE=bond0
> BOOTPROTO=none
> ONBOOT=yes
> TYPE=Ethernet
> BONDING_OPTS='mode=2 miimon=100 xmit_hash_policy=1'
> BRIDGE=xenbr0
>
> /etc/sysconfig/network-srcipt/ifcfg-eth0
> DEVICE=eth0
> USERCTL=no
> ONBOOT=yes
> MASTER=bond0
> SLAVE=yes
> BOOTPROTO=none
> HWADDR=00:15:17:55:C1:D0
>
> /etc/sysconfig/network-srcipt/ifcfg-eth1
> DEVICE=eth1
> USERCTL=no
> ONBOOT=yes
> MASTER=bond0
> SLAVE=yes
> BOOTPROTO=none
> HWADDR=00:15:17:55:C1:D1
>
> To configure Xen to use the bond in /etc/xen/xend-config.sxp
> change the network-script and vif-script lines to the following
>
> (network-script '/bin/true')
> (vif-script 'vif-bridge bridge=xenbr0')
>
> Reboot.
Thanks Mike! I now have everything coming up nicely. I had looked at  
that patch before but had been finding different solutions to what  
seemed like the same problem. Your run down of what needs to happen  
finally brought everything into focus.
I now have one problem left. :)

I cannot ping from the dom0 and I am not sure where to look for any problems.

I have configured my system as you have shown above, except I put in  
my values.
I have dropped my firewall
turned off SELinux
Logs show nothing out of the ordinary and am seeing no errors in them,  
at least none that I notice.
I tcpdump on the gateway and I see the arp (who has) coming in and an  
arp reply coming back out but I only see "Destination Host Unreachable"
I have the two ports on the switch bonded as 802.3ad same as my ports  
on the dom0.
Any more help is appreciated,

Jon



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