On Tue, Jan 25, 2011 at 8:15 AM, Alain.Moulle <alain.mou...@bull.net> wrote:
> Hi
>
> A bunch of thoughts/questions about heartbeat network(s) :
>
> In the following, when I talk about "two heartbeat networks" , I'm
> talking about two physically different networks set in the corosync.conf
> as two different ring-number (with rrp_mode set to "active").
>
> 1/ with a 2-nodes HA cluster, it is recommended to have two heartbeat
> networks
>    to avoid the race for fencing, or even the dual-fencing in case of
> problem on
>    this heartbeat network.
>
>    But with a more-than-2-nodes HA cluster, is it always worthwhile to
> have two
>    heartbeat networks ? My understanding is that if one node can't have
> contact
>    from other nodes in the cluster due to a heartbeat network problem,
> as it is
>    "isolated", it does not have quorum and so is not authorized to
> fence any other node,
>    whereas other nodes have quorum and so will decide to fence the node
> with problem.
>    Right ?

Right, but wouldn't it be better to have no need to shoot anyone?

>
>    So is there any other advantage to have more than 2 heartbeats networks
>    in a more-than-2-nodes HA cluster ?
>
> 2/ if the future of the HA stack for Pacemaker is option 4 (corosync +
> cpg + cman + mcp),

Option 4 does not involve cman

> meaning
>    that cluster manager configuration parameters will all be in
> cluster.conf and nothing more in
>    corosync.conf (again that's my understanding...) ,

Other way around, cluster.conf is going away (like cman) not corosync.conf

> from memory there
> is any possibility
>    to set two heartbeat networks in cluster.conf (Cluster Suite from RH
> was working only
>    on 1 heartbeat network and if one wanted to work on 2 hearbeat
> netwoks he has to configure
>    a bonding solution).
>
>    Am I right when I write "no possibility of 2 hb networks with stack
> option 4" ?

No

>
> Thanks a lot for your responses, and tell me if some of my understanding
> is not right ...
>
> Alain
>
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to