Adding alternate heartbeat to cluster

[Sean OB_1]

Hello,

I have a 2 node cluster that I have recently added a private network to.

I have connected the two machines via a 4 port hub and given them addresses in the 192.168.0.n range (address 1 & 2).

I'm unsure of what I need to do now to set this up as an alternate heartbeat. I've attached the cluster.cfg file and have modified it with what I think is needed for the additional heartbeat. Please have a look and tell me what else if anything is needed to get this going.

TIA

Sean

[Uday_S_Ankolekar]

Hello,

Add additional Heartbeat entries in /etc/cmcluster/cmclconfig.ascii file and do recompile with cmcheckconf cmapplyconf.

Goodluck,
-USA..

[Tom Danzig · Accepted solution]

Add and entry in the cluster ascii file and apply the config via cmapplyconf -C cluster_ascii_file.

The file should look like:

NODE_NAME nodename
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.2.1.2
NETWORK_INTERFACE lan4
HEARTBEAT_IP 199.199.199.2

[keith persons]

Sean,

Your entries look correct, only thing I was wondering was why such a large value for node_timeout? is it needed that large? You're sending an hb packet every second so the 300,000,000 timeout seems excessive to me, imo.

keith

[Sean OB_1]

Keith,

The time out is that high due to application issues. With this application if there is a failover the application needs to run a file check which takes about 1 hour. So they wanted an extra long time out to make sure they didn't fail over on a transient network error, because it results on the app being down for 1 hour.

We may be able to lower the time out now that we have two heartbeats instead of just the one they had before.

Sean

[Ashwani Kashyap]

YOur entries are all correct .