On 06/29/2012 11:48 AM, EXTERNAL Konold Martin (erfrakon, RtP2/TEF72) wrote: > Hi, > > I am in the process to setup a cluster using HP iLo3 as stonith devices using > SLES11 SP2 HA Extension. (I used formerly heartbeat-1 clusters successfully). > > I defined the following primitives for stonith fencing. > > primitive st-ilo-rt-lxcl9ar stonith:ipmilan \ > params hostname="rt-lxcl9ar.de.bosch.com" ipaddr="10.13.172.85" > port="623" auth="straight" priv="admin" login="stonith" password="secret > " > primitive st-ilo-rt-lxcl9br stonith:ipmilan \ > params hostname="rt-lxcl9br.de.bosch.com" ipaddr="10.13.172.93" > port="623" auth="straight" priv="admin" login="stonith" password="secret" > > Using the location keyword I made sure that the stonith is not running on its > own node: > > location l-st-rt-lxcl9a st-ilo-rt-lxcl9ar -inf: rt-lxcl9a > location l-st-rt-lxcl9b st-ilo-rt-lxcl9br -inf: rt-lxcl9b > > crm(live)configure# verify leads to some warnings: > > WARNING: Resources st-ilo-rt-lxcl9ar,st-ilo-rt-lxcl9br violate uniqueness for > parameter "port": "623" > WARNING: Resources st-ilo-rt-lxcl9ar,st-ilo-rt-lxcl9br violate uniqueness for > parameter "password": "secret" > WARNING: Resources st-ilo-rt-lxcl9ar,st-ilo-rt-lxcl9br violate uniqueness for > parameter "auth": "straight" > WARNING: Resources st-ilo-rt-lxcl9ar,st-ilo-rt-lxcl9br violate uniqueness for > parameter "priv": "admin" > > I now have two questions. > > 1. Why does crm the two distrinct primitives st-ilo-rt-lxcl9ar and > st-ilo-rt-lxcl9br to have different parameters? Is this an error in > stonith:ipmilan? >
yes, this is an error in the metadata of ipmilan ... but you should still be able to commit that configuration. > 2. Is stonith:ipmilan the correct stonith driver for HP iLo3 (DL380 G7)? If > yes, how to test if it is really working? well, I personally prefer external/ipmi ... used it on several management cards including ilos without a problem. You can use the "stonith" command to test it prior to cluster integration .... or -- once configured in pacemaker -- you can also do a "kill -9 corosync" on a node and hopefully see it being fenced. Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now > > Best regards > > Martin Konold > > Robert Bosch GmbH > Automotive Electronics > Postfach 13 42 > 72703 Reutlingen > GERMANY > www.bosch.com > > Tel. +49 7121 35 3322 > > Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; > Aufsichtsratsvorsitzender: Hermann Scholl; Geschäftsführung: Franz > Fehrenbach, Siegfried Dais; > Stefan Asenkerschbaumer, Bernd Bohr, Rudolf Colm, Volkmar Denner, Christoph > Kübel, Uwe Raschke, > Wolf-Henning Scheider, Werner Struth, Peter Tyroller > > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
