Help

Table Of Contents
Operational status Description
Starting The distributed device is not yet ready.
Service status Description
Running The distributed device is functioning normally.
Winnerrunning This cluster detached the distributed device while the other cluster was
unreachable, and is now sending I/O to the device.
Clusterunreachable Metro node cannot reach the cluster; the status is unknown.
Potentialconflict This cluster has detached the distributed device in order to resume I/O while the
other cluster was unreachable. This creates a potential conflict when the clusters
can communicate again.
Needresume 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.
Needwinner 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.
Suspended The distributed device is not accepting new I/O; pending I/O requests are frozen.
Virtual volumes
About virtual volumes
A virtual volume is created on a device or a distributed device, and is presented to a host through a storage view. Virtual
volumes are created on top-level devices only, and always use the full capacity of the device or distributed device.
Exporting volumes to hosts
A virtual volume is not visible to a host until you add it to a storage view. Exporting a virtual volume consists of the following
steps:
1. Registering an initiator
2. Creating a storage view
3. Adding initiators to the storage view
4. Adding ports to the storage view
5. Adding virtual volumes to the storage view
Volume visibility
You can enable or disable remote access for a virtual volume. Remote access allows a virtual volume in one cluster to be visible
in the other cluster. After remote access is enabled, the virtual volume will display in both clusters with global visibility. Global
visibility indicates that the virtual volume is visible in both clusters. Local visibility indicates that it is visible only at the cluster
under which you are viewing the virtual volume.
Volume names
Virtual volume names are assigned automatically based on the device name. For example, if a device is named Testdevice, by
default, the volume created on that device will be named Testdevice_vol. You can rename the virtual volume at any time in the
Virtual Volume Properties dialog box.
Provisioning storage
85