Hi, On Wed, Nov 07, 2012 at 06:01:51PM +0900, Josh Bowling wrote: > Nevermind, I think I got it. > Basically, I just made sure to unplug the NIC used for STONITH while > keeping the corosync NIC plugged in when I started the victim server back > up. > I then made sure that they both saw eachother correctly with `crm status` > and then plugged the STONITH NIC back in. No problem.
Normally, you shouldn't have to do this. It sounds like startup fencing, but that should happen only in case the other node is not "seen" for a while after corosync/pacemaker started. Thanks, Dejan > I've tested this method with all of my data and KVMs and it's working > without a hitch. > > Thanks again for all the help. > I'll try and return the favor down the road. > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
