Managing Serviceguard Fifteenth Edition, reprinted May 2008

Planning and Documenting an HA Cluster
Cluster Configuration Planning
Chapter 4 163
NOTE The use of a private heartbeat network is not advisable
if you plan to use Remote Procedure Call (RPC)
protocols and services. RPC assumes that each network
adapter device or I/O card is connected to a route-able
network. An isolated or private heartbeat LAN is not
route-able, and could cause an RPC request-reply,
directed to that LAN, to risk time-out without being
serviced.
NFS, NIS and NIS+, and CDE are examples of RPC
based applications that are frequently used on HP-UX.
Other third party and home-grown applications may
also use RPC services directly through the RPC API
libraries. If necessary, consult with the application
vendor to confirm its usage of RPC.
STATIONARY_IP
The IP address of each subnet that does not carry the
cluster heartbeat, but is monitored for packages.
Any subnet that is configured as a monitored_subnet
in a package configuration file (or SUBNET in a legacy
package; see “Package Configuration Planning” on
page 169) must be specified as either a STATIONARY_IP
or HEARTBEAT_IP.
If you want to separate application data from heartbeat
messages, define one or more monitored non-heartbeat
subnets here. You can identify any number of subnets
to be monitored.
IMPORTANT In a cross-subnet configuration, each package subnet
configured on an interface (NIC) must have a standby
interface connected to the local bridged network; see
“Cross-Subnet Configurations” on page 41.
A stationary IP address can be either an IPv4 or an
IPv6 address. For more details of IPv6 address format,
see “IPv6 Address Types” on page 522.