Help
Table Of Contents
- Dell EMC Storage Systems Online Help for the metro node appliance
- Contents
- Figures
- Welcome
- Using the GUI
- Configuring GUI default settings
- Using storage hierarchy maps
- Viewing system status
- Monitoring the system
- Performance
- 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
- Virtual Volumes dashboard
- Front End Ports dashboard
- System Health
- Performance
- Provisioning storage
- Guide
- Provisioning from storage volumes
- Provision Job properties
- Distributed storage
- Storage arrays
- Storage volumes
- Devices
- 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
- Extents
- Distributed devices
- 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
- Virtual volumes
- 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
- Consistency group
- 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
- Initiators and metro node ports
- Storage views
- 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
Write Latency Delta chart
This chart provides the delta between Front-end latency and Back-end Latency per director. This is a key metric for Local/
Metro — the amount of overhead time metro node spends processing a write.
NOTE: The chart displays data only for the directors in the cluster to which you are currently connected. To simultaneously
view Write Latency Delta for another cluster, open a second browser session and connect to the second cluster.
Guidelines (metro node Local only)
● This is typically <1 msec
● 1-10 msec is concerning
● >10 msec should be investigated.
● Large spikes indicate metro node spent a long time adding processing time to the I/O — This is generally bad for
performance.
● During disruptive events, this value may go as high as a few seconds, which could be due to I/Os timing out in the back-end.
● Note that in a heavily loaded system, this value climb as the directors become more busy, especially if the directors approach
saturation (>95% director CPU busy).
● Large block writes (host I/O block sizes >128KB) add to extra metro node write processing time.
Guidelines (metro node Metro only)
● For distributed devices in write-through mode, this statistic includes the time required to write to the remote leg of the
distributed Raid (WAN latency plus remote storage array write latency). The write is not acknowledged to the host without
first writing to both legs of the distributed Raid, thus we only perform as fast as the slowest leg which in most cases will
be the remote leg on the other cluster. This is why WAN performance is so critical. It is good to also check WAN round-trip
latency.
● During disruptive events, this value may go as high as a few seconds, which could be due to I/Os timing out in the back-end,
or a poorly performing WAN link.
Corrective actions
● Check CPU load: If CPU load is too high, this will mean less CPU cycles available to process data.
● Check back-end errors, and back-end latency: If the metro node back-end is aborting I/Os, must re-try them and this wait
time is reflected in the metro node write delta time.
● Metro node Metro: Check WAN latency. The time spent writing to the remote leg of a distributed Raid is encapsulated in this
write delta time.
Changing the view
To view the Write Latency Delta of a single director in your metro node system, select the director name from the Director
drop-down.
Viewing the Write Latency Delta chart
1. From the GUI main menu, click Performance.
2. In the Performance Dashboard, select the tab in which you want to display the Write Latency Delta chart (or create a
custom tab).
3. Click +Add Content.
4. Click the Write Latency Delta icon.
WAN Port Performance chart
The WAN Port Performance chart on the Performance Dashboard shows the WAN port performance by IP or Fibre Channel port
for the cluster to which you are connected.
44
Monitoring the system