Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF
Select a site to perform the rolling upgrade.
2. Select a node in a site to perform the rolling upgrade.
# cmviewcl –l node -S <site_name>
3. View all the packages running on the selected node.
# cmviewcl -l package -n <nodename>
Identify the Site Controller packages that are running on the node.
4. Move all Site Controller packages running on the selected node to a different node in the
same site using DETACH halt mode.
For more information about moving the Site Controller package, see “Moving the Site Controller
package to a node at the local site” (page 65).
5. Verify that there are no Site Controller packages running on the node.
# cmviewcl -l package -n <nodename>
6. If SGeRAC is configured, then halt the Oracle software (RAC, CRS, Clusterware, and OPS)
on the selected node.
7. Halt the node that is selected for upgrade.
# cmhaltnode -f
Instances of all MNP packages running on this node are halted and the failover packages
move to the adoptive node.
8. Add the following line in the /etc/rc.conf.d/cmcluster file:
AUTOSTART_CMCLD = 0
9. Upgrade the node to the new HP-UX release, Serviceguard, SGeRAC or Metrocluster version.
10. Set the AUTOSTART_CMCLD value in the /etc/rc.conf.d/cmcluster file to 1:
AUTOSTART_CMCLD = 1
11. If the Event Monitoring Service (EMS) is configured, then it must be restarted.
a. Stop all the EMS monitors.
b. Stop all the EMS clients.
c. End all the registrar processes.
d. Stop the p_client demon.
The p_client process is restarts immediately. The EMS registrar and the monitor
processes restart automatically when it is required.
12. Restart the cluster on the upgraded node.
13. Restart all MNP package instances that were previously running on this node.
14. If SGeRAC is configured, restart the Oracle software (RAC, CRS, Clusterware, OPS) on the
node.
15. Repeat steps 2 through 14 for every node in the site before upgrading the nodes in the other
site of the cluster.
In the event of a disaster that results in the cluster failing before the rolling upgrade is complete,
restart the cluster using the cmruncl command from a node that has been upgraded to the latest
version of the software.
Rolling upgrade 69