Managing Serviceguard A.11.20, March 2013

• 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 294).
• 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 297) 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 with package switching disabled when
you place pkgA in maintenance mode. This applies to all types of dependency (including
exclusionary dependencies) as described under “About Package Dependencies” (page 142).
◦ You cannot enable a package that depends on pkgA.
◦ You cannot run a package that depends on pkgA, unless the dependent package itself
is in maintenance mode.
• Dependency rules governing packages that pkgA depends on to be UP are bypassed so that
these packages can halt and fail over as necessary while pkgA is in maintenance mode.
• If both packages in a dependency relationship are in maintenance mode, dependency rules
are ignored for those two packages.
For example, both packages in an exclusionary dependency can be run and halted in
maintenance mode at the same time.
Performing Maintenance Using Maintenance Mode
You can put a package in maintenance mode, perform maintenance, and take it out of maintenance
mode, whether the package is down or running.
This mode is mainly useful for making modifications to networking, generic resources, or EMS
resources. To modify other components of the package, such as services or storage, follow the
additional rules and instructions under “Performing Maintenance Using Partial-Startup Maintenance
Mode” (page 295).
If you want to reconfigure the package (using cmapplyconf (1m)) see “Reconfiguring a Package”
(page 315) and “Allowable Package States During Reconfiguration ” (page 319).
Procedure
Follow these steps to perform maintenance on a package's networking, generic resources
components, or EMS components.
In this example, we'll call the package pkg1 and assume it is running on node1.
1. Place the package in maintenance mode:
cmmodpkg -m on -n node1 pkg1
2. Perform maintenance on the networks or resources and test manually that they are working
correctly.
294 Cluster and Package Maintenance