HP Serviceguard for Linux Version A.11.19 Release Notes, July 2009

• Other minor new package features are listed under “Other Package Changes”
(page 31).
• Serviceguard can now monitor subnets at the IP level, as well as the link level. See
“About the IP Monitor” (page 21).
• 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 21).
• 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 21). (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 22).
• A new utility allows you to monitor applications running inside Virtual Machine
(VM) guests. See “About cmappmgr” (page 23).
• Serviceguard A.11.19 uses Persistent Reservations (PR). See “About Persistent
Reservations” (page 22)
• You can now configure a maximum of 300 packages in a cluster. The previous
limit was 150.
• There are new Serviceguard demons:
— Service Assistant Daemon: cmserviced (replaces cmsrvassistd)
— Cluster WBEM Agent Daemon: cmwbemd
— Proxy Daemon: cmproxyd
See the section “Serviceguard Daemons” in Chapter 3 of the latest edition Managing
Serviceguard for Linux for more information about these daemons.
About the New Features
New Support for IPv6
Serviceguard A.11.19 allows you to choose either the IPv4 or the IPv6 address family
for any subnet configured into the cluster, including subnets that carry the cluster
heartbeat, and those connected to a Quorum Server.
In addition, with the patches listed under “July 2009 Patches” (page 9), you can
configure an IPv6–only cluster; and the Quorum Server, if used, can also be an IPv6–only
system. The following are the possibilities for resolving the nodes' hostnames (and
Quorum Server hostnames, if any) to network address families:
• IPv4-only
• IPv6-only (requires July 2009 patch)
• Mixed
What’s in this Release 15