[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Re: debian wheezy interface bonding (dom0) / xen 4.1.2*
Am 28.08.2011 12:18, schrieb Pasi Kärkkäinen: On Sat, Aug 27, 2011 at 11:16:09PM +0200, Mark Schneider wrote:Hello Pasi, Thank you for your hints due to my questions about interface bonding and xen HVMs. I have commented out the network-script line in /etc/xen/xend-config.sxp and tested a bit around (s. below): ### (network-script network-bridge) ### (network-script 'network-bridge netdev=bond0 antispoof=yes') I have tried to use "bridge_ports bond0" and activated config for bond0 but it didn't worked as I expected. *Would you expect that such "bond0-config" also should work?*You should do one step at a time. First get the bond0 working without any Xen stuff. When bond0 works from dom0, then add bond0 to the bridge. Bond0 works already (without xen) I use Extreme switch cluster with sharing group for eth0 and eth2 (VLAN LAN1 ports 1:9 and 2:9) so there is no danger to get any loops as they act only with one MAC-address (s. below). The second entry is another VLAN (ICON) with ports 1:19 and 2.19.Maybe you would like to put some parts of my config into your wiki xen-networking pages. auto xenbr0 iface xenbr0 inet static address 192.168.1.150 network 192.168.1.0 broadcast 192.168.1.255 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports eth0 eth2 #bridge_ports bond0This looks dangerous. Having both eth0 and eth2 in the same bridge could cause a loop in the network! Slot-1 Stack.1 # show fdb Mac Vlan Age Flags Port / Virtual Port List ----------------------------------------------------------------------------- b4:99:ba:c1:27:36 LAN1(0010) 0034 d m 1:9 b4:99:ba:c1:27:38 ICON(0070) 0031 d m 1:19The question is if e.g. setting with "bridge_ports bond1" should work for xen (like below)? # --- auto bond1 iface bond1 inet static slaves eth1 eth3 bond-mode active-backup #bond-mode 802.3ad bond-miimon 100 bond-downdelay 200 bond-updelay 200 auto xenbr1 iface xenbr1 inet static address 10.0.1.150 network 10.0.1.0 broadcast 10.0.1.255 netmask 255.255.255.0 gateway 10.0.1.1 #bridge_ports eth1 eth3 bridge_ports bond1 # --- Thank you / regards, Mark -- Pasi#auto bond1 #iface bond1 inet static # address 10.0.1.150 # netmask 255.255.255.0 # network 10.0.1.0 # broadcast 10.0.1.255 # gateway 10.0.1.1 # slaves eth1 eth3 # bond-mode active-backup # #bond-mode 802.3ad # bond-miimon 100 # bond-downdelay 200 # bond-updelay 200 auto xenbr1 iface xenbr1 inet static address 10.0.1.150 network 10.0.1.0 broadcast 10.0.1.255 netmask 255.255.255.0 gateway 10.0.1.1 bridge_ports eth1 eth3 #bridge_ports bond1 #auto xenbr0 #iface xenbr0 inet static # bridge_ports eth0 eth2 # address 192.168.1.150 # broadcast 192.168.1.255 # netmask 255.255.255.0 # gateway 192.168.1.1 #auto xenbr1 #iface xenbr1 inet static # bridge_ports eth1 # address 192.168.1.151 # broadcast 192.168.1.255 # netmask 255.255.255.0 # gateway 192.168.1.1 # #auto xenbr2 #iface xenbr2 inet static # bridge_ports eth2 # address 10.0.1.152 # broadcast 10.0.1.255 # netmask 255.255.255.0 # gateway 10.0.1.1 # #auto xenbr3 #iface xenbr3 inet static # bridge_ports eth3 # address 10.0.1.153 # broadcast 10.0.1.255 # netmask 255.255.255.0 # gateway 10.0.1.1 # --- root@xen411dom0:/ftp/HVM# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.b499bac12736 no eth0 eth2 vif4.0 vif5.0 xenbr1 8000.b499bac12738 no eth1 eth3 vif5.1 root@xen411dom0:/ftp/HVM# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1536 2 r----- 527.2 squeezehvm.born2b3.net 4 8192 4 -b---- 14.9 wheezyhvm.born2b3.net 5 8192 8 -b---- 23.3 Best regards, Mark -- ms@xxxxxxxxxxxxxxxxxxxxxx_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users -- ms@xxxxxxxxxxxxxxxxxxxxxx _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |