Managing Serviceguard Sixteenth Edition, March 2009

• Changing package switching behavior
• Maintaining a package using maintenance mode
Non-root users with the appropriate privileges can perform these tasks. See “Controlling
Access to the Cluster” (page 224) for information about configuring access.
You can use Serviceguard Manager or the Serviceguard command line to perform these
tasks.
Starting a Package
Ordinarily, when a cluster starts up, the packages configured as part of the cluster will
start up on their configured nodes. You may need to start a package manually after it
has been halted manually. You can do this either in Serviceguard Manager or on the
Serviceguard command line.
If any package has a configured dependency on another package, Serviceguard will
start them in order, ensuring that a package will not start until its dependency is met.
You can use Serviceguard Manager, or Serviceguard commands as shown below, to
start a package.
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 section that follows, and “About Package Dependencies”
(page 166).)
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.
Using Serviceguard Commands to Start a Package
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, to start a
failover package:
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.
316 Cluster and Package Maintenance