HP StorageWorks MSA2012i HP StorageWorks 2000 Modular Smart Array Reference Gu - Page 224

Configuring the Debug Log, Select Manage > Utilities > Debug Utilities > Debug Log Setup.

Page 224 highlights

8. If prompted to specify the file location and name, do so using a .logs extension. The default file name is store.logs. If you intend to capture multiple event logs, be sure to name the files appropriately so that they can be identified later. Note - If you are using Firefox and have a download directory set, the file is automatically saved there. Configuring the Debug Log When instructed to do so by service personnel, as an Advanced Manage user you can configure the debug log. The debug log captures data that will help service personnel locate problems within the system logic. After you configure the debug log as instructed, you will need to perform I/O to the system or re-create the situation that is causing the fault. This populates the debug log with information that service personnel can use to diagnose the system. Note - The debug log only collects data after you configure it. It will not contain information about any problems that occurred before you configure it. To configure the debug log: 1. Select Manage > Utilities > Debug Utilities > Debug Log Setup. The Debug Log Setup page is displayed. 2. Select the debug log setup you want. ■ Standard - Used for diagnosing general problems. With minimal impact on I/O performance, it collects a wide range of debug data. ■ I/O - Performance - Used for diagnosing I/O interface problems. Using this option, the debug log is dedicated to collecting I/O interface information, with minimal impact on I/O performance. ■ Device-Side - Used for diagnosing device-side problems. It collects device failure data as well as I/O interface information, with minimal impact on I/O performance. ■ Device Management - Collects very verbose information, including all Configuration API (CAPI) transactions. Because this option collects a lot of data, it has a substantial impact on performance and quickly fills up the debug trace. 224 HP StorageWorks 2000 Family Modular Smart Array reference guide • August 2008

  • 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
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

224
HP StorageWorks 2000 Family Modular Smart Array reference guide
August 2008
8.
If prompted to specify the file location and name, do so using a
.logs
extension.
The default file name is
store.logs
. If you intend to capture multiple event logs,
be sure to name the files appropriately so that they can be identified later.
Note –
If you are using Firefox and have a download directory set, the file is
automatically saved there.
Configuring the Debug Log
When instructed to do so by service personnel, as an Advanced Manage user you
can configure the debug log. The debug log captures data that will help service
personnel locate problems within the system logic.
After you configure the debug log as instructed, you will need to perform I/O to the
system or re-create the situation that is causing the fault. This populates the debug
log with information that service personnel can use to diagnose the system.
Note –
The debug log only collects data after you configure it. It will not contain
information about any problems that occurred before you configure it.
To configure the debug log:
1.
Select Manage > Utilities > Debug Utilities > Debug Log Setup.
The Debug Log Setup page is displayed.
2.
Select the debug log setup you want.
Standard – Used for diagnosing general problems. With minimal impact on I/O
performance, it collects a wide range of debug data.
I/O - Performance – Used for diagnosing I/O interface problems. Using this
option, the debug log is dedicated to collecting I/O interface information, with
minimal impact on I/O performance.
Device-Side – Used for diagnosing device-side problems. It collects device
failure data as well as I/O interface information, with minimal impact on I/O
performance.
Device Management – Collects very verbose information, including all
Configuration API (CAPI) transactions. Because this option collects a lot of data,
it has a substantial impact on performance and quickly fills up the debug trace.