Managing HP Serviceguard for Linux, Tenth Edition, September 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 138) 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 207) is set to yes, Serviceguard will not halt
the node under any of the following conditions:
◦ Subnet 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
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.
256 Cluster and Package Maintenance