HP Serviceguard A.12.00.00 for Linux Release Notes, May 2014

Known problems and limitations in Serviceguard
QXCR1001316351: In a very rare condition cmcld will dump core during shutdown of a
node. Since package failover takes place and application does not stop there is no visible
impact to the end user.
QXCR1001335928: In a very rare condition cmcld may dump core when multiple commands
are run in parallel. Multiple Serviceguard command executing in parallel is an unlikely scenario
for a customer.
QXCR1001251484 : SLES 11 SP2: "identd Service failed to start if the IPV6 stack is disabled".
QXCR1001243955: RHEL 5.x : ssh to another node using IPv6 site-local address hangs.
QXCR1001251481: RHEL 5.x : Empty XML doc error due to rpmReadConfigFiles() failure.
Known problems and limitations in Serviceguard Manager
The known problems and limitations of Serviceguard Manager in this release are as follows:
Configuration management (Settings option in Serviceguard Manager)— While configuring
a subnet if certain nodes are not displayed under Available Subnets, then ensure that the IP
address of all the Subnets of a node that needs to be configured in Serviceguard Manager is
present in /etc/hosts file along with hostname mapping.
LDAP login: To log in to Serviceguard Manager successfully with LDAP credentials edit /etc/
pam.d/sgmgr_login file to include the following entries:
auth required pam_ldap.so
account required pam_ldap.so
Example of how /etc/pam.d/sgmgr_login file will appear after editing it:
auth sufficient pam_unix.so auth
required pam_ldap.so account
sufficient pam_unix.so account
required pam_ldap.so
QXCR1001331670—Serviceguard Manager becomes unresponsive when you perform
frequent operations on Serviceguard.
QXCR1001335508—Package overview does not show the node on which package is currently
running.
QXCR1001334964—During cluster create operation a site selection window appears while
adding nodes.
QXCR1001333902—Subent configuration shows inappropriate behavior about configured
subnet.
QXCR1001318457—Some times all packages disappears for 20 or 30 seconds.
QXCR1001332407—Node state displayed in Serviceguard Manager is inconsistent when
viewed from other nodes where Serviceguard Manager is running.
QXCR1001332414—Add Node button on create cluster page scrolls towards the right side
of the window along with added nodes.
QXCR1001336321—The detailed view for analytics shows multiple lines for maintenance in
graph.
QXCR1001336245—Serviceguard Manager becomes unresponsive if SGeSAP package
creation fails.
QXCR1001342895—Serviceguard Manager service does not start with Jetty tar ball.
Workaround
Known problems and limitations 9