System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

How to get the Heartbeat information

 
SOLVED
Go to solution
Vishu
Trusted Contributor

How to get the Heartbeat information

Hi,

Can anyone please tell me how to identify the heartbeat Lan card and IP address. And also how can i get the heartbeat information between my cluster nodes.

I have the following Lan information from my cluster ASCII file.

NODE_NAME paxil
NETWORK_INTERFACE lan0
HEARTBEAT_IP 135.75.120.101
NETWORK_INTERFACE lan1
HEARTBEAT_IP 135.75.108.122
NETWORK_INTERFACE lan2
NETWORK_INTERFACE lan3


NODE_NAME prozac
NETWORK_INTERFACE lan0
HEARTBEAT_IP 135.75.120.100
NETWORK_INTERFACE lan1
HEARTBEAT_IP 135.75.108.121
NETWORK_INTERFACE lan2
NETWORK_INTERFACE lan3

Can anyone explain me these figures as i am confused as why two heartbeat IPs are given and which is my lan IP and which is Heartbeat IP.

thanks
15 REPLIES
VK2COT
Honored Contributor

Re: How to get the Heartbeat information

Hello,

a) You have a two node cluster, with two
heartbeat interfaces:

lan0
lan1

This is obviously not a full config (where
are details of your lock design)?

b) You are not using Auto Port Aggregation.

c) HEARTBEAT_IP carries the cluster
heartbeat.

You can have more than one heartbeat
interface (unless you use CVM).

STATIONARY_IP does not carry the cluster heartbeat (you do not have it defined).

d) Even if a LAN interface is configured as
a HEARTBEAT_IP, it can carry normal
application data as well (not recommended
though).

The designation STATIONARY_IP simply means
that no heartbeat packets are transmitted
over that interface; it does not mean the IP
address cannot be moved to a redundant,
standby LAN card.

The use of a redundant standby LAN interface
for all interfaces is highly recommended and
you have two of them:

lan2
lan3

Finally, if you want to test the quality of your heartbeat design, HP offers
service based on Heartbeat Exchange
Latency Measurement (HELM). It basically tests your heartbeat network.

Cheers,

VK2COT
VK2COT - Dusan Baljevic
Kranti Mahmud
Honored Contributor

Re: How to get the Heartbeat information

Hi

Heartbeat IP address for cluster only define in cmclconf.ascii file not anywhere.

IP address for packages used to failover between nodes whenver failover occurs. This is to be configured in package control script. These IP addresses are floating IP.

Check the below links:

http://docs.hp.com/en/B9903-90054/ch04s06.html

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1117571

Rgds-Kranti
Dont look BACK as U will miss something INFRONT!
Basheer_2
Trusted Contributor

Re: How to get the Heartbeat information

Vishu,

vi /etc/cmcluster/cmclconfig.ascii
will tell you your configured LANs ( heartbeat and also the LAN)

post your cmquerycl -v
Vishu
Trusted Contributor

Re: How to get the Heartbeat information

Hi,

thanks for your prompt replies. It was a valuable information for me. But will you please tell me that on the basis on above configuration, how can i know which is my network IP (through which i will telnet the server) and which is my heartbeat IP.

Also, like to know, how can i find the heartbeat communication between cluster nodes i.e. packets send/receive.

Will appreciate your responses on it.
Suraj K Sankari
Honored Contributor

Re: How to get the Heartbeat information

Hi,
open the cluster ascii file and search for heartbit or stationary, you will get the information see the below output from my cluster ascii file

NETWORK_INTERFACE lan1
HEARTBEAT_IP 172.26.5.57
NETWORK_INTERFACE lan3
STATIONARY_IP 172.26.5.58

do same thing for other node you will find the HEARTBEAT_IP and STATIONARY_IP

Suraj
Vishu
Trusted Contributor

Re: How to get the Heartbeat information

Hi Suraj,

But i have already pasted my cluster config for nodes in my first post. there is nothing as such STATIONARY_IP in it. Both are configured as HEARTBEAT_IP. Then how can i identify which is my network IP and heartbeat IP.
Torsten.
Acclaimed Contributor
Solution

Re: How to get the Heartbeat information

You should use "cmgetconf" to get the current config - consider to attach the complete output.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
joseph51
Regular Advisor

Re: How to get the Heartbeat information

Hi vishu

just try the command netstat -rn

i think i will display you data ip,HB ip & package ip information..Package ip is the virtual ip..that come along with the data ip..like 192.168.1.1:1

Suraj K Sankari
Honored Contributor

Re: How to get the Heartbeat information

Hi,
Did you search for STATIONARY_IP into your cluster ascii file?

if you didn't find the STATIONARY_IP into the cluster ascii file that means by mistake someone over right STATIONARY_IP instead of HEARTBEAT_IP and i think the second one is your STATIONARY_IP which is lan1

Suraj
Steven E. Protter
Exalted Contributor

Re: How to get the Heartbeat information

Shalom,

I see two heartbeat interfaces,

HEARTBEAT_IP 135.75.120.100
NETWORK_INTERFACE lan1
HEARTBEAT_IP 135.75.108.121

You should if possible have more than one.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Torsten.
Acclaimed Contributor

Re: How to get the Heartbeat information

As said earlier, if you find this ascii file "somewhere", it is likely not the current configuration.

You should use "cmviewconf" or "cmgetconf" instead.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vishu
Trusted Contributor

Re: How to get the Heartbeat information

Hi,

i saw the configuration from cmgetconf and this is the same i pasted above. i have also attached it for reference.

1. Can it be also, that same lan carried the heartbeat info as well as network data?

2. Is there any way we can trace the heartbeat communication (packets send/receive) between cluster nodes so that we can identify which is our heartbeat lan.
Vishu
Trusted Contributor

Re: How to get the Heartbeat information

Can anyone answer my queries. Please help in getting this info as i am totally confused in it. I have attached the cluster ascii in my previous post.
Torsten.
Acclaimed Contributor

Re: How to get the Heartbeat information

From the manual:

"When multiple heartbeats are configured, heartbeats are sent in parallel;
Serviceguard must receive at least one heartbeat to establish the health of a node. HP
recommends that you configure all subnets that connect cluster nodes as heartbeat
networks; this increases protection against multiple faults at no additional cost."

So the heartbeat goes via your lans 0 and 1.
For failed HBs I assume an entry in the logs.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Suraj K Sankari
Honored Contributor

Re: How to get the Heartbeat information

Hi,

>>I have assigned points to 29 of 85 responses to my questions

To get good response then please assign some points who give there valuable time for your problem.

To know how to assign points please go through the below link.


http://forums13.itrc.hp.com/service/forums/helptips.do?#33

Suraj