- Notes, cautions, and warnings
- Welcome
- Using the GUI
- Configuring GUI default settings
- Using storage hierarchy maps
- Viewing system status
- Monitoring the system
- The Performance Monitoring dashboard
- Viewing a chart
- Modifying a dashboard layout
- Creating a custom dashboard
- Removing a chart
- Moving a chart
- Back-end Bandwidth Chart
- Back-end Throughput chart
- Back-end Errors chart
- Back-end Latency chart
- CPU utilization chart
- Heap Usage chart
- Front-end Queue Depth chart
- Front-end Bandwidth chart
- Front-end Latency chart
- Front-end Throughput chart
- Front-end Aborts chart
- Write Latency Delta chart
- WAN Port Performance chart
- WAN Latency chart
- Rebuild Status dashboard
- The Virtual Volumes Performance dashboard
- Virtual Volume Throughput chart
- Virtual Volume Latency chart
- Virtual Volume Bandwidth chart
- The Front End Ports dashboard
- System Health
- Provisioning storage
- Guide
- Provisioning from storage volumes
- Provision Job properties
- Distributed storage
- Supported storage arrays
- Using the Storage Arrays view
- Rediscovering a storage array
- Viewing logical units for an array
- Forgetting a storage array
- Storage array connectivity status
- About storage volumes
- The Storage Volumes view
- Claiming storage volumes
- The Claim Storage wizard
- Setting a storage volume rebuild type
- Unclaiming a storage volume
- Viewing ITLs for a storage volume
- Renaming a storage volume
- Storage Volume status
- About devices
- Using the Devices view
- The Create Devices wizard
- The Add Local/Remote Mirror wizards
- Viewing the status of IO to a device
- Creating a device
- Renaming a device
- Deleting a device
- Mirroring a device
- Device status
- Device component properties
- Device properties
- Distributed device properties
- Add capacity to virtual volumes
- Extent properties
- About extents
- Using the Extents view
- The Create Extents wizard
- Creating an extent
- Renaming an extent
- Deleting an extent
- Extent status
- About distributed devices
- The Distributed Devices view
- The Create Distributed Device from Claimed Storage Volumes wizard
- Distributed device rule sets
- Changing the rule set for a distributed device
- Creating a distributed device
- Deleting a distributed device
- Renaming a distributed device
- Distributed Device status
- About virtual volumes
- The Virtual Volumes view
- The Distributed Virtual Volumes view
- Creating a virtual volume
- About virtual volume expansion
- Expanding a virtual volume using storage volumes
- Enabling or disabling remote access for a volume
- Manually assigning LUN numbers to volumes
- Deleting a volume
- Renaming a volume
- Tearing down a volume
- Virtual Volume status
- Pool properties
- Virtual volume properties
- Show ITLs dialog box
- Logical unit properties
- ALUA Support field values
- Visibility field values
- Extent or Device mobility job properties
- Metro node port properties
- Storage array properties
- Storage view properties
- Storage volume properties
- Create Virtual Volumes dialog box
- About consistency groups
- Using the Consistency Groups view
- Distributed Consistency Groups view
- Create Consistency Group wizard
- Types of consistency groups
- Creating a consistency group
- Adding a volume to a consistency group
- Removing a volume from a consistency group
- Deleting a consistency group
- Consistency Group status
- Consistency group properties
- Step 1: Select or create a consistency group for the virtual volume
- Step 1: Create a consistency group
- Step 2: Select volume options
- Step 3: Select a storage pool
- Step 3: Select a pool for each mirror on the second cluster
- Step 3: Select a pool for each mirror in the cluster
- Step3: Create thin virtual volumes
- Select a storage view for the virtual volume(s) (optional)
- Step 5: Review your selections
- Step 6: View results
- Step 2: Select volume options
- Step 2: Select volume options
- Step 3: Select a storage volume to create the virtual volume
- Step 3: Select a source and target storage volume
- Step 3: Create thin volumes
- Step 3: Select a target storage volume on the remote cluster
- Step 3: Select target storage on the remote cluster
- Step 6: View results
- Show Logical Units
- Exporting storage
- About Initiators and metro node ports
- Using the Ports view
- Using the Initiators view
- Enabling or disabling a port
- Registering an initiator
- Rediscovering an initiator
- Manually registering an initiator
- Unregistering an initiator
- Metro node port status
- Initiator properties
- Add capacity to virtual volumes
- About storage views
- Using the Storage Views screen
- The Create Storage View wizard
- Creating a storage view
- Deleting a storage view
- Renaming a storage view
- Adding or removing initiators from a storage view
- Adding virtual volumes to a storage view
- Removing virtual volumes from a storage view
- Adding or removing metro node ports from a storage view
- Storage view status
- Storage group properties
- Director properties
- Cluster properties
- Moving data
- Mobility
- Move Data Within Cluster
- Move Data Across Clusters
- Create Mobility Job wizards
- Mobility job transfer size
- Creating a mobility job
- Viewing job details
- Committing a job
- Canceling a job
- Pausing a job
- Resuming a job
- Removing the record of a job
- Changing a job transfer size
- Searching for a job
- Mobility job status
- Notifications
Dell EMC Metro node 7.0.1 Online Help
About storage views
A storage view defines which hosts access which virtual volumes on which metro node ports. It consists of the following components:
- Registered initiators (hosts) to access the storage
- metro node ports (front-end) to export the storage
- One or more virtual volumes to export (with their respective LUN numbers)
Typically, one storage view is created for all hosts that require access to the same storage. The process of exporting storage requires the following steps:
- Create a storage view
- Add registered initiators
- Add metro node ports
- Add virtual volumes
Initiators
For an initiator (host) to see the virtual volumes in a storage view, it must be registered and included in the storage view’s registered initiator list. The initiator must also be able to communicate with the front-end ports over Fibre Channel connections—either through a direct connection or through a fabric.
Metro node ports
Typically, a storage view has one metro node port assigned to it from each director in the cluster to provide maximum redundancy. When volumes are added to a storage view, they are exported on all metro node ports in the view, using the same LUN numbers.
Virtual volumes
The virtual volumes added to a storage view can be created on devices, distributed devices, or can be a member of a consistency group. The Virtual Volumes view contains a list of all volumes in the cluster, including the volume's Service status, which indicates whether or not the virtual volume is exported to a host.
Storage view status
Until all three components (registered initiators, metro node ports, and virtual volumes) are added to a storage view, the view is Inactive. When all three components are added to a storage view, it automatically becomes active, and hosts can access the virtual volumes in the storage view.
Storage view maps
You can view a storage hierarchy map to see the components in the storage view, and drill down further to see the health and properties of all underlying storage objects. Storage view map provides more information.
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: <>()\