Howard Yuan wrote:
> Okay...I got a working heartbeat setup...but...now I'm curious and
> can't figure a way around this. Wondering if you guys have any idea.
>
> Currently, I have two SLES running DRBD and Heartbeat. Here are the
> configs:
>
> Server A LAN 1: 192.168.15.30/255.255.255.0 LAN 2:
> 10.0.0.2/255.255.255.0
>
> Server B LAN 1: 192.168.15.31/255.255.255.0 LAN 2:
> 10.0.0.4/255.255.255.0
>
> LAN 1's is connected to the main network switch. LAN 2's are
> connected to each other via a crossover cable. Heartbeat is serving
> up MySQL and a floating IP address of 10.0.0.5/255.255.255.0.
>
> The question I'm having is...if the crossover cable breaks for any
> reason...heartbeat never fails over (as the servers are technically
> still alive), but the service is no longer accessible (as they're
> trying to access it via 10.0.0.5).
>
> What is the best way to get around this problem? I want to make it
> where the service is/will still be available whenever ONE of the
> connection is broken..as the fail over doesn't occur until both
> connections die. Any ideas?
Why does the service die when the crossover breaks?
I need more configuration information to give a detailed answer.
But, the short answer is "run an R2 configuration with pingd properly
configured for your problem"
--
Alan Robertson <[EMAIL PROTECTED]>
"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
