Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Managing Packages and Services
Chapter 7260
Managing Packages and Services
This section describes the following tasks:
• “Starting a Package” on page 260
• “Halting a Package” on page 261
• “Moving a Failover Package” on page 262
• “Changing Package Switching Behavior” on page 262
Non-root users with the appropriate privileges can perform these tasks.
See “Controlling Access to the Cluster” on page 180 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” on page 123.)
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.