Using Serviceguard Extension for RAC, 5th Edition, June 2007

Maintenance and Troubleshooting
Reviewing Cluster and Package States with the cmviewcl Command
Chapter 4204
Node Status and State
The status of a node is either up (active as a member of the cluster) or
down (inactive in the cluster), depending on whether its cluster daemon
is running or not. Note that a node might be down from the cluster
perspective, but still up and running HP-UX.
A node may also be in one of the following states:
• Failed. A node never sees itself in this state. Other active members
of the cluster will see a node in this state if that node was in an
active cluster, but is no longer, and is not halted.
• 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.
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.