Managing Serviceguard 12th Edition, March 2006

Cluster and Package Maintenance
Managing Packages and Services
Chapter 7 335
Managing Packages and Services
Managing packages and services involves the following tasks:
• Starting a Package
• Halting a Package
• Moving a Package (halt, then start)
• Changing Package Switching Behavior
In Serviceguard A.11.16 and later, these commands can be done by
non-root users, according to access policies in the cluster’s configuration
files. See “Editing Security Files” on page 190, for more 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 dependencies on another package,
Serviceguard will start them in order, ensuring that a package will not
start until its dependency is met.
Using Serviceguard Manager to Start a Package
To start a failover package, right-click it to display the Admin menu. You
can let Serviceguard start the failover package on its default configured
node, or you can specify a node in the package node list.
To start a system multi-node package, right-click its cluster symbol to
display the menu. Serviceguard starts system multi-node packages on
every node active in the cluster.
From the menu, select “Run package
<pkgname> ” or “Run package
<pkgname> on node...” with a select list of running eligible nodes from
which you can choose the node on which the package should start.