Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Managing Packages and Services
Chapter 7344
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 run
cmviewcl -v -l package and look at dependencies. If the package has
dependencies, be sure they can be met on the new node.
To move the package, first halt it where it is running using the
cmhaltpkg command. This action not only halts the package, but also
disables package switching.
After it halts, run the package on the new node using the cmrunpkg
command, then re-enable switching as described under “Using
Serviceguard Commands to Start a Package” on page 342.
Changing Package Switching Behavior
There are two options to consider:
• Whether the package can switch (fail over) or not.
• Whether the package can switch to a particular node or not.
For failover packages, if package switching is set to NO the package
cannot move to any other node; if node switching is set to NO, the package
cannot move to that particular node.
For multi-node packages, if package switching is set to NO, the package
cannot start on a new node joining the cluster; if node switching is set to
NO, the package cannot start on that node.
Both node switching and package switching can be changed dynamically
while the cluster is running. The initial setting for package switching is
determined by the auto_run parameter, which is set in the package
configuration file (see page 283). If auto_run is set to yes, then package
switching is enabled when the package first starts. The initial setting for
node switching is to allow switching to all nodes that are configured to
run the package.
You can use Serviceguard Manager to change package switching
behavior, or Serviceguard commands as shown below.