Managing Serviceguard Fifteenth Edition, reprinted May 2008

Software Upgrades
Performing a Rolling Upgrade
Appendix E488
Step 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” on
page 84.
Step 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.
Step 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 the cmclnodelist file is migrated to the new Access
Control Policy form. All the hostname username pairs from the
cmclnodelist file are now triplets in the cluster configuration file, and
all have the role of Monitor. If you want to grant administration roles to
non-root users, add more entries in the configuration file.
“Controlling Access to the Cluster” on page 239 for more information
about access control policies.