Managing Serviceguard Eighteenth Edition, September 2010

Identifying Heartbeat Subnets
The cluster configuration file includes entries for IP addresses on the heartbeat subnet.
HP recommends that you use a dedicated heartbeat subnet, and configure heartbeat
on other subnets as well, including the data subnet. The heartbeat can be configured
on an IPv4 or IPv6 subnet; see “About Hostname Address Families: IPv4-Only,
IPv6-Only, and Mixed Mode” (page 139).
The heartbeat can comprise multiple subnets joined by a router. In this case at least
two heartbeat paths must be configured for each cluster node. See also the discussion
of HEARTBEAT_IP under “Cluster Configuration Parameters ” (page 143), and
“Cross-Subnet Configurations” (page 41).
Specifying Maximum Number of Configured Packages
This specifies the most packages that can be configured in the cluster.
The parameter value must be equal to or greater than the number of packages currently
configured in the cluster. The count includes all types of packages: failover, multi-node,
and system multi-node.
The default is 300, which is the maximum allowable number of packages in a cluster.
NOTE: Remember to tune HP-UX kernel parameters on each node to ensure that they
are set high enough for the largest number of packages that will ever run concurrently
on that node.
Modifying the MEMBER_TIMEOUT Parameter
The cmquerycl command supplies a default value of 14 seconds for the
MEMBER_TIMEOUT parameter. Changing this value will directly affect the cluster’s
re-formation and failover times. You may need to increase the value if you are
experiencing cluster node failures as a result of heavy system load or heavy network
traffic; or you may need to decrease it if cluster re-formations are taking a long time.
You can change MEMBER_TIMEOUT while the cluster is running.
For more information, see the MEMBER_TIMEOUT parameter discussion under “Cluster
Configuration Parameters ” (page 143), “What Happens when a Node Times Out”
(page 117), and “Cluster Re-formations Caused by MEMBER_TIMEOUT Being Set too
Low” (page 415).
Controlling Access to the Cluster
Serviceguard access-control policies define cluster users’ administrative or monitoring
capabilities.
Configuring the Cluster 251