Managing HP Serviceguard for Linux, Tenth Edition, September 2012

In this example we'll assume that packages pkg1 through pkg5 are unsupported for
Live Application Detach, and pkg6 through pkgn are supported.
Proceed as follows:
1. Halt all the unsupported packages:
cmhaltpkg pkg1 pkg2 pkg3 pkg4 pkg5
2. Halt the cluster, detaching the remaining packages:
cmhaltcl -d
3. Upgrade the heartbeat networks as needed.
4. Restart the cluster, automatically re-attaching pkg6 through pkgn and starting any
other packages that have auto_run (page 206) set to yes in their package
configuration file:
cmruncl
5. Start the remaining packages; for example
cmmodpkg -e pkg1 pkg2 pkg3 pkg4 pkg5
Managing Packages and Services
This section describes the following tasks:
• Starting a Package (page 252)
• Halting a Package (page 253)
• Moving a Failover Package (page 254)
• Changing Package Switching Behavior (page 254)
Non-root users with the appropriate privileges can perform these tasks. See Controlling
Access to the Cluster (page 186) for information about configuring access.
You can use Serviceguard Manager or the Serviceguard command line to perform these
tasks.
Starting a Package
Ordinarily, a package configured as part of the cluster will start up on its primary node
when the cluster starts up. You may need to start a package manually after it has been
halted manually. You can do this either in Serviceguard Manager, or with Serviceguard
commands as described below.
The cluster must be running, and if the package is dependent on other packages, those
packages must be either already running, or started by the same command that starts
this package (see the subsection that follows, and “About Package Dependencies”
(page 130).)
You can use Serviceguard Manager to start a package, or Serviceguard commands as
shown below.
252 Cluster and Package Maintenance