a shared HeartBeat network ?

[Francois LAURENT]

Hi all,

Is there any problem to have 2 DIFFERENTS CLUSTER heart beat on the same network ?

Heart beat runs on broadcast mode, isn't it ? So how the 2 different clusters could dissociate his own heart beat if the 2 heart beat are on the same network ?

At this time, this network is a heart beat dedicated network for one cluster, the network team want to use it for the heart beat of an other cluster too.

Hope that question is not so stupid ...

Francois

[harry d brown jr]

I'm not sure what kind of cluster you have, or if it is a problem, but if it is, then have them just create two vlans (virtual lans).

live free or die
harry

[Stefan Farrelly]

The hearbeat for an SG cluster is simply an IP address - normally its on a separate network and uses something like a 192.x.y.z range. We have a separate network for our SG heartbeats and we run multiple SG clusters on it - each SG cluster has a different hearbeat IP address so there is no possible conflict. Works fine.

[Sanjay_6 · Accepted solution]

Hi,

There is no problem is you have multiple cluster heartbeats on the same network / subnet.

The heartbeats are identified using their cluster name and node name. So you can have multiple cluster heartbeats on the same subnet.

Hope this helps.

Regds

[Jeff Schussele]

Hi Francois,

1) No - no problem at all. We do it all the time & have had a dozen or more clusters on the same subnet.

2) No - heartheats use DLPI packets from MAC to MAC. They do not broadcast. They transmit on layer 2 - the Link layer.

3) As stated in #1 - this is perfectly acceptable.

HTH,
Jeff

[Francois LAURENT]

Thank all for the reactivity and the precision of answers ...
;-)

[Steven E. Protter]

I would pay attention to the timeout in the cluster configuration for the heartbeat.

While a shared heartbeat lan is no problem, if the lan becomes congested for a long enough period of time, the race to the lock disk or quorum server starts and nodes may start to TOC.

Thats why a lot of people have their own little private lans for the heartbeat. Then you just have to make sure nobody unplugs the hub or switch.

Having a second heartbeat on a second NIC can mitigate the effects of congestion on your cluster.

SEP