Each instance of the external IBM RSA stonith resource agent (ibmrsa-telnet) can only poweroff a single node and it is not clone aware. This means you have to provide a primitive resource per node to shoot.
This external stonith plugin uses the possibility to connect via telnet to the RSA board to reboot the node. It does not requires the IBM tool 'MPCli.sh' which consumes relative much resources.
The following example is a snippet which shoots node01 if requested. Put this snippet to a file 'file.xml', change values appropriately and put the whole stuff to a running HAv2 cluster via cibadmin -M -x 'file.xml'
The constraint guarantees that the stonith resource agent does not run on the node which has to be shot in case. Suicide is not allowed at the moment (2008-01-27).
<?xml version="1.0" ?>
<cib>
<configuration>
<resources>
<primitive id="r_stonith-node01" class="stonith" type="external/ibmrsa-telnet" provider="heartbeat" resource_stickiness="INFINITY">
<operations>
<op name="monitor" interval="60" timeout="300" prereq="nothing" id="r_stonith-node01-mon"/>
<op name="start" timeout="180" id="r_stonith-node01-start"/>
<op name="stop" timeout="180" id="r_stonith-node01-stop"/>
</operations>
<instance_attributes id="r_stonith-node01">
<attributes>
<nvpair id="r_stonith-node01-nodename" name="nodename" value="node01"/>
<nvpair id="r_stonith-node01-ipaddr" name="ipaddr" value="192.168.0.1"/>
<nvpair id="r_stonith-node01-userid" name="userid" value="userid"/>
<nvpair id="r_stonith-node01-passwd" name="passwd" value="password"/>
</attributes>
</instance_attributes>
</primitive>
</resources>
<constraints>
<rsc_location id="r_stonith-node01_hates_node01" rsc="r_stonith-node01">
<rule id="r_stonith-node01_hates_node01_rule" score="-INFINITY">
<expression attribute="#uname" id="r_stonith-node01_hates_node01_expr" operation="eq" value="node01"/>
</rule>
</rsc_location>
</constraints>
</configuration>
</cib>
(contributed by Andreas Mock)