Viewing CFS Multi-Node Information

If you are running Veritas Cluster File System (CFS) cluster, you can use cfs commands to see multi-node package configuration information, status, and dependencies; for example:

cfsdgadm show_package <diskgroup>

cfsmntadm show_package <mountpoint>

getconf -p <mnpkg> grep dependency

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, as shown by cmviewcl, can 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 (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.

262 Cluster and Package Maintenance