Dell PowerVault MD3260i CLI Guide - Page 160

Save Storage Array Events, forceSave=TRUE | FALSE]

Get Dell PowerVault MD3260i PDF manuals and user guides View all Dell PowerVault MD3260i manuals
Add to My Manuals
Save this manual to your list of manuals

Page 160 highlights

Parameter Description the LUN mapping, set this parameter to FALSE. The default value is FALSE. NOTE: When you use this command, you can specify any combination of the parameters for global setting, virtual disk configuration setting, host topology, or LUN mapping. To enter all settings, use the allConfig parameter. The parameters are optional; you do not have to enter any parameters. Save Storage Array Events This command saves events from the Major Event Log (MEL) to a file. Any or all of the following events can be saved: • Critical events-Errors occurring on the storage array that needs to be addressed immediately. Loss of data access may occur if the error is not immediately corrected. • Warning events-- Errors occurring on the storage array resulting in degraded performance or reduced ability to recover from additional errors. Access to data has not been lost, but the must be corrected to prevent possible loss of data access in the event of an additional error. • Informational events-Events occurring on the storage array that do not impact normal operations. This event is reporting a change in configuration or other information useful in evaluating the performance of the storage array. • Debug events-Events occurring on the storage array that provides information useful in determining steps or states that led to the error. This information may be useful to your Technical Support representative in helping determine error causes. NOTE: Some storage arrays may be unable to support all the above mentioned types of events. Syntax save storageArray (allEvents | criticalEvents warningEvents | infoEvents | debugEvents) file="filename" [count=numberOfEvents forceSave=(TRUE | FALSE)] Parameters Parameter allEvents Description Saves all events to a file. criticalEvents Saves only critical events to a file. warningEvents Saves only warning events to a file. infoEvents Saves only informational events to a file. debugEvents Saves only debug events to a file. file count Specifies name of the file to which to save the events. You must put quotation marks (" ") around the file name. Specifies the number of events or critical events to save to a file. If you do not enter a value for the count, all events or critical events are saved to the file. If you enter a value for the count, only that number of events or critical events 160

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
Parameter
Description
the LUN mapping, set this parameter to
FALSE
. The
default value is
FALSE
.
NOTE:
When you use this command, you can specify any combination of the parameters for global setting, virtual
disk configuration setting, host topology, or LUN mapping. To enter all settings, use the
allConfig
parameter.
The parameters are optional; you do not have to enter any parameters.
Save Storage Array Events
This command saves events from the Major Event Log (MEL) to a file.
Any or all of the following events can be saved:
•
Critical events—Errors occurring on the storage array that needs to be addressed immediately. Loss of data
access may occur if the error is not immediately corrected.
•
Warning events—- Errors occurring on the storage array resulting in degraded performance or reduced ability
to recover from additional errors. Access to data has not been lost, but the must be corrected to prevent
possible loss of data access in the event of an additional error.
•
Informational events—Events occurring on the storage array that do not impact normal operations. This event is
reporting a change in configuration or other information useful in evaluating the performance of the storage
array.
•
Debug events—Events occurring on the storage array that provides information useful in determining steps or
states that led to the error. This information may be useful to your Technical Support representative in helping
determine error causes.
NOTE:
Some storage arrays may be unable to support all the above mentioned types of events.
Syntax
save storageArray (allEvents | criticalEvents warningEvents
| infoEvents | debugEvents)
file="
filename
" [count=
numberOfEvents
forceSave=(TRUE | FALSE)]
Parameters
Parameter
Description
allEvents
Saves all events to a file.
criticalEvents
Saves only critical events to a file.
warningEvents
Saves only warning events to a file.
infoEvents
Saves only informational events to a file.
debugEvents
Saves only debug events to a file.
file
Specifies name of the file to which to save the events. You
must put quotation marks (" ") around the file name.
count
Specifies the number of events or critical events to save
to a file. If you do not enter a value for the count, all events
or critical events are saved to the file. If you enter a value
for the count, only that number of events or critical events
160