- Notes, cautions, and warnings
- Preface
- CLI Workspace and User Accounts
- Meta Volumes
- System Management
- Events and alerts
- About call-home notifications
- Additional documentation
- SupportAssist MFT feature
- Event log locations
- System Configuration log location
- SupportAssist Syslog
- SupportAssist syrcollect feature
- SupportAssist Connectivity Command
- Hardware acceleration with VAAI
- Offload copy overhead with XCOPY
- Change the name of the cluster
- LCD Front Panel settings
- 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
Dell EMC Metro node 7.1 Administrator Guide
Managing and Monitoring back-end network
For high availability each director should have multiple paths to each storage volume. Environmental issues such as network congestion or array problems can affect the availability and performance of these paths. Metro node monitors the latency of each back-end IT Nexus, and there is a possibility of encountering poorly performing back-end paths. Metro node has several mechanisms to limit the performance impact:
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: <>()\