Operational Status
|
OK
|
The cluster is functioning normally.
|
Degraded
|
The cluster is not operating as configured. This may indicate one or more of the following problems: degraded redundancy level (for example, a director is dead), suspended virtual volumes or exported volumes, storage volumes not visible from all directors, or the metadata volume is not yet processed.
|
Unknown
|
Metro node encountered a problem determining the operational status of the cluster. This may indicate a degraded state, since it usually means that at least one of the directors is not responding or is communicating abnormally.
|
Transitioning
|
The cluster is reacting to external events and may not be operating as configured. I/O may be suspended during the transition period.
|
Isolated
|
The cluster is not communicating with any other clusters.
|
Not-running
|
All directors in any one of the clusters are in Stopped state and when the VPN is stopped between clusters.
|
Transitioning Indication
|
Suspended exports
|
Cluster lost local quorum during the unvaulting state. This is possibly due to a disk not visible from all directors, no active meta-volume, delayed cluster transition, metadata, not all directors are present, or no quorum.
|
Suspended volumes
|
The distributed device is not accepting new I/O; pending I/O requests are frozen.
|
Health state
|
OK
|
The cluster is functioning normally.
|
Degraded
|
The cluster is not functioning at an optimal level. This may indicate non-functioning remote virtual volumes, unhealthy devices or storage volumes, suspended devices, conflicting director count configuration values, out-of-date devices, and so forth.
|
Unknown
|
Metro node cannot determine the cluster's health state, or the state is invalid.
|
Critical failure
|
The cluster is not functioning and may have failed completely. This may indicate a complete loss of back-end connectivity through all directors in the cluster.
|
Major failure
|
The cluster is failing and some functionality may be degraded or unavailable. This may indicate a loss of back-end connectivity through one or more (but not all) directors. When any director has issues with field replacement or if the required number of uninterrupted power supplies is not detected. If any one of the directors is waiting to gain quorum or unvaulting. Example:
Major-failure: engine-2-1 : director-2-1-A : Director has not gained quorum Major-failure: director is unvaulting
|
Minor failure
|
The cluster is functioning, but some functionality may be degraded. This may indicate one or more unreachable storage volumes.
|
LOCAL_COM
|
OK
|
All LOCAL-COM links have the expected connectivity: this port-group is operating correctly.
|
warning
|
Some links have unexpected connectivity. This port-group is operational but not properly configured. Performance may not be optimal.
|
error
|
Some connectivity is missing from this port-group. It is not operating correctly.
|
fail
|
All connectivity is missing from this port-group. LOCAL-COM is not operational.
|
WAN_COM
|
OK
|
The WAN COM switch is operating normally
|
full
|
All port-groups have a status of either ok or warning. wan-com connectivity is complete through minor configuration errors may still exist. See individual port-group statuses.
|
partial
|
Some port-groups have a status of error or fail, but at least one port-group has a status of OK or warning. wan-com is operating (possibly minimally) through at least one channel. Performance is degraded.
|
none
|
All port-groups have a status of either error or fail. wan-com is not operational.
|
not-applicable
|
The system is a single-cluster (i.e. metro node Local) system. Validating wan-com connectivity is not applicable.
|