<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi!<br>
<br>
I have used a small variety of fencing on my very small clusters.
My opinions here are all my own. ;-) Here's what I've had experience
with:<br>
<br>
* USB-capable APC Back-UPS with NUT (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a>).
It works and has served me well for two, three, and four node
clusters. With two-node clusters I cross-connect the nodes to each
other's UPSs, obviating the need for a third system to act as the
NUT server. (I detailed my experiences with setting up
UPS+NUT-based stonith on my blog:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://burning-midnight.blogspot.com/2012/08/vm-clusternow-with-stonith-on-budget.html">http://burning-midnight.blogspot.com/2012/08/vm-clusternow-with-stonith-on-budget.html</a>)
I would have larger clusters talk to a central (non-cluster) NUT
server; occasionally an interruption in communication would cause
the stonith resource to fail and thus make stonith impossible until
the failure was cleared, but luckily this seemed to be rare (and
non-existent in the cross-connected case).<br>
<br>
* APC PDU (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Model AP7900), via SNMP. These work very well for me, though I've
found you have to tweak the timing parameters in the stonith agent
to get it to work correctly (i.e. to shut down the outlet for
sufficient time, and not just a brief off-on operation). I like
them very much; they provide per-outlet control and are not too
expensive. Its web interface is also very handy for
remote-controlling both cluster and non-cluster systems.<br>
<br>
* IPMI on Supermicro-based motherboards. I've heard good things,
and not-so-good things. In my environment, issues with keeping
connected with IPMI was the reason I moved away from using it; the
IPMI would eventually just stop responding to commands. I suspect
it's an issue with the IPMI itself, something unresolved that only
Supermicro can fix. As with any stonith, test thoroughly. Some
folks do a two-step stonith: IPMI, then power, just to make
doubly-sure. <br>
<br>
Hope this helps!<br>
<br>
<br>
<div class="moz-cite-prefix">On 08/16/2013 06:13 PM, Nick Khamis
wrote:<br>
</div>
<blockquote
cite="mid:CAGWRaZbVSzqR3DkDzgztbnQaCD4q88e=wZcMfdv_Bg5iP1KbRw@mail.gmail.com"
type="cite">
<div dir="ltr">Hello Everyone,
<div><br>
</div>
<div style="">We are in the market for a new UPS. And would like
to know some of your experiences given the different means of
stonith (ie, ups, pdu, blade hardware). The UPS unit we are
looking at is:<a moz-do-not-send="true"
href="http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=SYA4K8RMP&total_watts=500">http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=SYA4K8RMP&total_watts=500</a>.
But before all that would like to know if <span
style="color:rgb(0,0,0);font-family:Georgia,serif;font-size:medium">RSA/iLO/DRAC
is the preferred way of implementing it?</span></div>
<div style=""><span
style="color:rgb(0,0,0);font-family:Georgia,serif;font-size:medium"><br>
</span></div>
<div style=""><span
style="color:rgb(0,0,0);font-family:Georgia,serif;font-size:medium">One
thing to think of is that with a UPS stonith, there is less
worry of drivers, kernel modules etc...? As for PDU level
stontih, can we really expect anything more from our PDU
other than distribution?</span></div>
<div style=""><span
style="color:rgb(0,0,0);font-family:Georgia,serif;font-size:medium"><br>
</span></div>
<div style=""><span
style="color:rgb(0,0,0);font-family:Georgia,serif;font-size:medium"><br>
</span></div>
<div style=""><font color="#000000" face="Georgia, serif"
size="3">Have more questions but for the sake of brevity...</font></div>
<div style=""><font color="#000000" face="Georgia, serif"
size="3"><br>
</font></div>
<div style=""><font color="#000000" face="Georgia, serif"
size="3"><br>
</font></div>
<div style=""><font color="#000000" face="Georgia, serif"
size="3">Kind Regards,</font></div>
<div style=""><font color="#000000" face="Georgia, serif"
size="3"><br>
</font></div>
<div style=""><font color="#000000" face="Georgia, serif"
size="3">Nick.</font></div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Pacemaker mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Thank you!
Matthew O'Connor
(GPG Key ID: 55F981C4)
CONFIDENTIAL NOTICE: The information contained in this electronic message is legally privileged, confidential and exempt from disclosure under applicable law. It is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return e-mail and delete the original message and any copies of it from your computer system. Thank you.
EXPORT CONTROL WARNING: This document may contain technical data that is subject to the International Traffic in Arms Regulations (ITAR) controls and may not be exported or otherwise disclosed to any foreign person or firm, whether in the US or abroad, without first complying with all requirements of the ITAR, 22 CFR 120-130, including the requirement for obtaining an export license if applicable. In addition, this document may contain technology that is subject to the Export Administration Regulations (EAR) and may not be exported or otherwise disclosed to any non-U.S. person, whether in the US or abroad, without first complying with all requirements of the EAR, 15 CFR 730-774, including the requirement for obtaining an export license if applicable. Violation of these export laws is subject to severe criminal penalties.</pre>
</body>
</html>