CLI Guide

array re-discover
Re-discovers an array, and makes the array's storage volumes visible to the metro node.
Contexts
Cluster-specific context and lower.
Syntax
array re-discover
[-a|--array]context-path
[-c|--cluster] cluster-id
[-d|--hard]
[-f|--force]
Arguments
Required arguments
[-a|--array]
context-path
* Context path that specifies the storage-array to re-discover.
[-c|--cluster]
cluster-id
Cluster ID of the target cluster.
Optional arguments
[-d|--hard]
● Perform a hard rediscover. This is a disruptive operation because ITLs are destroyed and full
discoveries executed. I/O temporarily stops until the array responds with data for each LUN.
Discovery time correlates to array response time, number of provisioned volumes, and number of
paths per volume. Large numbers of volumes result in longer discovery times.
● Metro node automatically verifies the volume ID (VPD ID) on existing provisioned volumes to
detect if the array's device/LUN mapping has changed.
● *LUN swapping: Logical-unit swapping occurs when the array's back-end device/LUN mapping
has changed. This can be detected by comparing the system's saved copy of the volume's ID
(VPD_ID) with value returned by INQ VPD83 to its LUN.
● For example: A LUN is removed from a storage group on an array and then re-added. The LUN
may now be mapped to a different device which reports a different VPD_ID value. Data corruption
could occur if writes are sent to old VPD_ID value.
● If logical-unit swapping has occurred use the --hard option to force fresh discovery of all ITLs on
the array.
NOTE: using the --hard option is disruptive and can result in data unavailability and/or data loss
on live exported paths.
[-f|--force]
Force the operation without confirmation. Allows the command to be run from a non-interactive
script.
* - argument is positional.
Description
Manually synchronizes the export state of the target device. Used in two scenarios:
● When the exported LUNs from the target array to metro node are modified.
Commands
33