Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Reviewing Cluster and Package Status
Chapter 7320
• 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 master control script is active.
• down - The package master control script is not active.
• start_wait - A cmrunpkg command is in progress for this package.
The package is waiting for packages it depends on (predecessors) to
start before it can start.
• starting - The package is starting. The package master control
script is running.
• halting - A cmhaltpkg command is in progress for this package and
the halt script is running.
• halt_wait - A cmhaltpkg command is in progress for this package.
The package is waiting to be halted, but the halt script cannot start
because the package is waiting for packages that depend on it
(successors) to halt. The parameter description for
successor_halt_timeout (see page 284) provides more
information.
• failing - The package is halting because it, or a package it depends
on, has failed.