Administrator Guide
Table Of Contents
- Dell EMC Storage Systems Administrator Guide for PowerStore and Unity XT metro node feature
- CLI Workspace and User Accounts
- Meta Volumes
- System Management
- Thin support in metro node
- Provisioning Storage
- Volume expansion
- Data migration
- About data migrations
- Migrating thin-capable storage
- About rebuilds
- One-time data migrations
- Batch migrations
- Prerequisites
- Creating a batch migration plan
- Checking a batch migration plan
- Modifying a batch migration file
- Starting a batch migration
- Pausing/resuming a batch migration (optional)
- Canceling a batch migration (optional)
- Monitoring a batch migration’s progress
- Viewing a batch migration’s status
- Committing a batch migration
- Cleaning a batch migration
- Removing batch migration records
- Configure the WAN Network
- Consistency Groups
- Performance and Monitoring
- Metro node with active-passive storage arrays
- Index
Displaying XCOPY statistics
Metro node provides statistics that track performance and frequency of XCOPY operations. These statistics are collected at the
front-end.
See Statistics on page 95.
Setting up an XCOPY monitor
For all statistics not automatically collected as a part of perpetual monitoring, you can manually create a monitor to gather
statistics of XCOPY latency on a particular metro node virtual volume.
You create a monitor and configure a file sink so that the stats for the particular fe-lu (metro node virtual volume) will be
collected in the configured file.
The following example shows how to create a monitor to collect the fe-lu.xcopy-avg-lat statistics for a give volume
(VAAI_Vol1_Device_vol) in a file (/tmp/monitors/director-1-1-A-fe-lu-avg-lat):
VPlexcli:/monitoring/directors/director-1-1-A/monitors> monitor create --name fe-lu-
xcopy-avg-lat
--director /engines/engine-1-1/directors/director-1-1-A --stats fe-lu.xcopy-
avg-lat
--targets /clusters/cluster-1/virtual-volumes/VAAI_Vol1_Device_vol
VPlexcli:/monitoring/directors/director-1-1-A/monitors/fe-lu-ws-avg-lat> monitor add-
file-sink
/tmp/monitors/director-1-1-A-fe-lu-avg-lat
Renaming a metro node cluster
Metro node assigns names to its clusters automatically. By default, clusters are named cluster-1 and cluster-2. You can change
these names using the metro node CLI.
After you rename a metro node cluster:
● A running migration job or a scheduled job can fail. To prevent this issue, rename the cluster after the jobs are completed.
● The VPN connectivity can be lost after a system upgrade. Reconfigure VPN after the upgrade.
NOTE:
The new name for the cluster can contain up to 63 characters that include uppercase and lowercase letters,
numbers and underscores. The name must not start with a number or the prefix cluster-. Do not include spaces in the
name.
To rename a metro node cluster:
1. Log in to the metro node CLI.
2. Go to the context of the cluster.
3. Type the following command:
set name name
Where name is the new name of the cluster.
The following is an example:
vplexcli:/clusters/cluster-1>set name clusterone
vplexcli:/clusters/clusterone>
LCD Front Panel settings
CAUTION:
Do not use the panel to modify any of the settings of iDRAC or R640. Modifying the settings may
interfere with metro node settings and result in functionality failure.
22 System Management