Managing HP Serviceguard A.11.20.10 for Linux, December 2012

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 170) set to yes in their package configuration file:
cmruncl
5. Start the remaining packages; for example:
cmmodpkg -e pkg1 pkg2 pkg3 pkg4 pkg5
7.4 Managing Packages and Services
This section describes the following tasks:
• Starting a Package (page 209)
• Halting a Package (page 209)
• Moving a Failover Package (page 211)
• Changing Package Switching Behavior (page 211)
Non-root users with the appropriate privileges can perform these tasks. See Controlling Access to
the Cluster (page 152) for information about configuring access.
You can use Serviceguard Manager or the Serviceguard command line to perform these tasks.
7.4.1 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 107).)
You can use Serviceguard Manager to start a package, or Serviceguard commands as shown
below.
Use the cmrunpkg command to run the package on a particular node, then use the cmmodpkg
command to enable switching for the package; for example:
cmrunpkg -n ftsys9 pkg1
cmmodpkg -e pkg1
This starts up the package on ftsys9, then enables package switching. This sequence is necessary
when a package has previously been halted on some node, since halting the package disables
switching.
7.4.1.1 Starting a Package that Has Dependencies
Before starting a package, it is a good idea to use the cmviewcl command to check for package
dependencies.
You cannot start a package unless all the packages that it depends on are running. If you try, you’ll
see a Serviceguard message telling you why the operation failed, and the package will not start.
If this happens, you can repeat the run command, this time including the package(s) this package
depends on; Serviceguard will start all the packages in the correct order.
7.4.2 Halting a Package
You halt a package when you want to stop the package but leave the node running.
7.4 Managing Packages and Services 209