Managing Serviceguard Sixteenth Edition, March 2009
3. Upgrade the node to the new HP-UX release, including Serviceguard.
You can perform other software or hardware upgrades if you wish (such as
installation of Veritas Volume Manager software), provided you do not detach
any SCSI cabling. See the section on hardware maintenance in the
“Troubleshooting” chapter.
For instructions on upgrading HP-UX, see the HP-UX Installation and Update
Guide for the target version of HP-UX: go to http://docs.hp.com, choose the
target version of HP-UX under Operating Environments and then choose
Installing and Updating.
To upgrade Serviceguard, use swinstall (1m) to install the new version. You
do not need to remove the old version first, and you do not need to touch /etc/
cmcluster.
4. Edit the /etc/rc.conf.d/cmcluster file to include the following line:
AUTOSTART_CMCLD = 1
5. If the Event Monitoring Service (EMS) is configured, restart it as follows:
1. Kill all EMS monitors.
2. Stop EMS clients.
3. Kill all registrar processes.
4. Kill the p_client demon.
The p_client process restart immediately. The EMS registrar and monitor
processes will be restarted automatically when they are needed.
For more information, see “Using the Event Monitoring Service ” (page 80).
6. Restart the cluster on the upgraded node. You can do this in Serviceguard Manager:
from the System Management Homepage (SMH) choose Tools ->
Serviceguard Manager, then select the node and choose Administration
-> Run Node... Or, on the Serviceguard command line, issue the cmrunnode
command.
7. Repeat this process for each node in the cluster.
If the cluster fails before the rolling upgrade is complete (because of a catastrophic
power failure, for example), you can restart the cluster by entering the cmruncl
command from a node which has been upgraded to the latest version of the software.
Keeping Kernels Consistent
If you change kernel parameters as a part of doing an upgrade, be sure to change the
parameters to the same values on all nodes that can run the same packages in case of
failover.
Migrating cmclnodelist entries from A.11.15 or earlier
Information in thecmclnodelist file is migrated to the new Access Control Policy
form. All the hostname username pairs from the cmclnodelist file are now triplets
Performing a Rolling Upgrade 411