HP Serviceguard Version A.11.19 Release Notes, July 2009

• The cmviewcl command no longer supports the -r 11.09 option.
-r 11.12 and -r 11.16 are still supported. See the cmviewcl (1m) manpage
for details
• Serviceguard no longer supports versions of Veritas products from Symantec
earlier than 5.0. See “Support for Veritas 5.0 on HP-UX 11i v2 and 11i v3” (page 43).
For the most up-to-date information, check the
Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility and Feature
Matrix, at the address given under “Compatibility Information and Installation
Requirements” (page 49).
See “Announcements” (page 11) and “Rolling Upgrade Exceptions” (page 61) for more
information.
About the New Features
The subsections that follow discuss the major new capabilities introduced in the initial
A.11.19 release, as well as those that require the July 2009 patches. Information on using
these capabilities is in the latest version of Managing Serviceguard, which you can find
at the address given under “Documents for This Version ” (page 47).
New Kinds of Package Dependency
As of Serviceguard A.11.18, you can make a package dependent on any other package
or packages running on the same cluster node, subject to the restrictions spelled out in
Chapter 6 of Managing Serviceguard.
Serviceguard A.11.19 adds two new capabilities: you can specify broadly where the
package depended on must be running, and you can specify that it must be down.
For more information, see “About Package Dependencies” in Chapter 4 of the latest
version of Managing Serviceguard, and in particular the subsection “Extended
Dependencies”. See also the white paper Serviceguard’s Package Dependency Feature,
which you can find at the address given under “Documents for This Version ” (page 47).
Package Weights
Package weights and node capacities allow you to restrict the number of packages that
can run concurrently on a given node, or, alternatively, to limit the total package
“weight” (in terms of resource consumption) that a node can bear.
For example, suppose you have a two-node cluster consisting of a large system and a
smaller system. You want all your packages to be able to run on the large system at
the same time, but, if the large node fails, you want only the critical packages to run
on the smaller system. Package weights allow you to configure Serviceguard to enforce
this behavior.
For more information, see “About Package Weights” in Chapter 4 of the latest version
of Managing Serviceguard, and the white paper Using Serviceguard’s Node Capacity and
What’s in this Release 23