WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Need Help with Fence_xvm

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Need Help with Fence_xvm
From: rafael@xxxxxxxxxxx
Date: Mon, 25 Apr 2011 13:32:49 -0400 (EDT)
Delivery-date: Mon, 25 Apr 2011 10:34:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Dear Xen Users,

I am new to this technology and I've been reading all over the places about how to setup a cluster infrasctructre using Xen DOM0 and Xen DOMu Domains.

So far I have quite a few parts running (cluster) but I am trying to add a (virtual) fencing method. I have read that I can use (Virtual Fencing) using the fence_xvmd-fence_xvm deamon and agents; that will allow me to restart successfully any (Virtual-Machine) also known (DomU) from the actual Host Machine (Dom-0).

Here is my Infrasctructure.

2 Hosts Machines ( Dom-0 >> mxen0 --- Dom0 >> mxen1 )
2 Guest Machines hosted in each host machine ( Domu >> host1.testlab.local (living in mxen0) Domu >> host2.testlab.local (living in mxen1)
1 Cluster created between Hosts Machines with quorum partition using iscsi San device ( >> hostcluster )
--- <?xml version="1.0"?>
<cluster alias="hostcluster" config_version="20" name="hostcluster">
<fence_daemon clean_start="0" post_fail_delay="10" post_join_delay="600"/>
<clusternodes>
<clusternode name="----" nodeid="1" votes="1">
<fence>
<method name="1">
<device name="iSCSI" node="mxen1"/>
</method>
<method name="2">
<device name="mxen1"/>
</method>
</fence>
</clusternode>
<clusternode name="----" nodeid="2" votes="1">
<fence>
<method name="1">
<device name="iSCSI" node="mxen0"/>
</method>
<method name="2">
<device name="mxen0"/>
</method>
</fence>
</clusternode>
</clusternodes>
<cman broadcast="yes" expected_votes="3"/>
<fencedevices>
<fencedevice agent="fence_ipmilan" ipaddr="10.10.10.55" login="root" name="mxen0" passwd="----"/>
<fencedevice agent="fence_ipmilan" ipaddr="10.10.10.56" login="root" name="mxen1" passwd="----"/>
<fencedevice agent="fence_scsi" name="iSCSI"/>
</fencedevices>
<rm>
<failoverdomains/>
<resources/>
</rm>
<fence_xvmd/>
<quorumd interval="1" label="quorumhost" min_score="1" tko="10" votes="1">
<heuristic interval="1" program="ping -c2 -t1 192.168.0.1" score="1"/>
<heuristic interval="1" program="ping -c2 -t1 192.168.1.1" score="1"/>
</quorumd>
</cluster>

1 Cluster created between the Virtual Machines with quorum partition using iscsi san device ( >> fwdcluster )

<?xml version="1.0"?>
<cluster alias="fwdcluster" config_version="9" name="fwdcluster">
<fence_daemon clean_start="0" post_fail_delay="10" post_join_delay="600"/>
<clusternodes>
<clusternode name="mx3.enflyer.com" nodeid="1" votes="1">
<fence>
<method name="1">
<device domain="---- name="xenvm"/>
</method>
</fence>
</clusternode>
<clusternode name="mx5.enflyer.com" nodeid="2" votes="1">
<fence>
<method name="1">
<device domain="-----m" name="xenvm"/>
</method>
</fence>
</clusternode>
</clusternodes>
<cman expected_votes="3">
<multicast addr="239.192.0.1"/>
</cman>
<fencedevices>
<fencedevice agent="fence_xvm" name="xenvm"/>
</fencedevices>
<rm>
<failoverdomains/>
<resources/>
</rm>
<quorumd interval="1" label="fwdquorum" min_score="1" tko="10" votes="1">
<heuristic interval="1" program="ping -c2 -t1 192.168.0.1" score="1"/>
<heuristic interval="1" program="ping -c2 -t1 192.168.1.1" score="1"/>
</quorumd>
</cluster>

Now I have been following this guides that have been the only ones I've found on the NET ( http://sources.redhat.com/cluster/wiki/VMClusterCookbook http://miao5.blogspot.com/2008/12/xen-fencing-in-rhel5.html ) but I have not been able to fence neither of this Virtual-Machines using the same after mention method.

 

Here is my problem

 

on dom-u (testlab1) trying to fence domu (testlab2)

 

[root@mx3 ~]# fence_xvm -H mx5.enflyer.com -ddd -o null
Debugging threshold is now 3
-- args @ 0x7fff56c54b40 --
args->addr = 225.0.0.12
args->domain = testlab2.testlab.local
args->key_file = /etc/cluster/fence_xvm.key
args->op = 0
args->hash = 2
args->auth = 2
args->port = 1229
args->ifindex = 0
args->family = 2
args->timeout = 30
args->retr_time = 20
args->flags = 0
args->debug = 3
-- end args --
Reading in key file /etc/cluster/fence_xvm.key into 0x7fff56c53af0 (4096 max size)
Actual key length = 4096 bytesSending to 225.0.0.12 via 127.0.0.1
Sending to 225.0.0.12 via 10.0.10.57
Sending to 225.0.0.12 via 192.168.0.57
Sending to 225.0.0.12 via 192.168.1.57
Waiting for connection from XVM host daemon.
.................. continues for about a minute or so. and then....
Timed out waiting for response

 

Am I missing something ? I checked IPtables thinking was the connection (event disabled Iptables) still no resutls. Any sugestiongs I will gladly appreciate it.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Need Help with Fence_xvm, rafael <=