Managing Serviceguard 13th Edition, February 2007

Cluster and Package Maintenance
Reviewing Cluster and Package Status
Chapter 7298
• Reforming. A node is in this state when the cluster is re-forming.
The node is currently running the protocols which ensure that all
nodes agree to the new membership of an active cluster. If agreement
is reached, the status database is updated to reflect the new cluster
membership.
• Running. A node in this state has completed all required activity for
the last re-formation and is operating normally.
• Halted. A node never sees itself in this state. Other nodes will see it
in this state after the node has gracefully left the active cluster, for
instance with a cmhaltnode command.
• 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).