Managing HP Serviceguard for Linux, Tenth Edition, September 2012

exclusionary dependencies) as described under “About Package Dependencies”
(page 130).
◦ 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 components. 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 259).
If you want to reconfigure the package (using cmapplyconf (1m)) see “Reconfiguring
a Package” (page 280) and “Allowable Package States During Reconfiguration ”
(page 283).
Procedure
Follow these steps to perform maintenance on a package's networking 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.
NOTE: If you now run cmviewcl, you'll see that the STATUS of pkg1 is up and
its STATE is maintenance.
3. If everything is working as expected, take the package out of maintenance mode:
cmmodpkg -m off pkg1
258 Cluster and Package Maintenance