SANtricity 11.8 Commands ( CA08871-194 ～ 196 )
Save storage Array events
The save storageArray warningEvents command saves events from the Major Event Log to a file.
Supported Series
This command applies to any individual storage system, including the HB2100/HB2200/HB2300, HB5100/HB5200, AB6100 and AB3100 series, as long as all SMcli packages are installed.
Roles
To execute this command on an HB2100/HB2200/HB2300, HB5100/HB5200, AB6100, or AB3100 storage system, you must have the Storage Admin role.
Context
This command saves events from the Major Event Log to a file. You can save these events:
-
Critical events — An error occurred on the storage system that needs to be addressed immediately. Loss of data access might occur if you do not immediately correct the error.
-
Warning events — An error occurred on the storage system that results in degraded performance or reduced ability to recover from another error. Access to data has not been lost, but you must correct the error to prevent possible loss of data access if another error would occur.
-
Informational events — An event occurred on the storage system that does not impact normal operations. The event is reporting a change in configuration or other information that might be useful in evaluating how well the storage system is performing.
-
Debug events — An event occurred on the storage system that provides information that you can use to help determine the steps or states that led to an error. You can send a file with this information to Fujitsu Support to help determine the cause of an error.
|
Some storage systems might not be able to support all four types of events. |
Syntax
save storageArray (allEvents | criticalEvents | warningEvents | infoEvents | debugEvents) file="filename" [count=numberOfEvents] [forceSave=(TRUE | FALSE)]
Parameters
| Parameter | Description | ||
|---|---|---|---|
|
The parameter to save all of the events to a file. |
||
|
The parameter to save only the critical events to a file. |
||
|
The parameter to save only the warning events to a file. |
||
|
The parameter to save only the informational events to a file. |
||
|
The parameter to save only the debug events to a file. |
||
|
The file path and the file name to which you want to save the events. Enclose the file name in double quotation marks (" "). For example:
The default name of the file that contains the contents of the Major Event Log is |
||
|
The number of events that you want to save to a file. If you do not enter a value for the count, all events matching the type of event you specify are saved to the file. If you enter a value for the count, only that number of events (starting with the last event entered) are saved to the file. Use integer values. |
||
|
The parameter to force saving the debug events you may have filtered from view to a file. To force saving the events, set this parameter to
|
