[Pacemaker] Stonith Device APC AP7900

Pavlos Parissis pavlos.parissis at gmail.com
Tue Nov 2 03:08:32 EDT 2010

On 1 November 2010 15:01, Rick Cone <rcone at securepaymentsystems.com> wrote:

> Dejan,
> Below I had:
> primitive res_stonith stonith:apcmastersnmp \
>         params ipaddr="" port="161" community="sps" \
>         op start interval="0" timeout="60s" \
>         op monitor interval="60s" timeout="60s" \
>          op stop interval="0" timeout="60s"
> clone rc_res_stonith res_stonith \
>         meta target-role="Started"
> And you commented:
> You can also use a single instance setup, i.e. without clones.
> What is this "single instance setup", and what would it look like in the
> crm
> configure?

You have one already, res_stonith  is your single instance setup.

What are the pros/cons to this compared to the clone setup I
> have?

The decision of cloned or non-cloned stonith resource is mainly driven about
the ability of the fencing device to accept multiple connections
If you fencing device doesn't allow that then you can only use a non-cloned
The cloned resource will fence a node a bit faster in a case stonith
resource is running on the node to be fenced, there is no need to move the
resource to another node and then fence the node.
But, cloned resource is has a bit more complex configuration. cloning looks
easy but I bet there is some complexity behind it.

I have experiment with both versions on AP9606 using the rackpdu agent and
in both cases worked as expected. Now I am expecting a Aviosys 9258ST and I
will use the non-cloned version.

My 2 cents,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101102/d18dad35/attachment-0001.html>

More information about the Pacemaker mailing list