Managing Serviceguard Eighteenth Edition, September 2010

Node Status and State
The status of a node is either up (as an active 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. Active members of the cluster will see a node in this state if that node
was active in a 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. Other nodes will see a node in this state after the node has gracefully left
the active cluster, for instance as result of a cmhaltnode command.
• Unknown. 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 (page 291) provides more information.
• failing — The package is halting because it, or a package it depends on, has
failed.
• fail_wait — The package is waiting to be halted because the package or a
package it depends on has failed, but must wait for a package it depends on to
halt before it can halt.
• relocate_wait — The package’s halt script has completed or Serviceguard is
still trying to place the package.
Reviewing Cluster and Package Status 323