Hi, I have a HACMP 5.2 with heartbeat over ESS disks. Documentation
states clearly that there have to be defined special HB network and
enhnaced conurent volume group:

So I have it like that:

NODE node01:
Network db_diskhb_01
node01hb /dev/vpath1

NODE node02:
Network db_diskhb_01
node02hb /dev/vpath1


Volume group is called hbvg. I am wondering how this volume group should
be varied on? As enhanced volume groups could not be varied on
automatically so should I put some special script to varyon it manually
when hacmp is started? Or this group should be defined as some speciall
resource in HACMP?

And what is the best way to check if hearbeat is running properly? Using
trace facilities in hacmp?

Thank you,

Jan

Hi Jan,
I found the following communication test for disk heartbeat networks in
the "Configuring and Verifying Communication Across a Disk Heartbeat
Network in HACMP 5.1"

Verifying communication across a disk heartbeat network

1. Run the following command on the first node to put it in Receive
Mode:
/usr/sbin/rsct/bin/dhb_read -p hdisk# -r (replace hdisk# with vpath#
if using SDD)
The following should be displayed:
Receive Mode:
Waiting for Response . . .

2. Run the following command on a different node to put it in Transmit
Mode:
/usr/sbin/rsct/bin/dhb_read -p hdisk# -t (replace hdisk# with
vpath# if using SDD)
If communication is successful, the following should be displayed:
Link operating normally.


I hope, this will help you

regards,

Swen

On Mon, 23 May 2005, Jan Pomni wrote:

> Hi, I have a HACMP 5.2 with heartbeat over ESS disks. Documentation
....
> Volume group is called hbvg. I am wondering how this volume group should
> be varied on? As enhanced volume groups could not be varied on
> automatically so should I put some special script to varyon it manually
> when hacmp is started? Or this group should be defined as some speciall
> resource in HACMP?

It works fine without the volume group varied on. It just needs to be
defined.

> And what is the best way to check if hearbeat is running properly? Using
> trace facilities in hacmp?

You could use the information from the topology services like:

% /usr/bin/lssrc -ls topsvcs
....
NIM's PID: 536702
diskhb_0 [ 2] 2 2 S 255.255.10.0 255.255.10.2
diskhb_0 [ 2] rhdisk12 0x825e289f 0x825e28cb
HB Interval = 2.000 secs. Sensitivity = 4 missed beats
Missed HBs: Total: 3 Current group: 3
Packets sent : 1812340 ICMP 0 Errors: 0 No mbuf: 0
Packets received: 1812084 ICMP 0 Dropped: 0
....

This shows a working disk heartbeat from one of our clusters.

regards,
Jesper James
jjj rotte dk