System states in VERITAS Cluster Server 1.3.x, 2.x, and 3.x for Solaris and HP-UX
Here are the system states for VERITAS Cluster Server (VCS) 1.3.x, 2.x, and 3.x for Solaris and HP-UX. Knowing how each system state functions will help in understanding how VCS works and will help in writing triggers to customize the VCS environment. Some of these states may not exist in later releases of VCS.
UNKNOWN - The system has not joined the cluster because it does not have a system entry in the configuration.
INITING - The system has joined the cluster. This is the initial state for all systems.
CURRENT_DISCOVER_WAIT - The system has joined the cluster and its configuration file is valid. The system is waiting for information from other systems before it determines how to transition to another state.
CURRENT_PEER_WAIT - The system has a valid configuration file and another system is doing a build from disk (LOCAL_BUILD). When its peer finishes the build, this system transitions to the state REMOTE_BUILD.
STALE_PEER_WAIT - The system has a stale configuration file and another system is doing a build from disk (LOCAL_BUILD). When its peer finishes the build, this system transitions to the state REMOTE_BUILD.
STALE_DISCOVER_WAIT - The system has joined the cluster with a stale configuration file. It is waiting for information from any of its peers before determining how to transition to another state.
STALE_ADMIN_WAIT - The system has a stale configuration and there is no other system in the state of RUNNING from which to retrieve a configuration. If a system with a valid configuration is started, that system enters the LOCAL_BUILD state. Systems in STALE_ADMIN_WAIT transition to STALE_PEER_WAIT.
LOCAL_BUILD - The system is building the running configuration from the disk configuration.
REMOTE_BUILD - The system is building a running configuration that it obtained from a peer in a RUNNING state.
ADMIN_WAIT - The valid/running configuration was lost. This means the configuration file that the node uses to come up (hasys -force <node_name> or hastart -force) is not valid but it was not marked as "stale". A
hacf -verify command will usually return with errors. This situation is usually caused by someone manually editing the
main.cf and/or the types files while VCS (had) is not running which generated an errors in the configuration files. If a valid configuration is on a different node in the cluster, the command
hasys -force <node_with_valid_configuration> will bring the cluster up.
RUNNING - The system is an active member of the cluster.
LEAVING - The system is leaving the cluster gracefully. When the agents have been stopped, and when the current configuration is written to disk, the system transitions to EXITING.
EXITING - The system is leaving the cluster.
EXITED - The system has left the cluster.
FAULTED - The system has left the cluster unexpectedly.
EXITING_FORCIBLY - A
hastop -force command has forced the system to leave the cluster.
hastatus -sum and/or
hasys -state will display the node/system state. Here is a sample of the
hasys -state output:
# system Attribute Value SysA SysState RUNNING SysB SysState EXITED
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.