Managing Serviceguard 13th Edition, February 2007

Cluster and Package Maintenance
Managing Packages and Services
Chapter 7 321
Changing the Switching Behavior of Failover
Packages
There are two types of switching flags:
• package switching is enabled (YES) or disabled (NO) for the package.
• node switching is enabled (YES) or disabled (NO) on individual
nodes.
For failover packages, if package switching is NO the package cannot
move to any other node. If node switching is NO, the package cannot
move to that particular node.
For multi-node packages, if package switching is NO, the package cannot
start on a new node joining the cluster. If node switching is 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. If AUTO_RUN is
set to YES, then package switching is enabled initially when the package
first starts in the cluster.
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.
Changing Package Switching with Serviceguard Commands
You can change package switching behavior either temporarily or
permanently using Serviceguard commands. To temporarily disable
switching to other nodes for a running package, use the cmmodpkg
command. For example, if pkg1 is currently running, and you want to
disable its ability to start up on another node, enter the following:
# cmmodpkg -d pkg1
This does not halt the package, but it will prevent the package from
starting up elsewhere.
You can also disable package switching to particular nodes by using the
-n option of the cmmodpkg command. The following prevents pkg1 from
switching to node lptest3: