Managing HP Serviceguard A.11.20.10 for Linux, December 2012

• starting - The cluster is in the process of determining its active membership. At least one
cluster daemon is running.
• unknown - The node on which the cmviewcl command is issued cannot communicate with
other nodes in the cluster.
7.1.4 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 Linux.
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 the node is no longer active in the cluster, but is not shut down.
• 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.
7.1.5 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 172) 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 that depends on it to halt before it can
halt.
• relocate_wait - The package’s halt script has completed or Serviceguard is still trying to
place the package.
• reconfiguring — The node where this package is running is adjusting the package
configuration to reflect the latest changes that have been applied.
• reconfigure_wait — The node where this package is running is waiting to adjust the
package configuration to reflect the latest changes that have been applied.
194 Cluster and Package Maintenance