Managing Serviceguard Eighteenth Edition, September 2010

information about package types and modules.) These two methods are called
maintenance mode and partial-startup maintenance mode.
NOTE: If you need to do maintenance that requires halting a node, or the entire
cluster, you should consider Live Application Detach; see “Halting a Node or the
Cluster while Keeping Packages Running” (page 344).
Maintenance mode is chiefly useful for modifying networks and EMS resources
used by a package while the package is running.
See “Performing Maintenance Using Maintenance Mode” (page 356).
Partial-startup maintenance mode allows you to work on package services, file
systems, and volume groups.
See “Performing Maintenance Using Partial-Startup Maintenance Mode” (page 357).
Neither maintenance mode nor partial-startup maintenance mode can be used for
legacy packages, multi-node packages, or system multi-node packages.
Package maintenance does not alter the configuration of the package, as specified
in the package configuration file.
For information about reconfiguring a package, see “Reconfiguring a Package”
(page 385).
NOTE: In order to run a package in partial-startup maintenance mode, you must first
put it in maintenance mode. This means that packages in partial-startup maintenance
mode share the characteristics described below for packages in maintenance mode,
and the same rules and dependency rules apply. Additional rules apply to partial-startup
maintenance mode, and the procedure involves more steps, as explained
underPerforming Maintenance Using Partial-Startup Maintenance Mode.
Characteristics of a Package Running in Maintenance Mode or Partial-Startup Maintenance
Mode
Serviceguard treats a package in maintenance mode differently from other packages
in important ways. The following points apply to a package running in maintenance
mode:
Serviceguard ignores failures reported by package services, subnets, EMS resources,
and file systems; these will not cause the package to fail.
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.
354 Cluster and Package Maintenance