Re: mc/serviceguard cluster fails once
From: Alvaro Miranda (acmirand_at_puc.cl)
Date: 05/19/04
- Next message: Nissan 350Z: "Re: mc/serviceguard cluster fails once"
- Previous message: Ulrich Windl: "Re: question about ftp"
- In reply to: nissan350z: "Re: mc/serviceguard cluster fails once"
- Next in thread: Nissan 350Z: "Re: mc/serviceguard cluster fails once"
- Reply: Nissan 350Z: "Re: mc/serviceguard cluster fails once"
- Reply: Ulrich Windl: "Re: mc/serviceguard cluster fails once"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 19 May 2004 08:36:45 -0400
Hi,
Thanks for reply.
What do you recommend I need to start checking?, I want to find why when the
main switch went down, the cluster made a fail-over. The cluster is using 3
interfaces for heartbeat, I check recently and the ping went pretty well.
Thanks for any help.
Álvaro.
"nissan350z" <ota1998@hotmail.com> wrote in message
news:40ab1d08$0$8406$a0ced6e1@news.skynet.be...
> Hi,
>
> The best solution is to send heartbeat on all interface. 2 is a minimun
and
> preferably on different subnet (or vlan). Stationary (=interface not
sending
> heartbeat) is not a good idea.
> Heartbeat must be able to reach other node in any failure scenario
otherwize
> reboot will occur on isolated node (disk lock lost).
> For example, don't put all interfaces on the same switch.
>
> Alain.
>
>
- Next message: Nissan 350Z: "Re: mc/serviceguard cluster fails once"
- Previous message: Ulrich Windl: "Re: question about ftp"
- In reply to: nissan350z: "Re: mc/serviceguard cluster fails once"
- Next in thread: Nissan 350Z: "Re: mc/serviceguard cluster fails once"
- Reply: Nissan 350Z: "Re: mc/serviceguard cluster fails once"
- Reply: Ulrich Windl: "Re: mc/serviceguard cluster fails once"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|