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

— Utility Daemon: cmlockd
Runs on every node on which cmcld is running. It maintains the active and
pending cluster resource locks.
— Cluster SNMP Subagent (optionally running):cmsnmpd
• Hostnames for Serviceguard cluster nodes can be up to 39 characters (bytes) long.
(The former limit was 31 characters.)
• A new command, cmdisklock, can be used to repair or replace a lock LUN; see
“Replacing a Lock LUN” in Chapter 8 of Managing Serviceguard for Linux, and the
cmdisklock manpage, for more information.
• Serviceguard for Linux version A.11.18 introduced initial support for two
application interfaces based on the Service Availability Forum Specification (SAF,
saforum.org). These are for use only by ISVs (Independent Software Vendors)
with special support contracts.
Ask your HP Service Representative to contact the Serviceguard for Linux
development team for more information on these interfaces.
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 for Linux.
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 for Linux, and in particular the subsection “Extended
Dependencies”. See also the white paper Serviceguard’s Package Dependency Feature,
which you can find at docs.hp.com under High Availability —>
Serviceguard.
About 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 for Linux, and the white paper Using Serviceguard’s Node
What’s in this Release 15