Managing HP Serviceguard A.11.20.20 for Linux, May 2013

NOTE: If you do not do this, the cmhaltcl in the next step will fail.
3. Halt the cluster with the -d (detach) option:
cmhaltcl -d
NOTE: -d and -f are mutually exclusive. See cmhaltcl (1m) for more information.
To re-attach the packages, restart cluster:
cmrunnode node1
7.3.7 Example: Halting the Cluster for Maintenance on the Heartbeat Subnets
Suppose that you need to do networking maintenance that will disrupt all the cluster's heartbeat
subnets, but it is essential that the packages continue to run while you do it. 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 176) 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 217)
• Halting a Package (page 218)
• Moving a Failover Package (page 219)
• Changing Package Switching Behavior (page 220)
Non-root users with the appropriate privileges can perform these tasks. See Controlling Access to
the Cluster (page 158) 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 112).)
7.4 Managing Packages and Services 217