RE: Re: help with fence_xvmd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: linux-cluster-bounces@xxxxxxxxxx 
> [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of vu pham
> Sent: Wednesday, May 13, 2009 3:05 PM
> To: linux clustering
> Subject: Re:  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@xen01 ~]# cat /etc/sysconfig/network-scripts/route-xenbreth1
to multicast 224.0.0.0/4 dev xenbreth1

Jeff


--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux