Managing Serviceguard Sixteenth Edition, March 2009

which the node identified by the preceding
NODE_NAME entry belongs. Can be used only
in a site-aware disaster-tolerant cluster, which
requires additional software; see the documents
listed under “Cross-Subnet Configurations”
(page 41) for more information.
If SITE is used, it must be used for each node in
the cluster (that is, all the nodes must be
associated with some defined site, though not
necessarily the same one).
If you are using SITEs, you can restrict the output
of cmviewcl (1m) to a given site by means of
the -S <sitename> option. In addition, you
can configure a site_preferred failover_policy
(page 266) for a package.
NETWORK_INTERFACE The name of each LAN that will be used for
heartbeats or for user data on the node identified
by the preceding NODE_NAME. An example is
lan0.
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 159)) 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 91) and the descriptions of the package ip_
parameters (page 272).
For information about changing the configuration
online, see “Changing the Cluster Networking
Configuration while the Cluster Is Running”
(page 331).
144 Planning and Documenting an HA Cluster