Managing HP Serviceguard A.11.20.10 for Linux, December 2012

NOTE: But a failure in the package control script will cause the package to fail. The package
will also fail if an external script (or pre-script) cannot be executed or does not exist.
The package will not be automatically failed over, halted, or started.
A package in maintenance mode still has its configured (or default) weight, meaning that its
weight, if any, is counted against the node's capacity; this applies whether the package is
up or down. (See About Package Weights” (page 115) for a discussion of weights and
capacities.)
Node-wide and cluster-wide events affect the package as follows:
If the node the package is running on is halted or crashes, the package will no longer
be in maintenance mode but will not be automatically started.
If the cluster is halted or crashes, the package will not be in maintenance mode when the
cluster comes back up. Serviceguard will attempt to start it if auto_run is set to yes in
the package configuration file.
If node_fail_fast_enabled (page 171) is set to yes, Serviceguard will not halt the node
under any of the following conditions:
Subnet failure
Generic resource failure
A script does not exist or cannot run because of file permissions
A script times out
The limit of a restart count is exceeded
7.5.1.1 Rules for a Package in Maintenance Mode or Partial-Startup Maintenance Mode
IMPORTANT: See the latest Serviceguard release notes for important information about version
requirements for package maintenance.
The package must have package switching disabled before you can put it in maintenance
mode.
You can put a package in maintenance mode only on one node.
The node must be active in the cluster and must be eligible to run the package (on the
package's node_name list).
If the package is not running, you must specify the node name when you run cmmodpkg
(1m) to put the package in maintenance mode.
If the package is running, you can put it into maintenance only on the node on which it
is running.
While the package is in maintenance mode on a node, you can run the package only
on that node.
You cannot put a package in maintenance mode, or take it out maintenance mode, if doing
so will cause another running package to halt.
Since package failures are ignored while in maintenance mode, you can take a running
package out of maintenance mode only if the package is healthy.
Serviceguard checks the state of the package’s services and subnets to determine if the package
is healthy. If it is not, you must halt the package before taking it out of maintenance mode.
7.5 Maintaining a Package: Maintenance Mode 213