CLI Guide

Description
Displays summarized information for all distributed-devices.
Displays more detailed information for any device with a health-state or operational-status other than ok, and a
service-status other than running.
Displays devices per cluster, and calculates total and free capacity.
Use the --verbose argument to display additional information about unhealthy volumes in each consistency group.
Table 8. ds summary field descriptions
Field Description
Distributed Volumes (not in Consistency Groups) Unhealthy Summary:
Device Name
Name of the device.
Health State
● major failure - One or more children of the
distributed device is out-of-date and will never rebuild,
possibly because they are dead or unavailable.
● minor failure - Either one or more children of the
distributed device is out-of-date and will rebuild, or the
Logging Volume for the distributed device is unhealthy.
● non-recoverable error - Metro node cannot
determine the distributed device's Health state.
● ok - The distributed device is functioning normally.
● unknown - Metro node cannot determine the device's
health state, or the state is invalid.
Operational Status
● degraded - The distributed device may have one or more
out-of-date children that will eventually rebuild.
● error - One or more components of the distributed
device is hardware-dead.
● ok - The distributed device is functioning normally.
● starting - The distributed device is not yet ready.
● stressed - One or more children of the distributed
device is out-of-date and will never rebuild.
● unknown - Metro node cannot determine the distributed
device's Operational state, or the state is invalid.
Service Status
cluster unreachable - Metro node cannot reach the
cluster; the status is unknown.
need resume - The other cluster detached the distributed
device while it was unreachable. The distributed device needs
to be manually resumed for I/O to resume at this cluster.
need winner - All clusters are reachable again, but both
clusters had detached this distributed device and resumed
I/O. You must pick a winner cluster whose data will overwrite
the other cluster's data for this distributed device.
potential conflict - The clusters have detached each
other resulting in a potential for detach conflict.
running - The distributed device is accepting I/O.
suspended - The distributed device is not accepting new
I/O; pending I/O requests are frozen.
winner-running - This cluster detached the distributed
device while the other cluster was unreachable, and is now
sending I/O to the device.
Cluster Summary
Number of distributed devices on each cluster.
Commands 163