I'm somehow misplaced here. Lars, you're saying that both of the configurations aren't correct? In what way can I resolve this misconfiguration without reinventing the wheel?
On Mon, Oct 13, 2008 at 11:00 AM, Lars Marowsky-Bree <[EMAIL PROTECTED]> wrote: > On 2008-10-13T00:36:38, Brian Klauss <[EMAIL PROTECTED]> wrote: > > > When I disconnect the heartbeat from one of the servers, whether through > the > > shutdown of the NIC or by physically removing the cable, the other node > > senses this as a failure and immediately takes over both floating IP > > addresses. Strangely the node where the heartbeat was removed from also > > acquires both floating IP addresses and therefore causes much grief on > the > > network. I'm at a loss here and this is causing me a lot of headache. > Any > > ideas? > > > > Here is node 1's ha.cf: > > > > #debugfile /var/log/ha-debug > > ucast eth2 10.0.0.2 > > > > Here is node 2's ha.cf: > > > > ucast eth2 10.0.0.1 > > Unsupported twice; no redundant communication links, no STONITH. The > first would immensely decrease the probability of a split-brain > scenario, the second would prevent it. > > > Regards, > Lars > > -- > Teamlead Kernel, SuSE Labs, Research and Development > SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > _______________________________________________ > 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
