Dell PowerVault MD3260i CLI Guide - Page 19

Exit Status, Status Value

Page 19 highlights

When an exception occurs while executing a command, the CLI automatically saves the error information to a file named excprpt.txt. The CLI attempts to place excprpt.txt in the directory specified by the system property devmgr.datadir, which by default is the "client/data" directory under the main installation directory in Windows and the /var/opt/SM directory in Linux. If for any reason the CLI cannot place the file in the devmgr.datadir-specified directory, the CLI saves the excprpt.txt file in the same directory from which the CLI is running. You cannot change the file name or location. The excprpt.txt file is overwritten every time an exception occurs. To save the information in the excprpt.txt file, you must to copy the information to a new file or directory. Exit Status After you run a CLI command or a CLI and script command, status is displayed that indicates the success of the operation defined by the command. The status values are shown in the following table. Table 3. Exit Status Status Value Meaning 0 The command terminated without an error. 1 The command terminated with an error. Error information is also displayed. 2 The script file does not exist. 3 An error occurred while opening an output file. 4 A storage array is not at the specified address. 5 Addresses specify different storage arrays. 6 A storage array name does not exist for the host agent connected. 7 The storage array name was not at the specified address. 8 The storage array name was not in the configuration file. 10 A management class does not exist for the storage array. 11 A storage array was not found in the configuration file. 12 An internal error occurred. 13 Invalid script syntax was found. 14 The RAID controller module was unable to communicate with the storage array. 15 A duplicate argument was entered. 16 An execution error occurred. 17 A host was not at the specified address. 18 The World Wide Identifier (WWID) was not in the configuration file. 19 The WWID was not at the address. 20 An unknown IP address was specified. 21 The event monitor configuration file was corrupted. 22 The storage array was unable to communicate with the event monitor. 23 The RAID controller module was unable to write alert settings. 19

  • 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

When an exception occurs while executing a command, the CLI automatically saves the error information to a file
named
excprpt.txt
. The CLI attempts to place
excprpt.txt
in the directory specified by the system property
devmgr.datadir
, which by default is the "client/data" directory under the main installation directory in Windows and
the
/var/opt/SM
directory in Linux. If for any reason the CLI cannot place the file in the
devmgr.datadir
-specified
directory, the CLI saves the
excprpt.txt
file in the same directory from which the CLI is running. You cannot change the
file name or location. The
excprpt.txt
file is overwritten every time an exception occurs. To save the information in the
excprpt.txt
file, you must to copy the information to a new file or directory.
Exit Status
After you run a CLI command or a CLI and script command, status is displayed that indicates the success of the
operation defined by the command. The status values are shown in the following table.
Table 3. Exit Status
Status Value
Meaning
0
The command terminated without an error.
1
The command terminated with an error. Error information is also displayed.
2
The script file does not exist.
3
An error occurred while opening an output file.
4
A storage array is not at the specified address.
5
Addresses specify different storage arrays.
6
A storage array name does not exist for the host agent connected.
7
The storage array name was not at the specified address.
8
The storage array name was not in the configuration file.
10
A management class does not exist for the storage array.
11
A storage array was not found in the configuration file.
12
An internal error occurred.
13
Invalid script syntax was found.
14
The RAID controller module was unable to communicate with the storage array.
15
A duplicate argument was entered.
16
An execution error occurred.
17
A host was not at the specified address.
18
The World Wide Identifier (WWID) was not in the configuration file.
19
The WWID was not at the address.
20
An unknown IP address was specified.
21
The event monitor configuration file was corrupted.
22
The storage array was unable to communicate with the event monitor.
23
The RAID controller module was unable to write alert settings.
19