HP Serviceguard Version A.11.19 Release Notes, March 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.
In addition, in a site-aware disaster-tolerant cluster, you can use the SITE_PREFERRED
policy to configure packages to fail over to a node on a preferred site (for example, to
prevent a package from failing over to a node at a remote site when a local node is
eligible); and you can use cmviewcl -S to restrict output to information about the
local site. Site-aware disaster-tolerant clusters require additional software; see the
documents listed under “For More Information” (page 35), and thecmviewcl (1m)
and cmmakepkg (1m) manpages.
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. 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.
What’s in this Release 33