Managing Serviceguard Eighteenth Edition, September 2010

(page 283) 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, bring the package out of maintenance mode:
cmmodpkg -m off pkg1
8. Restart the package:
cmrunpkg pkg1
Excluding Modules in Partial-Startup Maintenance Mode
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
apart from the module whose components you are going to work on. In this case you
can use the -e option:
cmrunpkg -e sg/service pkg1
This runs all the package's modules except the services module.
You can also use -e in combination with -m. This has the effect of starting all modules
up to and including the module identified by -m, except the module identified by -e.
In this case the excluded (-e) module must be earlier in the execution sequence (as
listed near the top of the package's configuration file) than the -m module. For example:
cmrunpkg -m sg/services -e sg/package_ip pkg1
358 Cluster and Package Maintenance