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
director-1-1-B B0-FC00 (front-end) crc-errors has increased by 15254
director-1-1-B B0-FC01 (front-end) crc-errors has increased by 953630
Things to note
Take note of the number of ports and the number of directors reporting issues. For instance, if half of the ports are reporting
issues, then it may indicate a fabric-wide event. Whereas if only one port is reporting an error, then the problem is localized to a
specific I-T Nexus.
The script is designed to suppress email after 5 minutes (as to not flood an email server). At that point, it will only report once
an hour. The firmware connect to management server will contain all reports including any that were suppressed to email.
The following table contains a list of stats being monitored. What is being monitored depends on the hardware type, VS2 or
VS6, and the GeoSynchrony code level. While the script can be applied to any code level at 6.0 SP1 (6.0.1.00.00.08) and above,
what it can monitor depends the availability of the underlying stats. See below in the attachment (restricted) section a larger
view of this table.
Logging: The logging file port-stats-monitor.log can be found on the management server in the /var/log/
VPlex/cli/ directory.This log file is gathering raw data. The grep command [grep "back-end\|front-end\|wan-
com" /var/log/VPlex/cli/port-stats-monitor.log] can produce a summary that is related to error reported in the
port-stats-monitor.log file.
Example:
grep "back-end\|front-end\|wan-com" /var/log/VPlex/cli/port-stats-monitor.log
/var/log/VPlex/cli/port-stats-monitor.log.9:director-1-1-B B1-FC02 (back-end) invalid-
transmission-word has increased by 2956
/var/log/VPlex/cli/port-stats-monitor.log.9:director-1-1-B B1-FC02 (back-end) loss-of-
sync has increased by 443
/var/log/VPlex/cli/port-stats-monitor.log.9:director-1-1-B B1-FC02 (back-end) invalid-
transmission-word has increased by 3494
/var/log/VPlex/cli/port-stats-monitor.log.9:director-1-1-B B1-FC02 (back-end) loss-of-
sync has increased by 528
/var/log/VPlex/cli/port-stats-monitor.log.9:director-1-1-B B1-FC02 (back-end) invalid-
transmission-word has increased by 5996
Statistics
Metro node collects and reports three types of statistics:
● counters - Monotonically increasing value (analogous to a car’s odometer)
Performance and Monitoring
95