Managing Serviceguard Sixteenth Edition, March 2009

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 168). 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 325).
IMPORTANT: For detailed information and examples, see the cmeval (1m) manpage.
Updating the Cluster Lock Configuration
Use the procedures that follow whenever you need to change the device file names of
the cluster lock physical volumes. You may need to do this because you are changing
the device itself (the disk or LUN), or for some other reason — for example, in order
to migrate cluster nodes to the agile addressing scheme available as of HP-UX 11i v3
(see “About Device File Names (Device Special Files)” (page 107)).
Updating the Cluster Lock Disk Configuration Online
You can change the device file names (DSFs) of the cluster lock physical volumes (that
is, the values of the FIRST_CLUSTER_LOCK_PV and SECOND_CLUSTER_LOCK_PV
parameters in the cluster configuration file) without bringing down the cluster. Proceed
as follows.
Reconfiguring a Cluster 327