On Mon, Sep 7, 2009 at 8:24 PM, Michael Schwartzkopff<[email protected]> wrote: > Am Montag, 7. September 2009 17:35:36 schrieb Michael Hale: >> > 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> > > Ressource is called "pingd".
Not so in newer versions. ping is a new, simpler, RA that is more reliable because it uses the system "ping" program to obtain results. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
