HP Serviceguard Version A.11.19 Release Notes, July 2009

node joined the cluster, or was not run since the package was configured to run
on the node; otherwise it is yes.
• A new parameter in the package configuration file, vxvm_dg_retry, allows you
specify that a failed VxVM import should be retried; see “Package Modules and
Parameters” in Chapter 6 of Managing Serviceguard.
About Cross-Subnet Configurations
New Serviceguard capabilities, first introduced in a patch to A.11.18, allow you to
configure multiple subnets, joined by a router, both for the cluster heartbeat and for
data, with some nodes using one subnet and some another.
A cross-subnet configuration allows:
• Automatic package failover from a node on one subnet to a node on another
• A cluster heartbeat that spans subnets.
Configuration Tasks
Cluster and package configuration tasks are affected as follows:
• You must use cmquerycl -w full to discover actual or potential nodes and
subnets across routers.
• For modular packages, you must configure two new parameters in the package
configuration file to allow packages to fail over across subnets:
— ip_subnet_node - to indicate which nodes the subnet is configured on
— monitored_subnet_access - to indicate whether the subnet is configured on all
nodes (FULL) or only some (PARTIAL)
(For legacy packages, see “Configuring Cross-Subnet Failover” in Chapter 7 of
the latest edition of Managing Serviceguard, at the address given under “Documents
for This Version ” (page 47). See chapter 6 of that manual for a discussion of legacy
and modular packages.)
• You should not use the wildcard (*) for node_name in the package configuration
file, as this could allow the package to fail over across subnets when a node on the
same subnet is eligible. Instead, list the nodes in order of preference.
Restrictions
The following restrictions apply:
• All nodes in the cluster must belong to the same network domain (that is, the
domain portion of the fully-qualified domain name must be the same).
• The nodes must be fully connected at the IP level.
• A minimum of two heartbeat paths must be configured for each cluster node.
• There must be less than 200 milliseconds of latency in the heartbeat network.
Features Introduced Before A.11.19 37