Managing Serviceguard Seventeenth Edition, First Reprint December 2009

package, use the cmmodpkg command. For example, if pkg1 is currently running, and
you want to prevent it from starting up on another node, enter the following:
cmmodpkg -d pkg1
This does not halt the package, but will prevent it from starting up elsewhere.
You can disable package switching to particular nodes by using the -n option of the
cmmodpkg command. The following prevents pkg1 from switching to node lptest3:
cmmodpkg -d -n lptest3 pkg1
To permanently disable switching so that the next time the cluster restarts, the change
you made in package switching is still in effect, change the auto_run flag in the package
configuration file, then re-apply the configuration. (See “Reconfiguring a Package on
a Running Cluster ” (page 351).)
Maintaining a Package: Maintenance Mode
Serviceguard A.11.19 provides two ways to perform maintenance on components of a
modular, failover package while the package is running. (See Chapter 6 (page 255) for
information about package types and modules.) These two methods are called
maintenance mode and partial-startup maintenance mode.
• 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 321).
• 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 322).
• 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 350).
318 Cluster and Package Maintenance