> You do not have any mechanism for the cluster to recornize the failure of
> network. No action is taken on the loss on the ping node.
>
> For the actual version of the cluster softwarte see:
> http://www.clusterlabs.org
>
> For examples of using pingnodes see:
> http://www.clusterlabs.org/mediawiki/images/f/fb/Configuration_Explained.pdf
Thanks for the pointers. After reading the docs I have come the
conclusion that I need to "Tell Pacemaker to monitor connectivity" and
"Tell Pacemaker how to interpret the connectivity data"
It looks like I need to add a ping primitive to my clone resource:
<resources>
<clone id="router">
<meta_attributes id="router_attributes">
<attributes>
<nvpair id="router_globally_unique" name="globally_unique"
value="true"/>
<nvpair id="router_target_role" name="target_role" value="started"/>
<!-- <nvpair id="router_resource_stickiness"
name="resource-stickiness" value="1"/> -->
</attributes>
</meta_attributes>
<primitive id="ping-gateway" provider="pacemaker" class="ocf" type="ping">
<operations>
<op id="ping-monitor-60s" interval="60s" name="monitor"/>
</operations>
<instance_attributes id="ping-attrs">
<nvpair id="pingd-dampen" name="dampen" value="5s"/>
<nvpair id="pingd-multiplier" name="multiplier" value="1000"/>
<nvpair id="pingd-hosts" name="host_list" value="172.16.209.2"/>
</instance_attributes>
</primitive>
<primitive id="clusterip" class="ocf" type="IPaddr2" provider="heartbeat">
<operations>
<op id="clusterip_monitor" name="monitor" interval="3s"/>
</operations>
<instance_attributes id="clusterip_attributes">
<attributes>
<nvpair id="clusterip_ip" name="ip" value="172.16.209.200"/>
<nvpair id="clusterip_hash_mode" name="clusterip_hash"
value="sourceip-sourceport"/>
<nvpair id="cluster_nic" name="nic" value="eth0"/>
<nvpair id="cluster_mac" name="mac" value="01:00:5e:10:D1:C8"/>
</attributes>
</instance_attributes>
</primitive>
</clone>
</resources>
and a constraint:
<constraints>
<rsc_location id="router-no-connectivity" rsc="router">
<rule id="ping-exclude-rule" score="-INFINITY" >
<expression id="ping-exclude" attribute="ping-gateway"
operation="not_defined"/>
</rule>
</rsc_location>
</constraints>
I updated my cluster with the above configuration, but it doesn't seem
to change anything. I'm sure I've just not getting something about the
configuration. Here is the output of crm_mon after restarting
heartbeat on both machines:
============
Last updated: Sun Sep 6 14:23:02 2009
Current DC: vm-ubuntu-2 (75031981-ed3c-40e9-b527-ccabe5a7e91d)
2 Nodes configured.
1 Resources configured.
============
Node: vm-ubuntu-1 (9b229d79-fceb-4cc7-b131-fd690e97a990): online
Node: vm-ubuntu-2 (75031981-ed3c-40e9-b527-ccabe5a7e91d): online
Full list of resources:
Clone Set: router
clusterip:0 (ocf::heartbeat:IPaddr2): Stopped
clusterip:1 (ocf::heartbeat:IPaddr2): Stopped
Failcount summary:
* Node vm-ubuntu-2:
* Node vm-ubuntu-1:
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
