HP Serviceguard Version A.11.18 Release Notes, September 2008

QXCR1000820311 SGMgr does not show that MetroCluster is configured when using the Site
Aware Disaster Tolerant Architecture (SADTA)
• Problem: Serviceguard Manager Plug-in did not show that Metrocluster was
configured when Site Aware Disaster Tolerant Architecture was being used.
Serviceguard Manager also incorrectly showed that data replication was disabled
for the Site Controller package (hrdb_sc).
• Resolution: Serviceguard Manager now correctly shows that Metrocluster is
configured, and that data replication is enabled.
QXCR1000825752 SGMgr failed to display Oracle 10g databases
• Problem: When the capitalization of the hostname of the system and the hostname
configured in the Oracle Cluster Registry (OCR) did not match, Serviceguard
Manager did not display Oracle RAC 10g databases.
• Resolution: Changed code and script to fix this problem.
Known Problems and Workarounds
This section lists known problems in Serviceguard Version A.11.18 at the time of
publication. This list is subject to change without notice.
More-recent information may be available on the Hewlett-Packard IT Resource Center:
http://www.itrc.hp.com (Americas and Asia Pacific) or
http://www.europe.itrc.hp.com (Europe).
Contact your HP support representative for up-to-the-moment information.
JAGaf32484 (SR8606372066): Problems doing a rolling upgrade when moving from
CVM 3.2 to 3.5
• Problem: In a Serviceguard cluster with CVM 3.2, it is not possible to perform a
rolling upgrade from CVM 3.2 to CVM 3.5. After a node is upgraded to CVM 3.5,
when it attempts to rejoin the CVM cluster, it will fail, possibly causing a system
reset.
This problem exists regardless of whether the HP-UX operating system revision
was changed during the rolling upgrade. “Rolling upgrade” in this case means
halting one node in the cluster, upgrading CVM to 3.5 and then starting the node
back in the cluster, then performing the same steps for each node in the cluster.
The cluster is never completely halted. However, this issue does require the cluster
to be completely halted for at least some period of time, since it is not possible to
run the cluster with a mix of CVM 3.2 and 3.5.
• Workaround:
A workaround exists to do a semi-rolling upgrade to a cluster being upgraded
from CVM 3.2 to 3.5. It requires a small amount of downtime, however.
88 Serviceguard Version A.11.18 Release Notes