Managing Serviceguard 14th Edition, June 2007

Planning and Documenting an HA Cluster
Cluster Configuration Planning
Chapter 4158
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 monitored subnet that does not
carry the cluster heartbeat. You can identify any
number of subnets to be monitored. If you want to
separate application data from heartbeat messages,
define a monitored non-heartbeat subnet here.
A stationary IP address can be either an IPv4 or an
IPv6 address. For more details of IPv6 address format,
see the Appendix , “IPv6 Address Types,” on page 506.
For information about changing the configuration
online, see “Changing the Cluster Networking
Configuration while the Cluster Is Running” on
page 353.
CLUSTER_LOCK_LUN
The pathname on this node for the LUN used for the
cluster lock. Used only if a lock LUN is used for
tie-breaking services.
Enter the path name as it appears on each node in the
cluster (the same physical device may have a different
name on each node).