HP Serviceguard Version A.11.18 Release Notes, September 2008

QXCR1000766057: cmviewcl package state “blocked” is not documented
• Problem: cmviewcl shows the per-node state of multi-node packages as blocked,
but the manpage does not explain what “blocked” means.
• Resolution: “Blocked” means that the multi-node package has never run on the
node. This may be because a dependency has not been met, or auto_run is set to
no. This information has been added to the cmviewcl manpage.
Dependencies are configured in the package configuration file; see Chapter 6 of
Managing Serviceguard for more information.
QXCR1000766101: cmhaltpkg reports that auto_run is disabled for multi-node packages
but it is not
• Problem: When you used cmhaltpkg to halt packages, cmhaltpkg printed the
following message:
One or more packages or package instances have been halted.
These packages have AUTO_RUN disabled and no new instance
can start automatically. To allow automatic start, enable
AUTO_RUN via cmmodpkg -e <package_name>
This is true of the failover packages in the command list but not true of the
multi-node packages.
• Resolution: cmhaltpkg now behaves correctly.
QXCR1000768063: Serviceguard A.11.18 network validation errors missing
• Problem: When network validation failed when a cluster node was started, the
errors were not recorded.
• Resolution: Errors are now recorded properly.
QXCR1000770172: cmgetconf fails if some PV Links are missing
• Problem: If one of the PV (physical volume) links to an LVM volume group was
missing, cmgetconf (and Serviceguard Manager) failed to identify the cluster’s
volume groups.
• Resolution: The volume groups are now identified correctly.
QXCR1000836610 - cmgetconf and cmquerycl fail when VG's with names > 39 char
exist on a SG node
• Problem: Volume groups with names longer than 39 characters caused some
Serviceguard commands fail, as in the following examples:
cmgetconf
84 Serviceguard Version A.11.18 Release Notes