How to assign heart beat ip?

[seenivasan]

Dear ,

In cluster Heartbeat ip is same for both nodes or different?please explain

[Stephen Doud]

The heartbeat IP is the IP of a NIC designated as HEARTBEAT_IP (instead of STATIONARY_IP). If multiple active NICs (those assigned fixed IP addresses) are designated as HEARTBEAT_IP in the cluster configuration IP, then there are several heartbeat IPs on each server.

Note that if a NIC on one node is designated as a HEARTBEAT_IP, then partner nodes must also have a NIC on the same subnet that is designated as HEARTBEAT_IP.

[Steven E. Protter]

Shalom,

The answer is: It depends.

If the heartbeat is on your corporate LAN, you need to get an IP address assigned by your network team and then configure the SG package to use it.

IF you wisely build a second heartbeat network using a cross over cable or private LAN you can assign any IP you would like.

The heartbeat setup will require an IP address be assigned for each node.

SEP

[seenivasan]

Dear ,

my understanding from the following o/p:
Server 1:
Hardware: HP Integrity rx4640
OS: HP-UX B.11.31
Servername: boston.vogtnet.com
Stationary IP: 172.16.18.30 (lan0)
Heartbeat IP: 10.10.1.30 (lan1)
Standby: (lan2)
Lock Disk: VG: /dev/vglock
PV: /dev/disk/disk12

Server 2:
Hardware: HP Integrity rx4640
OS: HP-UX B.11.31
Servername: denver.vogtnet.com
Stationary IP: 172.16.18.31 (lan0)
Heartbeat IP: 10.10.1.31 (lan1)
Standby: (lan2)
Lock Disk: VG: /dev/vglock
PV: /dev/disk/disk12

heart beat ip is different for each server ok.why we no need to assign comman heart beat ip for each server?if i am assign what was the issue?

[Stephen Doud · Accepted solution]

A dedicated NIC on each server that is assigned a HEARTBEAT_IP function insures that heartbeat will be carried on a network that has a low volume of network traffic. This insures that cluster operations can continue regardless of the volume of traffic on the standard data network.

In your example, I recommend changing the term STATIONARY_IP on 172.16.18.30 and 172.16.18.31 to HEARTBEAT_IP. This causes Serviceguard to send heartbeat messages on both networks, which gives you a measure of redundancy - particularly if those NICs attach to a different network switch from the 10.10.1.x network.

All of this is covered in the "Managing Serviceguard Eighteenth Edition, September 2010"
on page 38-40 at http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02437444/c02437444.pdf

[Terry.giblin]

Dear seenivasan, 10 pts for effort.

Now please read the first response again. - 100 pts.

[Ismail Azad]

Hi,

As stephen said keeping a dedicated heartbeat LAN is a best practise as the cluster coordinator should not be fooled to think that the node is sick because of heavy congestion.

However, the heartbeat IPs on both the nodes should be on the same subnet for the transmission of heartbeat traffic which sends heartbeat messages to check if a node is healthy or not. However, keeping the Heartbeat IP as the same is going to have a duplicate IP on the network which I think is your primary question.

Regards
Ismail Azad

[seenivasan]

dear all,

my concern is single ip if enough or not?
for example i have two servers each server is having their own two nic cards.now i am going to build the new cluster time
1st server eth1 and 2nd server eth1 connected to hub.thn 1st server eth0 and 2nd server eth0 connected through cross over cable.in this case both servers eth0 ip address is same(heartbeat ip).it's correct or not?

if it's wrong please let me know.

Regards,
Seenivasan

[R.O.]

"1st server eth0 and 2nd server eth0 connected through cross over cable.in this case both servers eth0 ip address is same(heartbeat ip).it's correct or not?"

No, each lan must have different ip. I.e.

Server1 eth0: 192.168.0.1
Server2 eth0: 192.168.0.2


Regards,

[Ismail Azad]

Hi,

> seenivasan.

The scenario is right the way RO said it. I will say again you are trying to give duplicate IP addresses for the heartbeat LAN accross two nodes. The criteria is that the heartbeat IPs should be on the same SUBNET and not the SAME IP.

Regards
Ismail Azad