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

QXCR1001248606: While editing cluster configuration from Serviceguard Manager, if the
number of nodes in the Nodes tab is changed, the corresponding network information is not
updated in the summary page.
QXCR1001244974: While editing a multinode package from Serviceguard Manager, using
the Add Toolkit or Update Toolkit option, displays toolkits which are incompatible with a
multinode package.
QXCR1001250641: While configuring an Oracle ASM Toolkit package, if the Serviceguard
Manager version B.03.31 and Oracle Toolkit version A.05.01.01 are used, the configuration
apply fails for the package because the parameter Oracle Home and SID Name are mandatory
for the latest Oracle Toolkit version.
Known problems and limitations
This section provides a list of known problems and limitations as known to HP at the time of
publication. If workarounds are available, they are included.
Known problems and limitations in Serviceguard
When using Generic Resources feature, killing of cmresourced brings down the node.
No LAD support for MNP packages that are configured to use Persistent Reservation (PR).
Problem : While trying to install sgproviders in SUSE Linux Enterprise Server, it reports
insserve warning or missing messages.
Workaround: HP recommends that you ignore the warning message.
Problem: When /dev/hpdev/mylink-sde cannot be added to /dev/md0 which means
/dev/md0 is running with only one mirror half is only for Serviceguard XDC environment.
The mirror cannot be added back in the following scenarios. This log message can be seen
in SUSE Linux Enterprise Server 11 SP2 platform.
The following message is logged into the package log file:
mdadm: /dev/hpdev/mylink-sde reports being an active member for
/dev/md0, but a --re-add fails.
mdadm: not performing --add as that would convert
/dev/hpdev/mylink-sde in to a spare.
mdadm: To make this a spare, use "mdadm --zero-superblock
/dev/hpdev/mylink-sde" first.
When A package (P1) is running on a node (Node 1). The package uses a mirror (md0) that
consists of two corresponding mirror half. S1 (local to /dev/hpdev/mylink-sde) and S2
((/dev/hpdev/mylink-sdf local to Node 2). Access to S1 is lost from both nodes,
either due to power failure to S1 or loss of FC links to S1. Once you restore power to S1, or
restore the FC links to S1, the corresponding mirror half of S1(/dev/hpdev/mylink-sde)
is accessible from Node 1.
Workaround: For information about how to troubleshoot issues related to Serviceguard-xdc
package, see HP Serviceguard Extended Distance Cluster for Linux A.11.20.10 Deployment
Guide at http://www.hp.com/go/linux-serviceguard-docs.
QXCR1001243257: On Red Hat 6.3, getaddrinfo api does not return Fully Qualified
Domain Name (FQDN) of a host when the address family is mentioned as
AF_INET/AF_INET6 in the api call. The getaddrinfo api returns success but the hostname
14