[Linux-cluster] Re: help with fence_xvmd
Jeff Sturm
jeff.sturm at eprize.com
Wed May 13 19:38:02 UTC 2009
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of vu pham
> Sent: Wednesday, May 13, 2009 3:05 PM
> To: linux clustering
> Subject: Re: [Linux-cluster] Re: help with fence_xvmd
>
> You can overcome this by, if you use RHEL 5.3, adding -I
> vnet0 ( or whatever device which domain-0 uses to communicate
> with domU ) into the fence_xvmd 's parameter list .IIRC, this
> parm -I does not exist on RHEL
> 5.2 or ealier. You can do that by adding FENCE_XVMD_OPTS="-I
> vnet0" into /etc/sysconfig/cman.
On earlier versions you can also configure an explicit multicast route.
The following worked for us (xenbreth1 is the bridge device carrying the
DomU cluster traffic):
[root at xen01 ~]# cat /etc/sysconfig/network-scripts/route-xenbreth1
to multicast 224.0.0.0/4 dev xenbreth1
Jeff
More information about the Linux-cluster
mailing list