Hi All,
I have configured ha cluster with two nodes and two resources IP address and
httpd service. I am working with heartbeat-2.1.3-3.el5.centos CentOS 5.3.
I followed the
http://www.novell.com/documentation/sles10/heartbeat/?page=/documentation/sles10/heartbeat/data/heartbeat.html
documentation.
I want to discuss about 2 issues and 2 questions
Issue1:
I want to stop resources on a node if the network connection is not available
(default gateway is not reachable).
When I stop network of node 1 (using "service network stop" command) resources
are automatically launching on node2 but on node1 resources are still running.
Please check the below configuration and kindly advice me what is missing?
Sorry for the big xml but I have to share full configuration to check the
missing stuff.
Issue2:
Once the network is up resources running on node2 are moving to node1. In my
ha.cf file I have set auto_fallback false. But still resources are coming back
to node1. I don't want this. How to avoid this?
Question1
I want to implement a logic (quorum I suppose) which should enable me decide
whether to run resources on given node or not. This is required for me to avoid
accessing SAN simultaneously by two nodes. How to do this?
Question2
Is there any reference configuration (cib.xml) available for
HeartBeat+SAN+MySQL active-passive configuration.
<cib generated="true" admin_epoch="0" have_quorum="true" ignore_dtd="false"
num_peers="2" cib_feature_revision="2.0" epoch="137" num_updates="1"
cib-last-written="Tue Dec 1 21:14:22 2009" ccm_transition="2"
dc_uuid="1c45b92e-cf49-4aea-9a1d-c81ae906bb05">
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<attributes>
<nvpair id="cib-bootstrap-options-dc-version" name="dc-version"
value="2.1.3-node: 552305612591183b1628baa5bc6e903e0f1e26a3"/>
<nvpair id="cib-bootstrap-options-last-lrm-refresh"
name="last-lrm-refresh" value="1259682247"/>
</attributes>
</cluster_property_set>
</crm_config>
<nodes>
<node uname="srv-ind-rs8.vanenburg.com" type="normal"
id="1ab91a81-3daa-4757-9434-c977dbcea36a">
<instance_attributes id="nodes-1ab91a81-3daa-4757-9434-c977dbcea36a">
<attributes>
<nvpair name="standby"
id="standby-1ab91a81-3daa-4757-9434-c977dbcea36a" value="off"/>
</attributes>
</instance_attributes>
</node>
<node uname="srv-ind-rs9.vanenburg.com" type="normal"
id="1c45b92e-cf49-4aea-9a1d-c81ae906bb05">
<instance_attributes id="nodes-1c45b92e-cf49-4aea-9a1d-c81ae906bb05">
<attributes>
<nvpair name="standby"
id="standby-1c45b92e-cf49-4aea-9a1d-c81ae906bb05" value="off"/>
</attributes>
</instance_attributes>
</node>
</nodes>
<resources>
<group id="group1">
<meta_attributes id="group1_meta_attrs">
<attributes>
<nvpair name="target_role" id="group1_metaattr_target_role"
value="started"/>
<nvpair id="group1_metaattr_ordered" name="ordered" value="true"/>
<nvpair id="group1_metaattr_collocated" name="collocated"
value="true"/>
<nvpair id="group1_metaattr_is_managed" name="is_managed"
value="true"/>
</attributes>
</meta_attributes>
<primitive id="IP address" class="ocf" type="IPaddr2"
provider="heartbeat">
<instance_attributes id="IP address_instance_attrs">
<attributes>
<nvpair id="af1f551d-fbfa-4efb-b7ed-1139e374c0a1" name="ip"
value="10.192.60.97"/>
</attributes>
</instance_attributes>
<meta_attributes id="IP address_meta_attrs">
<attributes>
<nvpair id="IP address_metaattr_is_managed" name="is_managed"
value="true"/>
</attributes>
</meta_attributes>
</primitive>
<primitive id="httpd" class="lsb" type="httpd" provider="heartbeat">
<operations/>
<meta_attributes id="httpd_meta_attrs">
<attributes>
<nvpair id="httpd_metaattr_is_managed" name="is_managed"
value="true"/>
</attributes>
</meta_attributes>
</primitive>
</group>
<clone id="pingd-clone">
<meta_attributes id="pingd-clone_meta_attrs">
<attributes>
<nvpair id="pingd-clone_metaattr_target_role" name="target_role"
value="started"/>
<nvpair id="pingd-clone_metaattr_clone_max" name="clone_max"
value="2"/>
<nvpair id="pingd-clone_metaattr_clone_node_max"
name="clone_node_max" value="1"/>
</attributes>
</meta_attributes>
<primitive id="pingd" class="ocf" type="pingd" provider="heartbeat">
<instance_attributes id="pingd:0_instance_attrs">
<attributes>
<nvpair id="b62641f6-b85b-47b3-aaf3-db6e60983795" name="dampen"
value="1s"/>
</attributes>
</instance_attributes>
<meta_attributes id="pingd:0_meta_attrs">
<attributes/>
</meta_attributes>
</primitive>
</clone>
</resources>
<constraints>
<rsc_location id="switch_noconnectivity" rsc="group1">
<rule id="prefered_switch_noconnectivity" score="-INFINITY">
<expression attribute="pingd"
id="93ea7c3f-4939-48f7-9ea1-0f984b492eed" operation="not_defined"/>
</rule>
</rsc_location>
</constraints>
</configuration>
</cib>
Regards,
Prasad.
________________________________
The information contained in this communication is confidential, intended
solely for the use of the individual or entity to whom it is addressed and may
be legally privileged and protected by professional secrecy. Access to this
message by anyone else is unauthorized. If you are not the intended recipient,
any disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message in
error. This email does not constitute any commitment from Cordys Holding BV or
any of its subsidiaries except when expressly agreed in a written agreement
between the intended recipient and Cordys Holding BV or its subsidiaries.
Cordys is neither liable for the proper and complete transmission of the
information contained in this communication nor for any delay in its receipt.
Cordys does not guarantee that the integrity of this communication has been ma
intained nor that the communication is free of viruses, interceptions or
interference. If you are not the intended recipient of this communication
please return the communication to the sender and delete and destroy all copies.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
