Display summary information about distributed devices.
Contexts
All contexts.
In
/distributed-storage context, command is
summary.
Syntax
ds summary
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 1. 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.
Capacity Summary
Number of devices with free capacity, amount of free capacity for the cluster, and total capacity for all clusters.
Distributed volumes (in consistency groups) unhealthy summary:
CG Name
Name of the consistency group of which the unhealthy device is a member.
Cache Mode
Cache mode of the consistency group.
Synchronous - Supported on metro node Local and metro node Metro configurations where clusters are separated by up to 5 ms of latency. In synchronous cache mode, writes to the back-end storage volumes are not acknowledged to the host until the back-end storage volumes acknowledge the write.
Number of unhealthy volumes
Number of unhealthy volumes in the consistency group.
Cluster
Visibility of the consistency group.
cluster-1 - consistency group is visible only at cluster-1.
cluster-2- consistency group is visible only at cluster-2.
cluster-1, cluster-2
- consistency group is visible at both clusters.
Operational Status
Current status for this consistency group with respect to each cluster on which it is visible.
ok - I/O can be serviced on the volumes in the consistency group.
suspended - I/O is suspended for the volumes in the consistency group. The reasons are described in the
operational status: details.
degraded - I/O is continuing, but there are other problems described in
operational status: details.
unknown - The status is unknown, likely because of lost management connectivity.
Status Details
If operational status is
ok this field is empty: “[ ]”. Otherwise, it displays additional information, which may be any of the following:
requires-resolve-conflicting-detach - After the inter-cluster link is restored, two clusters have discovered that they have detached one another and resumed I/O independently. The clusters are continuing to service I/O on their independent versions of the data. The consistency-group resolve-conflicting-detach command must be used to make the view of data consistent again at the clusters.
rebuilding-across-clusters - One or more distributed member volumes is being rebuilt. At least one volume in the group is out of date at that cluster and is re-syncing. If the link goes out at this time the entire group is suspended. Use the
rebuild status command to display which volume is out of date at which cluster.
rebuilding-within-cluster - One or more local rebuilds is in progress at this cluster.
data-safe-failure - A single director has failed. The volumes are still crash-consistent, and will remain so, unless a second failure occurs before the first is recovered.
requires-resume-after-data-loss-failure - There have been at least two concurrent failures, and data has been lost. For example, a director fails shortly after the inter-cluster link fails, or when two directors fail at almost the same time. Use the
consistency-group resume-after-data-loss-failure command to select a winning cluster and allow I/O to resume.
cluster-departure - Not all the visible clusters are in communication.
requires-resume-after-rollback - A cluster has detached its peer cluster and rolled back the view of data, but is awaiting the
consistency-group resume-after-rollback command before resuming I/O. Displayed:
At the winning side when a detach rule fires, or shortly after the
consistency-group choose-winner command picks a winning cluster.
requires-resume-at-loser - Displayed on the losing side when the inter-cluster link heals after an outage. After the inter-cluster link is restored, the losing cluster discovers that its peer was declared the winner and resumed I/O. Use the
consistency-group resume-at-loser command to make the view of data consistent with the winner, and to resume I/O at the loser.
restore-link-or-choose-winner
- I/O is suspended at all clusters because of a cluster departure, and cannot automatically resume. This can happen if:
There is no detach-rule
If the detach-rule is 'no-automatic-winner', or
If the detach-rule cannot fire because its conditions are not met.
For example, if more than one cluster is active at the time of an inter-cluster link outage, the 'active-cluster-wins' rule cannot take effect. When this detail is present, I/O will not resume until either the inter-cluster link is restored, or the user intervenes to select a winning cluster with the
consistency-group choose-winner command.
unhealthy-devices - I/O has stopped in this consistency group because one or more volumes is unhealthy and cannot perform I/O.
will-rollback-on-link-down - If there were a link-down now, the winning cluster would have to roll back the view of data in order to resume I/O.
Examples
Display summary information when no devices are unhealthy:
VPlexcli:/distributed-storage> ds summary
Slot usage summary:
Total 912 slots used by distributed device logging segments.
Distributed devices health summary:
Total 25 devices, 0 unhealthy.
Cluster summary:
Cluster cluster-2 : 25 distributed devices.
Cluster cluster-1 : 25 distributed devices.
Capacity summary:
0 devices have some free capacity.
0B free capacity of 500G total capacity.
Distributed volume summary:
Total 25 distributed devices in consistency groups, 0 unhealthy.
Total 0 distributed devices not in consistency groups, 0 unhealthy
Display summary information when one or more devices are unhealthy:
VPlexcli:/> ds summary
Slot usage summary:
Total 912 slots used by distributed device logging segments.
Distributed Volumes (not in Consistency Groups) Unhealthy Summary:
Device Name Health State Operational Status Service Status
----------- ------------- ------------------ -------------------
DR10 major-failure stressed cluster-unreachable
Distributed volumes (in consistency groups) unhealthy summary:
CG Name Cache Mode Number of Cluster Operational Status Details
---------------- ------------ Unhealthy --------- Status -------------------------------------------
---------------- ------------ Vols --------- ---------------- -------------------------------------------
---------------- ------------ ------------- --------- ---------------- -------------------------------------------
AA_ACW_Cluster12 synchronous 9 cluster-1 unknown []
cluster-2 suspended [cluster-departure,
restore-link-or-choose-winner]
AP_ACW_Cluster1 synchronous 10 cluster-1 unknown []
cluster-2 suspended [cluster-departure,
restore-link-or-choose-winner]
AP_ACW_Cluster2 synchronous 5 cluster-1 unknown []
cluster-2 suspended [cluster-departure,
restore-link-or-choose-winner]
Distributed devices health summary:
Total 25 devices, 25 unhealthy.
Cluster summary:
Cluster cluster-2 : 25 distributed devices.
Cluster cluster-1 : 25 distributed devices.
Capacity summary:
0 devices have some free capacity.
0B free capacity of 500G total capacity.
Distributed volume summary:
Total 24 distributed devices in consistency groups, 24 unhealthy.
Total 1 distributed devices not in consistency groups, 1 unhealthy.
Use the --verbose argument to display detailed information about unhealthy volumes in each consistency group:
VPlexcli:/> ds summary --verbose
Slot usage summary:
Total 912 slots used by distributed device logging segments.
Distributed Volumes (not in Consistency Groups) Unhealthy Summary:
Device Name Health State Operational Status Service Status
----------- ------------- ------------------ -------------------
DR10 major-failure stressed cluster-unreachable
Distributed volumes (in consistency groups) unhealthy summary:
CG Name Cache Mode Number of Cluster Operational Status Details
---------------- ------------ Unhealthy --------- Status -------------------------------------------
---------------- ------------ Vols --------- ---------------- -------------------------------------------
---------------- ------------ ------------- --------- ---------------- -------------------------------------------
AA_ACW_Cluster12 synchronous 9 cluster-1 unknown []
cluster-2 suspended [cluster-departure,
restore-link-or-choose-winner]
AP_ACW_Cluster1 synchronous 10 cluster-1 unknown []
cluster-2 suspended [cluster-departure,
restore-link-or-choose-winner]
AP_ACW_Cluster2 synchronous 5 cluster-1 unknown []
cluster-2 suspended [cluster-departure,
restore-link-or-choose-winner]
Distributed volumes (in consistency groups) unhealthy details:
CG Name Unhealthy Vols
---------------- -----------------------------------------------------------------------------------------------------
AA_ACW_Cluster12 ['DR11_vol', 'DR12_vol', 'DR13_vol', 'DR14_vol', 'DR15_vol', 'DR16_vol', 'DR17_vol', 'DR18_vol',
'DR19_vol']
AP_ACW_Cluster1 ['DR20_vol', 'DR21_vol', 'DR22_vol', 'DR23_vol', 'DR24_vol', 'DR25_vol', 'DR6_vol', 'DR7_vol',
'DR8_vol', 'DR9_vol']
AP_ACW_Cluster2 ['DRa_12_vol', 'DRb_12_vol', 'DRc_12_vol', 'DRd_12_vol', 'DRe_12_vol']
Distributed devices health summary:
Total 25 devices, 25 unhealthy.
Cluster summary:
Cluster cluster-2 : 25 distributed devices.
Cluster cluster-1 : 25 distributed devices.
Capacity summary:
0 devices have some free capacity.
0B free capacity of 500G total capacity.
Distributed volume summary:
Total 24 distributed devices in consistency groups, 24 unhealthy.
Total 1 distributed devices not in consistency groups, 1 unhealthy.
luster cluster-1 : 25 distributed devices.
.
See also
export port summary
export storage-view summary
extent summary
local-device summary
storage-volume summary
virtual-volume provision
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\