Managing HP Serviceguard for Linux, Tenth Edition, September 2012

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.
You cannot do online configuration as described under “Reconfiguring a Package
(page 280).
You cannot configure new dependencies involving this package; that is, you cannot
make it dependent on another package, or make another package depend on it.
See also “Dependency Rules for a Package in Maintenance Mode or Partial-Startup
Maintenance Mode ” (page 257).
You cannot use the -t option of any command that operates on a package that is
in maintenance mode; see “Previewing the Effect of Cluster Changes” (page 261)
for information about the -t option.
Additional Rules for Partial-Startup Maintenance Mode
You must halt the package before taking it out of partial-startup maintenance mode.
To run a package normally after running it in partial-startup maintenance mode, you
must take it out of maintenance mode, and then restart it.
Dependency Rules for a Package in Maintenance Mode or Partial-Startup Maintenance Mode
You cannot configure new dependencies involving a package running in maintenance
mode, and in addition the following rules apply (we'll call the package in maintenance
mode pkgA).
The packages that depend on pkgA must be down and disabled when you place
pkgA in maintenance mode. This applies to all types of dependency (including
Maintaining a Package: Maintenance Mode 257