CLI Guide

[-f|--force]
Arguments
Optional arguments
[-c|--cluster] context
path
Resume I/O on the specified cluster and the clusters it is in communication with during a link
outage.
Applicable only when the all-at-island argument is used or when the specified devices are
distributed devices.
Not required for local devices with global visibility.
[-r|--devices] context
path or device-name
Name or context path of the devices for which to resume I/O. They must be top-level devices.
[-a|--all-at-island]
Resume I/O on all devices on the chosen winning cluster and the clusters with which it is
communicating.
[-f|--force]
Force the I/O to resume.
Description
Used when the inter-cluster link fails. Allows one or more suspended mirror legs to resume I/O immediately.
For example, used when the peer cluster is the winning cluster but is known to have failed completely.
Resumes I/O on the specified cluster and the clusters it is in communication with during a link outage.
Detaches distributed devices from those clusters that are not in contact with the specified cluster or detaches local devices
from those clusters that are not in contact with the local cluster.
WARNING:
The device resume-link-down command causes I/O to resume on the local cluster regardless
of any rule-sets applied to the device. Verify that rules and any manual detaches do not result in conflicting
detaches (cluster-1 detaching cluster-2, and cluster-2 detaching cluster-1). Conflicting detaches will result in
lost data on the losing cluster, a full rebuild, and degraded access during the time of the full rebuild.
When the inter-cluster link fails in a metro node Metro configuration, distributed devices are suspended at one or more clusters.
When the rule-set timer expires, the affected cluster is detached.
Alternatively, use the device resume-link-down command to detach the cluster immediately without waiting for the
rule-set timer to expire.
WARNING:
Verify that rules and any manual detaches do not result in conflicting detaches (cluster-1 detaching
cluster-2, and cluster-2 detaching cluster-1).
Conflicting detaches result in lost data on the losing cluster, a full rebuild, and degraded access during the time
of the full rebuild.
Only one cluster should be allowed to continue for each distributed device. Different distributed devices can have different
clusters continue.
Use the ll /distributed-storage/distributed-devices/device command to display the rule set applied to the
specified device.
Use the ll /distributed-storage/rule-sets/rule-set/rules command to display the detach timer for the specified
rule-set.
Examples
VPlexcli:/distributed-storage/distributed-devices> device resume-link-down --all-at-
island --cluster --devices DD_5d --force
124
Commands