Managing Serviceguard Sixteenth Edition, March 2009

2. Place the package in maintenance mode:
cmmodpkg -m on pkg1
3. Run the package in maintenance mode. In this example, we'll start pkg1 such that
only the modules up to and including the package_ip module are started. (See
“Package Modules and Parameters” (page 257) for a list of package modules. The
modules used by a package are started in the order shown near the top of its
package configuration file.)
cmrunpkg -m sg/package_ip pkg1
4. Perform maintenance on the services 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.
5. Halt the package:
cmhaltpkg pkg1
NOTE: You can also use cmhaltpkg -s, which stops the modules started by
cmrunpkg -m — in this case, all the modules up to and including package_ip.
6. Run the package to ensure everything is working correctly:
cmrunpkg pkg1
NOTE: The package is still in maintenance mode.
7. If everything is working as expected, halt the package and bring it out of
maintenance mode:
cmhaltpkg pkg1
cmmodpkg -m off pkg1
8. Restart the package:
cmrunpkg pkg1
NOTE: You cannot use the -t option of any command that operates on a package
that is in partial-startup maintenance mode; see “Previewing the Effect of Cluster
Changes” (page 324) for information about the -t option.
Excluding Modules
In the example above, we used cmrunpkg -m to run all the modules up to and including
package_ip, but none of those after it. But you might want to run the entire package
320 Cluster and Package Maintenance