[Xen-users] More on SLES10, XEN, and bonding

["Ulrich Windl" <ulrich.windl@xxxxxxxxxxxxxxxxxxxx>]

Hi,

I see no light at the end of the tunnel: It seems configuration that's wrong 
works 
better than a correct configuration in SLES10:

A server that is running fine uses this script "my-network-bridge":
DIR=$(dirname "$0")
"$DIR/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
"$DIR/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1

However "eth0" is a bonding slave of bond0, while eth1 is a bonding slave of 
bond1. Wit hthis setup, xenbr0 has a broadcast address, and routing looks OK:
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 bond1
132.199.0.0     0.0.0.0         255.255.0.0     U         0 0          0 bond0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo

With a correct script like:
DIR=$(dirname "$0")
"$DIR/network-bridge" "$@" vifnum=0 netdev=bond0 bridge=xenbr0
"$DIR/network-bridge" "$@" vifnum=1 netdev=bond1 bridge=xenbr1

xenbr0 has got as IP address and a unicast MAC assigned, and routing in Dom0 
goes 
to the bridges:
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 xenbr1
132.199.0.0     0.0.0.0         255.255.0.0     U         0 0          0 xenbr0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo

With this machine I have all kinds of strange network problems, and I'm unable 
to 
get out. The SLES10 script does this for bonding devices, and I don't 
understand 
it:

"network-bridge" has this setup for bonding devices:

        ip link set ${bridge} arp on
        add_to_bridge ${bridge} ${vif0}
        ip link set ${vif0} up
        add_to_bridge2 ${bridge} ${netdev}
        transfer_addrs  ${netdev} ${bridge}
        transfer_routes ${netdev} ${bridge}

while for non-bonding devices the setup is like this:

        mac=`ip link show ${netdev} | grep 'link\/ether' | sed -e 's/.*ether 
\(..:..:..:..:..:..\).*/\1/'`
        ifup ${netdev}  # To ensure there is an IP to transfer
        transfer_addrs ${netdev} ${vdev}
        ifdown ${netdev}
        ip link set ${netdev} name ${pdev}
        ip link set ${vdev} name ${netdev}

        setup_bridge_port ${pdev}
        setup_bridge_port ${vif0}
        ip link set ${netdev} addr ${mac} arp on

        ip link set ${bridge} up
        add_to_bridge ${bridge} ${vif0}
        add_to_bridge2 ${bridge} ${pdev}
        ip link set ${netdev} up
        ifup ${hwddev}

Sorry, but this is all a big incomprehensible mess! Did anybody succeed with 
XEN, 
two bridges and bonding? Plus maybe the necessary adjustments to the SuSE 
Firewall...

Regards,
Ulrich


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