HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009

the Tools tab, because there are incompatibilities between HP SMH components
and Serviceguard Manager B.01.01.
• What is the solution? Serviceguard Manager’s CGI script has been updated to be
compatible with newer versions of Linux IA64 SMH. This fix requires that the
following software is installed before installing the Serviceguard Manager patch:
jrockit-R27.4.0-jdk1.5.0_12-linux-ipf.bin; the latest version of HP
SMH (version 2.1.10-04 or later); and the latest version of HP SMH Tomcat (1.0-20
or later). JRockit can be downloaded from the BEA web site. HP SMH and HP
SMH Tomcat can be obtained from the HP Integrity Essentials Foundation Pack
for Linux Support Pack version 4.07 or later. See “Installing HP SMH and HP SMH
Tomcat” (page 60) for more information.
QXCR1000776883: Serviceguard LX allows activation of VG on multiple nodes even
with hosttags
• What was the problem? After a package halt failure it was possible to activate an
LVM2 volume group on one node when it was still activated on the node where
the package had been running, even when hosttags had been configured to
prevent this.
• What is the solution? The control script has been modified so that it does not remove
the LVM hosttag in the event of a volume group deactivation failure.
QXCR1000777286: UPCC Package applyconf will not work in a mixed patch
environment
• What was the problem? In a mixed patch environment in which at least one node
was at the 11.18.00 (Red Hat 4 or SLES 10) or 11.18.01 (Red Hat 5) patch level and
at least one other node was at 11.18.02, a cmapplyconf of a modular package
from the node at the higher patch level would fail as result of the absence of a
specific package module file on the node at the lower patch level. The module in
question contains support for VMware, but the problem occurred whether the
cluster was running VMware or not.The problem did not occur if all nodes were
at the same patch level (11.18.00, 11.18.01, or 11.18.02) and did not occur with
legacy packages.
• What is the solution? The 11.18.03 cmapplyconf code has been modified not to
fail if this module is not found on the node at the lower patch level. In this case
the package will be built without VMware support.
Fixed in This Version 81