Administrator Guide
Table Of Contents
- Dell EMC Storage Systems Administrator Guide for the metro node appliance
- Contents
- Preface
- 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
- Cluster Witness
- Consistency Groups
- Performance and Monitoring
- Metro node with active-passive storage arrays
NOTE: In Unisphere for metro node, performance statistics are displayed per cluster. To view statistics for both clusters in
a Metro configuration, connect to both clusters.
Custom monitors
You can use the CLI to create custom monitors to collect and display selected statistics for selected targets.
See Monitor performance using the CLI.
Perpetual monitors
GeoSynchrony includes perpetual monitors that gather a standard set of performance statistics every 30 seconds. Perpetual
monitors collect the statistics related to the performance of metro node directors and virtual volumes.
Perpetual monitor files are collected as part of collect-diagnostics. Collect-diagnostics is per cluster, so in Metro
configurations, run the command from one node on each metro node cluster.
Output of perpetual monitors is captured in the file smsDump_date.zip inside the base collect-diagnostics zip file.
Within smsDump_date.zip file, monitor files are in clilogs/.
You can also copy the perpetual files from the management server. They are located in /var/log/VPlex/cli/. There is one
perpetual monitor file per director, identifiable by the keyword “PERPETUAL” .
The following is an example for the statistics that perpetual monitors collect on virtual volumes:
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.1
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.2
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.3
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.4
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.5
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.6
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.7
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.8
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.9
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.10
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.1
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.2
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.3
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.4
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.5
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.6
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.7
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.8
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.9
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR.log.10
86
Performance and Monitoring