Save storage array support data
The save storageArray supportData
command saves the support-related information of the storage array to a file.
Supported Arrays
This command applies to any individual storage array, including the E4000, E2700, E5600, E2800, E5700, EF600 and EF300 arrays, as long as all SMcli packages are installed.
Roles
To execute this command on an E4000, E2800, E5700, EF600, or EF300 storage array, you must have the Storage Admin or Support Admin role.
Context
The following table lists the type of support data that you can collect.
Type of data | File name and description | ||
---|---|---|---|
Automatic Load Balancing statistics |
This file, one per controller, specify various statistics related to the Automatic Load Balancing feature that allow further analysis via offline analysis tool. |
||
Core dump metadata |
This file contains core dump metadata for the array.
|
||
AutoSupport status |
This file specifies the current status of ASUP for the given array. |
||
The AutoSupport history file |
This file specifies all ASUP messages, both standard and AutoSupport OnDemand messages, for the given array. Each entry in the table corresponds to an ASUP message currently sitting in one of the repositories for a given array. |
||
AutoSupport logs |
This file contains all the transmitted AutoSupport messages. |
||
Web Server Client Info |
This file specifies various Web Services client information.
|
||
Drive cabling topology |
|
||
Cumulative statistics bundles |
This file contains cumulative statistics for the controllers. |
||
Misbehaving drive log |
This file contains the storage array controller drive-side error and event log messages. |
||
Controller health image metadata |
This file contains DPL controller health image information.
|
||
DOM 0 journal files for controller A (E2800 or E5700 only) |
This file, one per controller, contains detailed Linux system logs. This includes logs for Linux packages and standard Linux utilities and services. |
||
DOM 0 journal files for controller B (E2800 or E5700 only) |
This file, one per controller, contains detailed Linux system logs. This includes logs for Linux packages and standard Linux utilities and services. |
||
Miscellaneous DOM 0 log files for controller A (E2800 or E5700 only) |
This file, one per controller, contains system logs that cannot be contained with the Journal. This includes the serial log for the RAID Application and debug logs for the Hypervisor. |
||
Miscellaneous DOM 0 log files for controller B (E2800 or E5700 only) |
This file, one per controller, contains system logs that cannot be contained with the Journal. This includes the serial log for the RAID Application and debug logs for the Hypervisor. |
||
Drive command aging timeout values |
|
||
Drive health logs |
|
||
Drive performance analyzer data |
This file contains drive performance data that helps you identify any drives that are performing below expectations. |
||
Enterprise Management Window configuration |
This file contains the EMW configuration data store file.
|
||
Tray event logs |
ESM event logs. |
||
Failed repository analysis |
This file contains the failed repository analysis information. |
||
Features of the storage array |
|
||
Firmware inventory |
|
||
InfiniBand interface statistics (InfiniBand only) |
This file contains the InfiniBand interface statistics. |
||
I/O path statistics |
|
||
IOC dump info for the host interface chip |
|
||
IOC dump logs for the host interface chip |
|
||
iSCSI connections (iSCSI only) |
|
||
iSCSI statistics (iSCSI only) |
|
||
iSER interface statistics (iSER over InfiniBand only) |
|
||
Major event log |
|
||
Manifest file |
This file contains a table that describes the files included in the archive file and the collected status of each of those files. |
||
Storage management software runtime information |
This file contains the storage management software application runtime information. Contains the JRE version currently used by the storage management software. |
||
NVMe-oF statistics |
This file contains a list of statistics, including NVMe controller statistics, NVMe queue statistics, and interface statistics for the transport protocol (for example, InfiniBand). |
||
NVSRAM data |
|
||
Object bundle |
This bundle contains a detailed description of the status of your storage array and its components, which was valid at the time that the file was generated. |
||
Summary performance statistics |
This file contains various controller performance statistics, one file per controller. |
||
Persistent reservations and registrations |
|
||
Storage management software user preferences |
This file contains the user preference persistent data store.
|
||
Recovery Guru procedures |
|
||
Recovery profile |
|
||
SAS PHY error logs |
This file contains the error information for SAS PHY. |
||
State capture data |
|
||
Storage array configuration |
|
||
Storage array profile |
|
||
Trace buffer contents |
|
||
Tray capture data |
|
||
Unreadable sectors |
|
||
Web Services Trace Log (E2800 or E5700 only) |
This file, one per controller, contains Web Services trace buffers that are used to record debug information. |
||
Workload capture analytics log file |
This file, one per controller, contains computed key workload characteristics such as LBA histogram, read/write ratio and I/O throughput across all active volumes. |
||
X-header data file |
|
Syntax
save storageArray supportData file="filename" [force=(TRUE | FALSE)]
save storageArray supportData file="filename"
[force=(TRUE | FALSE) |
csbSubsetid=(basic | weekly | event | daily | complete) |
csbTimeStamp=hh:mm]
Parameters
Parameter | Description |
---|---|
|
The file path and the file name to which you want to save the support-related data for the storage array. Enclose the file path and the file name in double quotation marks (" "). For example:
|
|
This parameter forces the collection of support data if there are any failures in securing a lock on controller operations. To force the collection of support data, set this parameter to |
Notes
Starting with firmware level 7.86, the file name extension must be .7z
. If you are running a firmware version earlier than 7.86, the files extension must be .zip
.
Minimum firmware level
7.80 adds the force
parameter.
8.30 adds information for the E2800 storage array.