HP Serviceguard A.11.20.10 for Linux Release Notes, December 2012

returned is not the FQDN of the host. Therefore the following effects are observed on
Serviceguard:
◦ The following Warning message is displayed during cmquerycl –n <node_name>
Warning: Unable to determine local domain name for <node_name>
◦ Wbemexec command fails for method getInstance on certain classes such as
HP_SGNodeIdentity and HP_SGNode.
Work around:
◦ HP recommends that you ignore the warning message. cmquerycl command does not
fail because of this warning.
◦ Only node names without domain names must be mentioned in the input XML passed to
wbemexec command as applicable.
No workaround exists for HP_SGNodeIdentity class.
• QXCR1001253592: cmpreparecl : new line missing after entry
/opt/cmcluster/doc/man
In SUSE Linux Enterprise Server 11 thecmpreparecl command updates the /etc/
manpath.config file with the location of Serviceguard manpage path. It is possible that
the man page location is entered without a new line character in the file because of which
"man" on Serviceguard commands will fail.
Workaround: Edit the file /etc/manpath.config and add a new line after the following
entry : MANDATORY_MANPATH /opt/cmcluster/doc/man
• Cluster ignore “halt aborted package” while calculating capacity.
Known problems and limitations in Serviceguard Manager
• QXCR1001229847: From Serviceguard Manager, disable sg maintenance does not have
proper checks for toolkit packages.
• QXCR1001246109: Previous button must not have any checks in the Site page.
• QXCR1001246279: Node status showing as up in the tooltip, even if the node is halted.
• QXCR1001251453: Creation of a second 3PAR package through Serviceguard Manager
shows exception intermittently.
• QXCR1001256262: DC1/DC2 Node list selection are not retained while editing 3PAR and
EVA packages.
• Rolling upgrade of Serviceguard rpms are not possible through Serviceguard Manager.
Compatibility and installation requirements
Read this entire document and any other Release Notes you may have before you begin an
installation.
NOTE: All nodes must be on the same distribution, including errata level and architecture version.
Using different distribution versions within the same cluster is supported only during rolling upgrade.
Servers using processors from Intel and AMD can be mixed in a cluster. For supported rolling
upgrade paths, see Rolling upgrade from A.11.19.X to A.11.20.00 (page 29). For information
about supported Serviceguard versions, Linux distributions, related software, and hardware, see
the documents listed under “Related information” (page 32).
Compatibility and installation requirements 15