Managing Serviceguard Sixteenth Edition, March 2009

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” (page 224) for more information about access control
policies.
Example of a Rolling Upgrade
NOTE: Warning messages may appear during a rolling upgrade while the node is
determining what version of software is running. This is a normal occurrence and not
a cause for concern.
The following example shows a simple rolling upgrade on two nodes running one
package each, as shown in Figure D-1. (This and the following figures show the starting
point of the upgrade as “SG (old)” and “HP-UX (old)”, with a roll to “SG (new)” and
“HP-UX (new)”. Substitute the actual release numbers of your rolling upgrade path.)
Figure D-1 Running Cluster Before Rolling Upgrade
Step 1.
Halt the first node, as follows
# cmhaltnode -f node1
This will cause pkg1 to be halted cleanly and moved to node 2. The Serviceguard
daemon on node 1 is halted, and the result is shown in Figure D-2.
412 Software Upgrades