HP-UX Serviceguard Heartbeat Configuration Solutions

Ensuring Heartbeat interfaces are optimally configured

Ensure that the heartbeat interface drivers are on different processors

Identify the interface(s) assigned to each of the primary and/or secondary heartbeat network

interface cards (NICs) for ServiceGuard.

1. Enter the following command on the target system running HP ServiceGuard:

/usr/sbin/cmgetconf

2. Look at the resulting output from /usr/sbin/cmgetconf. It should look something

like this:

NETWORK_INTERFACE lan9

HEARTBEAT_IP 1.1.1.1

NETWORK_INTERFACE lan15

NETWORK_INTERFACE lan5

HEARTBEAT_IP 1.1.2.1

# Possible standby Network Interfaces for lan9:lan15.

3. In the example above, the network interface is shown as lan9. This system does not

have a Link Aggregate interface. The lan9 and lan5 interfaces are being used for the

primary heartbeat, and lan15 is the standby for lan9.

Continue with the instructions in “If Your System has a Non-Link Aggregate Interface for

Serviceguard”.

4. The output from the /usr/sbin/cmgetconf command may look something like this:

NETWORK_INTERFACE lan903

HEARTBEAT_IP 1.1.1.1

NETWORK_INTERFACE lan905

NETWORK_INTERFACE lan900

HEARTBEAT_IP 1.1.1.1

In the example above, the primary network interfaces shown are lan903 and lan900

(and lan905 is the standby). If the numeric portion of the NETWORK_INTERFACE value

is 900 or above (900, 903 and 905 in this case) the system has a Link Aggregate

interface. Continue with the instructions “If Your System has a Link Aggregate Interface

for Serviceguard”.

If Your System has a Non-Link Aggregate Interface for Serviceguard