On Fri, Aug 17, 2012 at 12:09 PM, Yount, William D <[email protected]> wrote: > I have two servers. I am using pacemaker/cman(corosync). I am trying to share > an IP address between them. I would like the IP address to run on both > servers at the same time. However, my testing has shown that the IP address > stays locked onto Server2. If I put Server2 in standby, then the IP address > is no longer reachable even though it shows it is running on Server1. I was > wondering if anyone could spot the reason why in the configuration below:
You haven't enabled notifications for the clone. These are needed to tell the surviving clone instance that it should handle the bucket previous "owned" by the instance that was just stopped. > > <cib epoch="1177" num_updates="0" admin_epoch="0" > validate-with="pacemaker-1.2" cib-last-written="Thu Aug 16 20:49:46 2012" > crm_feature_set="3.0.6" update-origin="Server2" update-client="crmd" > have-quorum="1" dc-uuid=" Server1"> > <configuration> > <crm_config> > <cluster_property_set id="cib-bootstrap-options"> > <nvpair id="cib-bootstrap-options-dc-version" name="dc-version" > value="1.1.7-6.el6-148fccfd5985c5590cc601123c6c16e966b85d14"/> > <nvpair id="cib-bootstrap-options-cluster-infrastructure" > name="cluster-infrastructure" value="cman"/> > <nvpair id="cib-bootstrap-options-expected-quorum-votes" > name="expected-quorum-votes" value="2"/> > <nvpair id="cib-bootstrap-options-stonith-enabled" > name="stonith-enabled" value="false"/> > <nvpair id="cib-bootstrap-options-no-quorum-policy" > name="no-quorum-policy" value="ignore"/> > <nvpair id="cib-bootstrap-options-last-lrm-refresh" > name="last-lrm-refresh" value="1345168331"/> > </cluster_property_set> > </crm_config> > <nodes> > <node id=" Server1" type="normal" uname="Server1"> > <instance_attributes id="nodes-Server1"> > <nvpair id="nodes- Server1-standby" name="standby" value="off"/> > </instance_attributes> > </node> > <node id="Server2" type="normal" uname="Server2"> > <instance_attributes id="nodes-Server2"> > <nvpair id="nodes- Server2-standby" name="standby" value="off"/> > </instance_attributes> > </node> > </nodes> > <resources> > <clone id="cl_IPaddr2_1"> > <meta_attributes id="cl_IPaddr2_1-meta_attributes"> > <nvpair id="cl_IPaddr2_1-meta_attributes-clone-max" > name="clone-max" value="2"/> > <nvpair id="cl_IPaddr2_1-meta_attributes-notify" name="notify" > value="true"/> > <nvpair id="cl_IPaddr2_1-meta_attributes-interleave" > name="interleave" value="true"/> > </meta_attributes> > <primitive id="res_IPaddr2_1" class="ocf" provider="heartbeat" > type="IPaddr2"> > <instance_attributes id="res_IPaddr2_1-instance_attributes"> > <nvpair id="nvpair-res_IPaddr2_1-ip" name="ip" > value="10.89.99.30"/> > <nvpair id="nvpair-res_IPaddr2_1-cidr_netmask" > name="cidr_netmask" value="22"/> > </instance_attributes> > <operations id="res_IPaddr2_1-operations"> > <op interval="0" id="op-res_IPaddr2_1-start" name="start" > timeout="20"/> > <op interval="0" id="op-res_IPaddr2_1-stop" name="stop" > timeout="20"/> > <op id="op-res_IPaddr2_1-monitor" name="monitor" interval="10" > timeout="20" start-delay="0"/> > </operations> > <meta_attributes id="res_IPaddr2_1-meta_attributes"/> > </primitive> > </clone> > </resources> > <constraints/> > <op_defaults> > <meta_attributes id="op-options"> > <nvpair id="op-options-timeout" name="timeout" value="240s"/> > </meta_attributes> > </op_defaults> > <rsc_defaults> > <meta_attributes id="rsc-options"> > <nvpair id="rsc-options-resource-stickiness" > name="resource-stickiness" value="100"/> > </meta_attributes> > </rsc_defaults> > </configuration> > </cib> > > > Thanks, > William > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
