HP Serviceguard A.11.20.20 for Linux Release Notes, March 2014

• When nodes are in mixed patch version, WWID for lock LUN device on Node running
Serviceguard version A.11.20.00 might mismatch with WWID of lock LUN device on Node-2
running Serviceguard version A.11.20.10 or later even when the device is same. This is due
to the way the WWID is read by Serviceguard. Due to this it leads to the failure of cmcheckconf
and cmapplyconf of cluster configured with lock LUN as arbitration mechanism in the mixed
patch environment. Therefore, use cmcheckconf or cmapplyconf command only after
upgrading all the cluster nodes to Serviceguard version A.11.20.20.
NOTE: This issue is seen only on Red Hat Enterprise Linux.
• QXCR1001282336: Storage probing doesn't happen if all paths of a PV are down on all
nodes
• QXCR1001282339: cmcheckconf reports error for all n/w interfaces if only one interface is
down
• QXCR1001280737: If a pkg contains vg & pv inconsistencies both, pv errors are not reported
• QXCR1001280933: cmcheckconf not detecting PV unavailability while cluster and PKG creation
• When using Generic Resources feature with Serviceguard A.11.20.10 or earlier versions,
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 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
returned is not the FQDN of the host. Therefore the following effects are observed on
Serviceguard:
5 Known problems and limitations 11