Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Cluster and Package Maintenance
Managing Packages and Services
Chapter 7 247
Managing Packages and Services
This section describes the following tasks:
• “Starting a Package” on page 247
• “Halting a Package” on page 248
• “Moving a Failover Package” on page 249
• “Changing Package Switching Behavior” on page 249
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” on page 115.)
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.
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.