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
2. Run the following command to push the files present on local node to specific nodes using metadata file information:
service@director-1-1-a:~> /opt/dell/vplex/bin/supportassist_mft sync --metadata-file /home/
service/mft/metadata.json --nodes 10.226.81.190
File 'softwareWeekly.tar.gz' with checksum
47a08c12d4dddc30039fd0a86642b64c435e14f1d6a0c9ccfd83eff03ee7dfbd copied to /home/
service/mft/ directory
File 'log.txt' with checksum
0a9ee4b41f72f67c2abff8dce7a087e9ff270bd0ef0b1bb79b7c5e4855b6d8a3 copied to /home/
service/mft/ directory
File 'MFT_API_TEST/DummyFIle_test.docx' with checksum
8605cdc9caff613128c26d5500374089da63953b353efcf8a6aa66c11135c949 copied to /home/
service/mft/ directory
Copying all the MFT file(s) present under the directory /data/mft/ from the node
[10.226.81.189] to node(s) ['10.226.81.190']
SCP command invoked to copy all the files from node [10.226.81.189] to node
[10.226.81.190]
Sync operation completed successfully on node 10.226.81.190
Event log locations
Metro node includes services, processes, components, and operating systems that write entries to various logs.
The system collects logs for:
● Call-home events
The locations of various logs on the metro node management server are listed in the following table:
Table 4. Metro node log file locations
Log name Description and location
Call home log On a running management server:
● /opt/dell/vplex/ese/var/log/ESE.log
● /var/log/vplex/SupportAssist/SupportAssist.log
NSFW log GeoSynchrony log. NSFW sends events to a journald service on the director. The journal service writes
NSFW entries to the journal in /var/log/journal/. To view and perform analysis of NSFW logs, the
following steps can be performed:
● In collect-diagnostics output: The journal is found voyager-diagnostics/journal/
diagnostic-collection_journal.export. It requires systemd-journal-remote to
convert to a journal.
1. systemd-journal-remote --output=<name>.journal /path/to/
journal.export
a. It converts the .export into a file readable by journalctl.
b. It is required to have a .journal suffix on the output file name.
2. journalctl --file=<name>.journal <other-flags>
a. It has all the same options available as any other journalctl command.
3. journalctl --file=<name>.journal -u nsfw
a. It limits the journal output to the nsfw unit. It is one example of the many journal flags that
one can use.
System Configuration log location
For more information on the System Configuration logs, see the Logs section in the Configuration and Installation Guide for the
metro node appliance available at SolVe (https://solveonline.emc.com/solve/home/74).
20
System Management