Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Planning and Documenting an HA Cluster
Cluster Configuration Planning
Chapter 4 115
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 time-out without being
serviced.
NFS, NIS and NIS+, and CDE are examples of RPC
based applications that are frequently used. Other
third party and home-grown applications may also use
RPC services through the RPC API libraries. If
necessary, consult with the application vendor.
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 119) 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.
A stationary IP address can be either an IPv4 or an
IPv6 address. For more information about IPv6
addresses, see Appendix E, “IPv6 Network Support,” on
page 373.
For information about changing the configuration
online, see “Changing the Cluster Networking
Configuration while the Cluster Is Running” on
page 269.