Managing Serviceguard 12th Edition, March 2006

Cluster and Package Maintenance
Managing Packages and Services
Chapter 7338
Using Serviceguard Manager to Move a Failover Package
The package must be running to start the operation. It is a good idea to
check properties to be sure that the package’s dependencies can be met
on the new node.
You can select the package on the map or tree and drag it with your
mouse to another cluster node. Or, select the icon of the package you
wish to halt, and right-click to display the action list. Select “Move
package to node.” Or, select the package and go to the toolbar menu and
choose Actions -> Administering.
The Operation Log window shows messages as the action takes place.
This will include a message for halting the package and another for
starting it on the destination node.
After moving, you may want to change the switching flags. You can do
this from the Actions menu, or the right-click popup menu.
Using Serviceguard Commands to Move a Running Failover
Package
Before you move a failover package to a new node, it is a good idea to use
the cmviewcl -v -l package command and look at dependencies. If the
package has dependencies, be sure they can be met on the new node.
To move the package, you first halt it where it is running using the
cmhaltpkg command. This action not only halts the package, but also
disables switching the package back to the node on which it halts.
After it halts, you run the package on the new node using the cmrunpkg
command. Then re-enable switching. cmmodpkg can be used with the -n
option to enable a package to run on a node if the package has been
disabled from running on that node due to some sort of error. If no node
is specified, the node the command is run on is the implied node.
Example:
# cmhaltpkg pkg1
# cmrunpkg -n ftsys10 pkg1
# cmmodpkg -e pkg1