HP Serviceguard Version A.11.17 Release Notes, March 2006 (revised)
Serviceguard Version A.11.17 Release Notes
Known Problems and Workarounds
Chapter 154
1. Halt Serviceguard on one or more of the cluster nodes while the
other nodes remain in the cluster, still running CVM 3.2.
2. Perform the upgrade from CVM 3.2 to 3.5 on the nodes which are
not running in the Serviceguard cluster, but do not restart them
in the Serviceguard cluster when the CVM upgrade is complete.
3. Now, when you are able to take the entire cluster down, run
cmhaltcl -f on one of the nodes that is still running in the
Serviceguard cluster.
4. After the cluster has successfully halted, start the Serviceguard
cluster on the nodes that were upgraded to CVM 3.5. To do this,
you must not run the normal cmruncl command to start up the
Serviceguard cluster, since that will attempt to start all cluster
nodes. Instead, run cmviewcl -n
node1
-n
node2
-n
noden
,
where the nodes specified are the nodes that were upgraded to
CVM 3.5.
5. Now perform the CVM upgrade from 3.2 to 3.5 on the remaining
nodes in the cluster.
6. After the upgrade to CVM 3.5 has been completed on each node,
the node can rejoin the running Serviceguard cluster by running
the command, cmrunnode on that node.
For example, in a 4 node cluster, you could take down 2 nodes in the
cluster and upgrade CVM to 3.5, while the other 2 nodes continue
running the cluster with CVM 3.2. Then halt the entire cluster, and
start up the cluster on the 2 nodes that were upgraded to CVM 3.5.
Now upgrade the remaining CVM 3.2 nodes to CVM 3.5; once the
upgrade is complete, they can be added back into the cluster.
JAGad39695 (SR8606170431):User error can result in
"ghost" services:
• What is the problem? When the package was shutdown, references
for this service had already been removed, and the service failed
while the package was halting. Since the service no longer exists, it
cannot be halted manually. Any attempt to do so results in this error:
cmhaltserv : Service name oasmon is not running.
Due to the failure of the service, cmsrvassistd tries to re-start the
service since it was never halted. However, when cmsrvassistd goes
to register the re-started service, it’s status entry has been removed