The xml below works for me in a 4-node cluser (you need one clone
resource per node - fragment shows clone for first node):
<clone id="CL_stonithset_idm01">
<instance_attributes id="CL_stonithset_idm01">
<attributes>
<nvpair id="CL_stonithset_idm01_clone_node_max"
name="clone_node_max" value="1"/>
</attributes>
</instance_attributes>
<primitive id="CL_stonith_idm01" class="stonith"
type="external/riloe-ng" provider="heartbeat">
<operations>
<op name="monitor" interval="30s" timeout="20s"
id="CL_stonith_idm01_monitor"/>
<op name="start" timeout="60s" id="CL_stonith_idm01_start"/>
</operations>
<instance_attributes id="CL_stonith_idm01">
<attributes>
<nvpair id="CL_stonith_idm01_hostlist" name="hostlist"
value="idm01"/>
<nvpair id="CL_stonith_idm01_RI_HOST" name="RI_HOST" value="idm01"/>
<nvpair id="CL_stonith_idm01_RI_HOSTRI" name="RI_HOSTRI"
value="idm01-rm"/>
<nvpair id="CL_stonith_idm01_RI_LOGIN" name="RI_LOGIN"
value="Heartbeat"/>
<nvpair id="CL_stonith_idm01_RI_PASSWORD" name="RI_PASSWORD"
value="password"/>
</attributes>
</instance_attributes>
</primitive>
</clone>
Jure Pečar wrote:
> Hi all,
>
> I'm trying to configure iLo stonith with heartbeat 2.0.8.
> Calling external/riloe on the command line with all the RI_* variables in the
> environment works fine. Calling stonith -t external/riloe with RI_*
> variables and -S also reports OK. However, I'm having troubles figuring out
> how to put these variables in a file that I can call with -F. I haven't found
> any examples or documentation describing the syntax ...
>
> I figured that if I put all variables in signle line like this:
>
> RI_HOST=host RI_HOSTRI=host-ilo RI_LOGIN=Administrator RI_PASSWORD=password
>
> stonith doesn't complain about syntax but says "device not accessible". Why?
>
>
> Another related question: In a two-node cluster, should stonith config
> describe the iLo device of the local machine or of the other machine?
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
