Comments on: High Availability Xen http://www.santaba.com/blog/archives/3 Interesting things in making the web bigger, faster, better at Santaba Corp Fri, 06 Aug 2010 17:31:48 +0000 hourly 1 http://wordpress.org/?v=3.1 By: Eric http://www.santaba.com/blog/archives/3/comment-page-1#comment-12 Eric Tue, 16 Oct 2007 07:20:08 +0000 http://www.santaba.com/blog/?p=3#comment-12 This is exactly what I expected to find out after reading the title High Availability Xen. Thanks for informative article This is exactly what I expected to find out after reading the title High Availability Xen. Thanks for informative article

]]> By: Daniel http://www.santaba.com/blog/archives/3/comment-page-1#comment-11 Daniel Mon, 15 Oct 2007 22:47:13 +0000 http://www.santaba.com/blog/?p=3#comment-11 I couldn't understand some parts of this article High Availability Xen, but I guess I just need to check some more resources regarding this, because it sounds interesting. I couldn’t understand some parts of this article High Availability Xen, but I guess I just need to check some more resources regarding this, because it sounds interesting.

]]> By: hervé http://www.santaba.com/blog/archives/3/comment-page-1#comment-5 hervé Tue, 04 Sep 2007 18:06:53 +0000 http://www.santaba.com/blog/?p=3#comment-5 i made improvement on my conf yesteday i made a wrapper called by xend-config.sxp and it bind my bridge correctly now it work fine I don't brigde the bonding because only dom0 use it i made improvement on my conf yesteday
i made a wrapper called by xend-config.sxp and it bind my bridge correctly
now it work fine
I don’t brigde the bonding because only dom0 use it

]]> By: admin http://www.santaba.com/blog/archives/3/comment-page-1#comment-4 admin Fri, 31 Aug 2007 22:35:44 +0000 http://www.santaba.com/blog/?p=3#comment-4 I did not modify the network-bridge script. I played with various permutations of it (mainly figuring out why bonded NICs were treated so differently that regular nics), but no need to change it. (The answer is that the bond NIC doesn't have the equivalent veth interface from the netloop module that physical NICs do.) I haven't had to increase the number of interfaces (and if you run bonding, you probably wont either as the loopback interfaces aren't used with bonding.) Try setting options netloop nloopbacks=8 in /etc/modprobe.conf.local I did not modify the network-bridge script. I played with various permutations of it (mainly figuring out why bonded NICs were treated so differently that regular nics), but no need to change it. (The answer is that the bond NIC doesn’t have the equivalent veth interface from the netloop module that physical NICs do.)

I haven’t had to increase the number of interfaces (and if you run bonding, you probably wont either as the loopback interfaces aren’t used with bonding.)
Try setting options netloop nloopbacks=8 in /etc/modprobe.conf.local

]]> By: hervé http://www.santaba.com/blog/archives/3/comment-page-1#comment-3 hervé Fri, 31 Aug 2007 16:52:59 +0000 http://www.santaba.com/blog/?p=3#comment-3 hi steve I am also working on high availibility XEN datacenter My conf - 2 servers, 4 opteron, 7 network cards, SLES10 SP1 - 1 server, 2 opteron, 5 network card sun solaris + ZFS (in ISCSI mode) - 1 switch HP 1700 802.3ad (dedicated switch for the SAN) i use 4 network card per server for a bonding in 802.3ad and bind iscsi target on ZFS SAN with this bond and it work fine The other 3 netcard (in sles server) are for lan1, lan2, dmz perf are astonishing still i don't start xen !!! standard xend-config.sxp only bind one card (eth1 !!!), i can bind other card manually but perf are slow network-bridge stop network-bridge start netdev=eth0 .. etc etc i didnt try to start the bridge on bond0 manually Did you modify your network-script ? i also have problem with the number of interface . i tried modprobe loopback.nloopbacks=32 but network-script don't care 8-( have you info about surch conf ? if you want info about sles and ZFS SAN call me best regards hi steve

I am also working on high availibility XEN datacenter

My conf

- 2 servers, 4 opteron, 7 network cards, SLES10 SP1
- 1 server, 2 opteron, 5 network card sun solaris + ZFS (in ISCSI mode)
- 1 switch HP 1700 802.3ad (dedicated switch for the SAN)

i use 4 network card per server for a bonding in 802.3ad and bind iscsi target on ZFS SAN with this bond and it work fine

The other 3 netcard (in sles server) are for lan1, lan2, dmz

perf are astonishing still i don’t start xen !!!

standard xend-config.sxp only bind one card (eth1 !!!), i can bind other card manually but perf are slow

network-bridge stop
network-bridge start netdev=eth0 .. etc etc

i didnt try to start the bridge on bond0 manually

Did you modify your network-script ?

i also have problem with the number of interface . i tried modprobe loopback.nloopbacks=32 but network-script don’t care 8-(

have you info about surch conf ?

if you want info about sles and ZFS SAN call me

best regards

]]>