Hi, I am using heartbeat-2.1.2-2.i386.rpm, heartbeat-pils-2.1.2-2.i386. rpm, heartbeat-stonith-2.1.2-2.i386.rpm packages on RHEL 5.5.
I have 3 nodes and I only use cluster IP as resource. When I start heartbeat service on all nodes, node1 takes cluster IP. But, after about 2-3 days all 3 nodes got cluster IP, at the same time. Also I want node priority as node1, node2, node3. Sometimes node2 has cluster IP even heartbeat on node1 is running. I also attached my configuration files. Am I doing something wrong in the configurations? I am stucked with this problem, any help would be appreciated. Thanks!
authkeys_node1
Description: Binary data
authkeys_node2
Description: Binary data
authkeys_node3
Description: Binary data
<cib generated="false" admin_epoch="0" epoch="2" num_updates="1" have_quorum="false" ignore_dtd="false" num_peers="0" cib_feature_revision="1.3" cib-last-written="Thu Jan 9 20:55:52 2014" ccm_transition="1"> <configuration> <crm_config> <cluster_property_set id="cib-bootstrap-options"> <attributes> <nvpair id="no_quorum_policy" name="no-quorum-policy" value="ignore"/> </attributes> </cluster_property_set> </crm_config> <nodes> <node id="c141f967-b7db-467d-9396-dcd967a528b3" uname="geo1.netas.com" type="normal"/> <node id="5c5c652d-1af9-442d-9bab-fc76017a71f9" uname="geo2.netas.com" type="normal"/> <node id="fe3a44d3-ca01-4532-9250-6032a7c1c283" uname="geo3.netas.com" type="normal"/> </nodes> <resources> <primitive id="failover-ip" class="ocf" type="IPaddr" provider="heartbeat"> <operations> <op id="failover-ip-monitor" name="monitor" interval="10s"/> </operations> <instance_attributes id="failover-ip-attribs"> <attributes> <nvpair id="failover-ip-addr" name="ip" value="47.168.138.39"/> </attributes> </instance_attributes> </primitive> </resources> <constraints/> </configuration> </cib>
<cib generated="false" admin_epoch="0" epoch="0" num_updates="0" have_quorum="false" ignore_dtd="false" num_peers="0" cib-last-written="Thu Jan 9 20:58:06 2014"> <configuration> <crm_config> <cluster_property_set id="cib-bootstrap-options"> <attributes> <nvpair id="no_quorum_policy" name="no-quorum-policy" value="ignore"/> </attributes> </cluster_property_set> </crm_config> <nodes> <node id="c141f967-b7db-467d-9396-dcd967a528b3" uname="geo1.netas.com" type="normal"/> <node id="5c5c652d-1af9-442d-9bab-fc76017a71f9" uname="geo2.netas.com" type="normal"/> <node id="fe3a44d3-ca01-4532-9250-6032a7c1c283" uname="geo3.netas.com" type="normal"/> </nodes> <resources> <primitive id="failover-ip" class="ocf" type="IPaddr" provider="heartbeat"> <operations> <op id="failover-ip-monitor" name="monitor" interval="10s"/> </operations> <instance_attributes id="failover-ip-attribs"> <attributes> <nvpair id="failover-ip-addr" name="ip" value="47.168.138.39"/> </attributes> </instance_attributes> </primitive> </resources> <constraints/> </configuration> </cib>
<cib generated="false" admin_epoch="0" epoch="0" num_updates="0" have_quorum="false" ignore_dtd="false" num_peers="0" cib-last-written="Wed Jan 8 13:18:07 2014"> <configuration> <crm_config> <cluster_property_set id="cib-bootstrap-options"> <attributes> <nvpair id="no_quorum_policy" name="no-quorum-policy" value="ignore"/> </attributes> </cluster_property_set> </crm_config> <nodes> <node id="c141f967-b7db-467d-9396-dcd967a528b3" uname="geo1.netas.com" type="normal"/> <node id="5c5c652d-1af9-442d-9bab-fc76017a71f9" uname="geo2.netas.com" type="normal"/> <node id="fe3a44d3-ca01-4532-9250-6032a7c1c283" uname="geo3.netas.com" type="normal"/> </nodes> <resources> <primitive id="failover-ip" class="ocf" type="IPaddr" provider="heartbeat"> <operations> <op id="failover-ip-monitor" name="monitor" interval="10s"/> </operations> <instance_attributes id="failover-ip-attribs"> <attributes> <nvpair id="failover-ip-addr" name="ip" value="47.168.138.39"/> </attributes> </instance_attributes> </primitive> </resources> <constraints/> </configuration> </cib>
ha_node1.cf
Description: Binary data
ha_node2.cf
Description: Binary data
ha_node3.cf
Description: Binary data
_______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems