- 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
Storage Volume status
The following tables define a store volumes Health, Operational and I/O states.
| Health state | Definition |
|---|---|
| OK | The storage volume is functioning normally. |
| Degraded | The storage volume may be out-of-date and/or the underlying disk is not performing optimally. |
| Unknown | Metro node cannot determine the storage volume's Health state, or the state is invalid. |
| Non-recoverable error | The storage volume may be out-of-date compared to its mirror (applies only to a storage volume that is part of a RAID-1 Metadata Volume), and/or metro node cannot determine the Health state. |
| Critical failure | Metro node has marked the storage volume as hardware-dead. |
| Isolated | The storage volume is not performing optimally, which caused metro node to prevent IO to the mirror. |
| Operational state | Definition |
|---|---|
| OK | The storage volume is functioning normally. |
| Degraded | The storage volume may be out-of-date and/or the underlying disk is not performing optimally. |
| Unknown | Metro node cannot determine the storage volume's Operational state, or the state is invalid. |
| Error | Metro node has marked the storage volume as hardware-dead. |
| Starting | The storage volume is not yet ready. |
| Lost communication | The storage volume is unreachable. |
| I/O state | Definition |
|---|---|
| Alive | I/O is proceeding normally to the storage volume. |
| Dead | Metro node has marked the storage volume as dead; I/O cannot proceed on the storage volume. This can happen when a certain number of I/Os to the storage volume fails. |
| Unreachable | Metro node has lost communication with the storage volume. |
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: <>()\