HP A3550A User Manual - A3661-90001 - Page 290

Front End Fibre Link Up

Page 290 highlights

Table 6-8 Informational Codes (Continued) Event code Event code name Description 0x666 0x667 0x668 Configured for Dual SP Cache Recovering Cache Recovered The disk array detected a change to a dual SP configuration. The SP is recovering the contents of the Write Cache following a reboot. The SP successfully completed recovering the contents of the Write Cache following a reboot. 0x66A 0x66B Soft Vault Load Failure Front End Fibre Link Up The SP could not load the saved contents of the Write Cache from disk. However, there were no physical units with saved data, so the Write Cache does not need to be loaded. This situation can occur after SP memory is reconfigured, for example, when both the RAID-3 memory size and the write cache size are changed at the same time. The front-end Fibre Channel interface started running. 0x66C 0x66D General Front End Fibre Link Unsolicited Peer SP timed out This event code is intended for use by development personnel in the factory. Contact your Hewlett-Packard support representative if this event code occurs. The host SP has timed out waiting for the peer SP to reply to a request. 0x670 0x680 0x681 0x682 0x683 0x684 Memory Dump This event code is intended for use by development personnel in the factory. Contact your Hewlett-Packard support representative if this event code occurs. Invalid Data Sector Read The hardware found a bad checksum on a data sector. Invalid Parity Sector Read The hardware found a bad checksum on a parity sector. Invalid Sector Read The hardware found a bad checksum on a sector. There is not enough information to determine whether the sector holds data or parity information. Data Sector Reconstructed The hardware reconstructed a data sector that had a checksum or write stamp error. Parity Sector Reconstructed The hardware reconstructed a parity sector that had a checksum or write stamp error. 0x685 Hard Error The hardware detected an error other than a parity or write stamp error. 0x686 0x687 Command Complete Stripe Reconstructed A command completed after a soft error was corrected. Inconsistent write time stamps in a RAID group were corrected. 0x688 Command Dropped An optional command was dropped. 6-42 Unsolicited Event Log

  • 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
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372

6-42
Unsolicited Event Log
0x666
Configured for Dual SP
The disk array detected a change to a dual SP configuration.
0x667
Cache Recovering
The SP is recovering the contents of the Write Cache
following a reboot.
0x668
Cache Recovered
The SP successfully completed recovering the contents of the
Write Cache following a reboot.
0x66A
Soft Vault Load Failure
The SP could not load the saved contents of the Write Cache
from disk. However, there were no physical units with saved
data, so the Write Cache does not need to be loaded. This
situation can occur after SP memory is reconfigured, for
example, when both the RAID-3 memory size and the write
cache size are changed at the same time.
0x66B
Front End Fibre Link Up
The front-end Fibre Channel interface started running.
0x66C
General Front End Fibre
Link Unsolicited
This event code is intended for use by development personnel
in the factory. Contact your Hewlett-Packard support
representative if this event code occurs.
0x66D
Peer SP timed out
The host SP has timed out waiting for the peer SP to reply to a
request.
0x670
Memory Dump
This event code is intended for use by development personnel
in the factory. Contact your Hewlett-Packard support
representative if this event code occurs.
0x680
Invalid Data Sector Read
The hardware found a bad checksum on a data sector.
0x681
Invalid Parity Sector
Read
The hardware found a bad checksum on a parity sector.
0x682
Invalid Sector Read
The hardware found a bad checksum on a sector. There is not
enough information to determine whether the sector holds
data or parity information.
0x683
Data Sector
Reconstructed
The hardware reconstructed a data sector that had a
checksum or write stamp error.
0x684
Parity Sector
Reconstructed
The hardware reconstructed a parity sector that had a
checksum or write stamp error.
0x685
Hard Error
The hardware detected an error other than a parity or write
stamp error.
0x686
Command Complete
A command completed after a soft error was corrected.
0x687
Stripe Reconstructed
Inconsistent write time stamps in a RAID group were
corrected.
0x688
Command Dropped
An optional command was dropped.
Table 6-8
Informational Codes (Continued)
Event code
Event code name
Description