Manualshelf

Managing Serviceguard 12th Edition, March 2006

ManualsBrandsHP ManualsSoftwareHP Serviceguard Software
311312313314315316317318319320
Cluster and Package Maintenance
Reviewing Cluster and Package Status
Chapter 7 313
The cmviewcl -v command output lists dependencies throughout the
cluster. For a specific package’s dependencies, use the -p pkgname
option.
Types of Cluster and Package States
A cluster or its component nodes may be in several different states at
different points in time. The following sections describe many of the
common conditions the cluster or package may be in.
Cluster Status
The status of a cluster may be one of the following:
• Up. At least one node has a running cluster daemon, and
reconfiguration is not taking place.
• Down. No cluster daemons are running on any cluster node.
• 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.
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.