Redundant Heartbeat Needed??

[Darrell Tschakert]

Hi,
we have two rx4640's running HP-UX 11.23. They share a single VA7410 and run HP
Service Guard. We have a redundant main communication LAN - two NIC's. Our he
artbeat is on a private network 205.200.200.*. My supervisor has suggested that
we install another NIC in each rx4640 so that we have a redundant heartbeat. I
examined the syslog.log file showing the service Gaurd setup at boot time. Par
t of the syslog.log file follows.

Sep 16 12:57:54 host1 cmcld: Information Specific to node imsp9:
Sep 16 12:57:54 host1 cmcld: Cluster lock disk: /dev/dsk/c6t0d1.
Sep 16 12:57:54 host1 cmcld: lan0 0x0012798cbf98 201.5.64.133 bridged net:1
Sep 16 12:57:54 host1 cmcld: lan3 0x00128877ddf9 standby bridged net:1
Sep 16 12:57:54 host1 cmcld: lan2 0x001288f889e8 205.200.200.3 bridged net:2
Sep 16 12:57:54 host1 cmcld: Heartbeat Subnet: 201.5.64.0
Sep 16 12:57:54 host1 cmcld: Heartbeat Subnet: 205.200.200.0
Sep 16 12:57:54 host1 cmcld: The maximum # of concurrent local connections to th

Our main comunication lan for host1 is on 201.5.64.133 and the heartbeat is on 2
05.200.200.3. When looking at the syslog.log, it looks like we may already have
a redundant heartbeat. It looks as though the heartbeat may be able to go over
either subnet 201.5.64.0 or 205.200.200.0. I say this because I see two Heartbe
at Subnet's in the syslog.log file. Can you tell if the system, as currently c
onfigured, can send heartbeat over both of the subnets?

Thank you,

Darrell Tschakert

[melvyn burnard]

The heartbeat should be across as many LN's as possible in the configuration.
Looking at what you have supplied it appears that you already have two HEARTBEAT LAn's set up.

[Kevin Wright]

one dedicated HB, and HB over your prod network is perfect.

[Darrell Tschakert]

The consensus is that I have redundancy for my heartbeat over my primary network connection and that I do not need another heartbeat connection.

Thanks,

Darrell Tschakert