HP Serviceguard Version A.11.19 Release Notes, October 2009

Features Introduced in A.11.19
The features being introduced in the October 2009 patches are listed in the previous
subsection; see (page 19).
The following features were introduced in the initial release of A.11.19:
• You can configure new types of dependencies between packages. See “New Kinds
of Package Dependency” (page 25).
• You can configure package weights and node capacities, allowing you to control
broadly which packages can run simultaneously on a given node. See “Package
Weights” (page 26).
• Other minor new package features are listed under “Other Package Changes First
Introduced in Serviceguard A.11.18 Patches” (page 40).
• Serviceguard now supports the IPv6 hostname address family for all cluster
components, with some restrictions. The October 2009 patches provide further
support. See “New Support for IPv6” (page 26).
• Serviceguard can now monitor subnets at the IP level, as well as the link level. See
“The IP Monitor” (page 29).
• You can now make configuration changes while the cluster is running, particularly
in regard to the cluster lock, that were not allowed online in previous releases, or
were restricted; see “New Online Cluster Configuration Capabilities” (page 29).
• In the case of modular packages, you can now make most package configuration
changes while the package is running, and you can also make more changes to
legacy packages online. See “New Online Package Configuration Capabilities”
(page 30). (For information about modular and legacy packages, see Chapter 6 of
the latest version of Managing Serviceguard.)
• You can now preview the effects both of individual commands and of large-scale
cluster changes; see “New Preview Capabilities” (page 30).
• You can now perform maintenance on a running package. The October 2009 patches
provide further support. See “Package Maintenance Mode” (page 30).
• A new utility allows you to monitor applications running inside Virtual Machine
(VM) guests. See “cmappmgr” (page 32).
• You can now configure a maximum of 300 packages in a cluster. The previous
limit was 150.
• A quorum server can now support up to 150 clusters comprising up to 300 nodes.
The previous limits were 50 clusters and 100 nodes. The new limits are supported
in Quorum Server versions A.02.04 and later.
• There are new Serviceguard demons:
— Service Assistant Daemon: cmserviced (replaces cmsrvassistd)
— Cluster WBEM Agent Daemon: cmwbemd
— Proxy Daemon: cmproxyd
What’s in this Release 21