How to get the Heartbeat information

[Steven E. Protter]

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

[Torsten.]

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

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

[Vishu]

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]

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.]

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.

[Suraj K Sankari]

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