Bob, as we've discussed a few other times recently, when you're testing (and depending on your preference in production), you may want to set the stonith policy to 'poweroff' as opposed to 'reboot'.
Also, if you have a two-node cluster, pacemaker depends on quorum and the loss thereof creates another stonith event. You'll want to set the loss of quorum action to 'ignore'. ... in short, RTFM: http://www.clusterlabs.org/wiki/Documentation -- Pacemaker Configuration Explained 1.0 has *everything* you need to know in it. -K --- Karl Katzke Systems Analyst II TAMU - DRGS >>> On 5/15/2009 at 7:22 PM, in message <1242433367.21186.4.ca...@nalu.engr.sgi.com>, Bob Haxo <bh...@sgi.com> wrote: > Ok, never mind this question. "ifdown interface" works nicely to > trigger STONITH action. > > Unfortunately (if I may ask a new question) ... I now have one server > rebooting, then the other rebooting, and back to the first rebooting in > what looks to be an endless loop of reboots. > > Suggestions? > > Cheers, > Bob Haxo > SGI > > On Fri, 2009-05-15 at 16:53 -0700, Bob Haxo wrote: > > > Greetings, > > > > What manual administrative actions can be used to trigger STONITH > > action? > > > > I have created a pair of STONITH resources (external/ipmi) and would > > like to test that these resources work as expected (which, if I > > understand the default correctly, is to reboot the node). > > > > Thanks, > > Bob Haxo > > SGI > > > > SLES11 HAE > > > > _______________________________________________ > > Pacemaker mailing list > > Pacemaker@oss.clusterlabs.org > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
