Managing HP Serviceguard for Linux, Tenth Edition, September 2012

lower-priority-packages are currently running on node2. pkg1 is down and disabled,
and you want to see the effect of enabling it.
In the output of cmviewcl -v -f line, you would find the line
package:pkg1|autorun=disabled and change it to
package:pkg1|autorun=enabled. You should also make sure that the nodes the
package is configured to run on are shown as available; for example:
package:pkg1|node:node1|available=yes. Then save the file (for example as
newstate.in) and run cmeval:
cmeval -v newstate.in
You would see output something like this:
package:pkg3|node:node2|action:failing
package:pkg2|node:node2|action:failing
package:pkg2|node:node1|action:starting
package:pkg3|node:node1|action:starting
package:pkg1|node:node1|action:starting
This shows that pkg1, when enabled, will “drag” pkg2 and pkg3 to its primary node,
node1. It can do this because of its higher priority; see “Dragging Rules for Simple
Dependencies” (page 132). Running cmeval confirms that all three packages will
successfully start on node2 (assuming conditions do not change between now and when
you actually enable pkg1, and there are no failures in the run scripts.)
NOTE: cmeval cannot predict run and halt script failures.
This is a simple example; you can use cmeval for much more complex scenarios; see
“What You Can Preview” (page 262).
IMPORTANT: For detailed information and examples, see the cmeval (1m) manpage.
Reconfiguring a Halted Cluster
You can make a permanent change in cluster configuration when the cluster is halted.
This procedure must be used for changes marked “Cluster must not be running” in Table 9,
but it can be used for any other cluster configuration changes as well.
Use the following steps:
1. Halt the cluster on all nodes.
2. On one node, reconfigure the cluster as described in “Building an HA Cluster
Configuration” (page 156). You can use cmgetconf to generate a template file,
which you then edit.
3. Make sure that all nodes listed in the cluster configuration file are powered up and
accessible. Use cmapplyconf to copy the binary cluster configuration file to all
nodes. This file overwrites any previous version of the binary cluster configuration
file.
4. Use cmruncl to start the cluster on all nodes, or on a subset of nodes.
264 Cluster and Package Maintenance