Managing HP Serviceguard for Linux Ninth Edition, April 2009

Halting the Entire Cluster
You can use Serviceguard Manager, or Serviceguard commands as shown below, to
halt a running cluster.
The cmhaltcl command can be used to halt the entire cluster. This command causes
all nodes in a configured cluster to halt their HP Serviceguard daemons. You can use
the -f option to force the cluster to halt even when packages are running. This command
can be issued from any running node. Example:
cmhaltcl -f -v
This halts all the cluster nodes.
Automatically Restarting the Cluster
You can configure your cluster to automatically restart after an event, such as a
long-term power failure, which brought down all nodes in the cluster. This is done by
setting AUTOSTART_CMCLD to 1 in the $SGAUTOSTART file (see “Understanding the
Location of Serviceguard Files” (page 147)).
Managing Packages and Services
This section describes the following tasks:
Starting a Package (page 234)
Halting a Package (page 235)
Moving a Failover Package (page 236)
Changing Package Switching Behavior (page 236)
Non-root users with the appropriate privileges can perform these tasks. See Controlling
Access to the Cluster (page 176) 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 121).)
You can use Serviceguard Manager to start a package, or Serviceguard commands as
shown below.
234 Cluster and Package Maintenance