what is hear beat IP first

[gany59]

what is hear beat IP first of all on a cluster server?. If i have 3 lan card on my primary server lan0,1,2 and also on the adoptive server too. Now how can we configured the hear beat ip ?. Is hear beat ip is like calling the server by private IP.
I have read so many forumns, but hard luck i am unable to get the point clear.

Please any one share this.. Thanks in advance :)

[Torsten.]

This is the heartbeat - just like yours ... ;-)

Heartbeat present means alive.

Configured in the clusters ascii file.

[gany59]

ha ha ..

Torsten,

Can u pls explain me some what clearly... lol..

[melvyn burnard]

The cluster configuration gets set up using an ascii file, and in their will be the network cards/IP address pairing for each configured NIC. The IP address that is configured on a NIC using /etc/rc.config.d/netconf is referred to as a STATIONERY_IP.
To have cluster heartbeats sent and monitored on any configured NIC, change the STATIONERY statement to HEARTBEAT_IP before you apply the configuration.
The general recommendation is to have as many heartbeats as there are configured subnets in the cluster

[gany59]

sorry melvyn,

i am unable to get ur point clearly. so as per you, in the cluster configuration process, we need to remove the line called stationary ip and replace the hear beat ip right ?

[melvyn burnard]

If you read the Managing Serviceguard manual available on line, this will explain all about the HEARBEAT iP address, and how to configure it, but basically you are correct

[nijokj]

heartbeat IP is the dedicated IP which is used for cluster internal communication which is configured through the cluster configuration ascii file.

[P Arumugavel]

Hi,

Heartbeat is a dedicated communication between server nodes for clustering function. As you said, yes it is called private IP. To avoid single point of failure, it is recommended to have two confiured heartbeat Lancard. This heartbeat connection is the only that cluster manager understood that the nodes are alive.

Rgds...

[gany59]

Thanks a lot for all ur valuable response!
so the hear beat ip is used by the nodes only for signaling, to check whether they are alive or not. So we can't able to login to the server with the heat beat IP right ?. More over we got the alert like heart beat fails, is that is the case, the communication between the nodes are down but the server is up right?.


Please post the replies for this also.

[John Bigg]

The heartbeat IP is simply the IP/subnet you choose to use for heartbeat. You can have one or more heartbeat IPs. I'd recommend more than one to prevent the subnet being a single point of failure (even if you use standby lan cards).

You can have dedicated heartbeat, i.e. use this IP only for heartbeat, or you can use the IP for heartbeat, data, logins or anything you want. This is your decision.

[nijokj]

HEARTBEAT_IP

IP notation indicating a subnet that will carry the cluster heartbeat.

A heartbeat IP address must be an IPv4 address.


Heartbeat configuration requirements:

A minimum Serviceguard configuration on HP-UX 11i v2 or 11i v3 needs two network interface cards for the heartbeat in all cases, using one of the following configurations:

Two heartbeat subnets; or

One heartbeat subnet with a standby; or

One heartbeat subnet using APA with two physical ports in hot standby mode or LAN monitor mode.


Or you can configured heartbeat using cross-over cables between nodes.

One more way is through serial communication.




If heartbeat is failed between nodes ,which will cause split brain syndrome.

suppose we have communication lost between the four servers in your cluster and suppose they are able to communicate in pair of two and not all. Suppose a,b,c,d are four nodes and during the failure a can talk to b and c to d in that case both nodes will try to form two seperate cluster of two nodes each. This situation is called a split brain syndrome where more than one clusters can be created within one cluster. which will cause correction of data which will not be expected.

To avoid this situation we have quorum server, which will be contacted during the above scenarion and which two nodes contacts the quorum server first will continue to operate in cluster and other nodes will be shutdown thus avoiding split brain syndrome. This is also termed as tie breaker mechanism.

In a two node cluster, the same can be achived by a lock disk itself.

[gany59]

Hi Niko, Now i got it.

See i have 2 interface on my servere. So if i want to configured the hear beat ip and stand by interface and primary interface, what i have to do on that.

Can i able to configure those 3 with 2 lan card. Please let me know the steps


INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=10.50.50.77
SUBNET_MASK[0]=255.255.252.0
BROADCAST_ADDRESS[0]=10.151.115.255
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0
INTERFACE_MODULES[0]=""


INTERFACE_NAME[1]=lan1
IP_ADDRESS[1]=10.50.50.211
SUBNET_MASK[1]=255.255.252.0
INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]=10.50.51.255
INTERFACE_STATE[1]=up

Say with examples, or define the entry what i need to mention in the /etc/rc.config.d/netconf file.

Thanks in advance!!

[nijokj]

Suppose you have only two interface available on your system the network configuration should like one dedicated Ip you need to assign for heartbeat only. Another one will share the data and heartbeat link which will work as redundant heartbeat incase one of your heart beat will become unavailable. Please look the configuration required for this scenario.If you have one more interface that you can configure as a standby .suppose lan3 is available after cabling have been done this with the subnet of public IP, when you run cmquerycl for creating the ascii file serviceguard automatically pick that interface as standby for your public IP. no need to put the statndy lan interface information in /etc/rc.config.d/netconf file.

After all physical cabling configuration done,
Node 1

INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=10.50.50.77
SUBNET_MASK[0]=255.255.252.0
BROADCAST_ADDRESS[0]=10.151.115.255
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0
INTERFACE_MODULES[0]=""


INTERFACE_NAME[1]=lan1
IP_ADDRESS[1]=192.168.2.1
SUBNET_MASK[1]=255.255.255.0
INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]=
INTERFACE_STATE[1]=up

Interface :lan0 and lan1

Heartbeat dedicated ip lan1=192.168.2.1

Public IP lan0=10.50.50.77, in which (data and heartbeat)

NODE_NAME node1
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.50.50.77

NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.168.2.1




Node2

NODE_NAME node2
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.50.50.78

NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.168.2.2


hope this will help you

[gany59]

Hello Nijoki,

If i have 3 interfaces , i need to mention which interface and ip's are belong to hear beat and primary lan in the cluster configuration file right.. not in the /etc/rc.config.d/netconf file... Is that correct ?

[nijokj · Accepted solution]

If you have three interfaces lan0 , lan1

and lan3

Dedicated heatbeat IP lan1=192.168.2.1
public/heartbeat IP lan0=10.50.50.77

standby interface lan3= no need to put the entry in netconf.


Only physical cabling required for lan3 with the same network of lan0. when you run cmquerycl serviceguard automatically discover your statdby interface it will include in your cluster configuration. if the lan1 failed due to any reason the lan0 interface IP automatically plump to lan3.

So you need to put the following entries to netconf

INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=10.50.50.77
SUBNET_MASK[0]=255.255.252.0
BROADCAST_ADDRESS[0]=10.151.115.255
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0
INTERFACE_MODULES[0]=""


INTERFACE_NAME[1]=lan1
IP_ADDRESS[1]=192.168.2.1
SUBNET_MASK[1]=255.255.255.0
INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]=
INTERFACE_STATE[1]=up

[gany59]

Thanks a lot folks for ur valuable timings and replies. HP techies always rocks!!!!!!!!! :)