HP Serviceguard A.11.20.20 for Linux Release Notes, May 2013

• QXCR1001274453: Error messages during vgdisplay of package vg seen during cmcheckconf
• QXCR1001273835: cmcheckconf outputs error but reports no errors found
4.2 Defects fixed in Serviceguard Manager
There are no defects fixed in this version of the release.
5 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.
5.1 Known problems and limitations in Serviceguard
• Persistent Reservation (PR) module pr_cntl internally uses the dmsetup info command to
probe /dev/dm-n devices. In SUSE Linux Enterprise Server 11 SP1, the dmsetup info
command does not support probing /dev/dm-n devices. Therefore, the features that use
/dev/dm-n, such as udev alias cannot be supported with PR. If you are using udev aliases
in serviceguard-xdc environment, then PR module cannot be supported with that configuration.
NOTE: This restriction is applicable only on SUSE Linux Enterprise Server 11 SP1.
• To use multipath devices you can configure the Serviceguard packages as follows:
In the case of Serviceguard A.11.20.00, if you are using multipath devices, HP
recommends you to exclude the PR module from the package configuration file. After
◦
Serviceguard is upgraded to A.11.20.20, you must generate the package configuration
file to include in the PR module. To enable PR protection, you must restart the package
with the new configuration file.
◦ In the case of Serviceguard A.11.20.10, PR module is included in the package
configuration file, but is ignored for multipath devices. After Serviceguard is upgraded
to A.11.20.20, you must re-apply and restart the package configuration to enable PR
protection.
IMPORTANT: Ensure that all the nodes are upgraded to Serviceguard A.11.20.20 before
reapplying the package configuration
• 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
10