Managing HP Serviceguard A.11.20.10 for Linux, December 2012

Now, suppose you run the command cmhaltpkg pkgA, if a failure is detected in
non-sg-module2, then the package halt process is aborted at this point and the package is
moved to the halt_aborted state. The command exits and does not proceed further to halt the
sg-module3 and sg-module4 modules.
After fixing the error, if you re-run cmhaltpkg pkgA, halt begins from sg-module1 and proceeds.
NOTE: This error handling mechanism is applicable only for failover packages and not for
multi-node or system multi-node packages.
It is applicable only for modular packages and not for legacy packages.
If a package is in the detached or maintenance mode, the package cannot be in halt_aborted
state.
The following operations cannot be performed on a package which is in the partially_down
status:
• Reconfigure a package
• Run a package
• Halt a node (however, you can forcefully halt a node using cmhaltnode -f option.)
• Halt a cluster (however, you can forcefully halt a cluster using cmhaltcl -f option.)
• Delete a package
• Failover of a package automatically. You must halt the package completely and manually
failover the package.
7.4.3 Moving a Failover Package
You can use Serviceguard Manager to move a failover package from one node to another, or
Serviceguard commands as shown below.
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 below.
7.4.4 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 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 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 (page 170)). 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.
7.4 Managing Packages and Services 211