Managing Serviceguard 12th Edition, March 2006

Cluster and Package Maintenance
Reviewing Cluster and Package Status
Chapter 7314
• Unknown. A node never sees itself in this state. Other nodes assign a
node this state if it has never been an active cluster member.
Package Status and State The status of a package can be one of the
following:
• Up. The package control script is active.
• Down. The package control script is not active.
• Unknown. Serviceguard cannot determine the status at this time.
A system multi-node package is up when it is running on all the active
cluster nodes. A multi-node package is up if it is running on any of its
configured nodes.
The state of the package can be one of the following:
• Starting. The start instructions in the control script are being run.
• Running. Services are active and being monitored.
• Halting. The halt instructions in the control script are being run.
Package Switching Attributes Packages have the following
switching attributes:
• Auto Run. For failover packages, enabled means that Serviceguard
can switch the package to another node in the event of failure.
For system multi-node packages, Enabled means an instance of the
package can start on a new node joining the cluster (Disabled means
it will not).
• Switching Enabled for a Node. For failover packages, enabled means
that the package can switch to the referenced node. Disabled means
that the package cannot switch to the specified node until the node is
enabled for the package using the cmmodpkg command.
Every failover package is marked Enabled or Disabled for each node
that is either a primary or adoptive node for the package.
For multi-node packages, node switching Disabled means the
package cannot start on that node.
Service Status Services have only status, as follows:
• Up. The service is being monitored.
• Down. The service is not running. It may have halted or failed.