Managing Serviceguard Eighteenth Edition, September 2010

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
timeout 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 This node's IP address on each subnet that does
not carry the cluster heartbeat, but is monitored
for packages.
NOTE: Any subnet that is configured in this
cluster configuration file as a SUBNET for IP
monitoring purposes, or as a monitored_subnet in
a package configuration file (or SUBNET in a
legacy package; see “Package Configuration
Planning ” (page 168)) must be specified in the
cluster configuration file via
NETWORK_INTERFACE and either
STATIONARY_IP or HEARTBEAT_IP. Similarly,
any subnet that is used by a package for
relocatable addresses should be configured into
the cluster via NETWORK_INTERFACE and
either STATIONARY_IP or HEARTBEAT_IP. For
more information about relocatable addresses,
see “Stationary and Relocatable IP Addresses ”
(page 90) and the descriptions of the package ip_
parameters (page 298).
If you want to separate application data from
heartbeat messages, define one or more
Cluster Configuration Planning 155