HP-UX Serviceguard Heartbeat Configuration Solutions

NOTE Be sure you have determined that your system has a NON-Link Aggregate

interface by completing the section “Ensure that the heartbeat interface drivers are on

different processors” before continuing here.

1. Determine the hardware path of the interfaces.

From the steps in the previous section, the Serviceguard information example showed

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.

a) Enter the following ioscan command to determine the hardware path number:

/usr/sbin/ioscan -kfC lan

Note: uppercase “C” in the above command

The output should look something like this:

Class I H/W Path Driver S/W State H/W Type Description

=======================================================================

lan 0 8/16/6 btlan CLAIMED INTERFACE Built-in LAN

lan 5 1/10/1 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX 4 port

lan 9 1/12/2 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX 4 port

lan 15 1/14/1 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX 4 port

b) This output shows the LAN interfaces on your system. The “I” column indicates the

instance number. In the case of a network interface of lan9 (where the value “9” is

the instance number), and the output shows a hardware path of 1/12/2 for this

interface.

c) Likewise, the above output shows that the hardware path for a network interface =

lan15 to be 1/14/1 and interface = lan5 to be 1/10/1.

2. Identify the processors.

a) Obtain the hardware path value using the ioscan procedure shown in the previous

step.

b) Enter the following interrupt migration command: /usr/contrib/bin/intctl

c) The output should look something like this: