HP NetServer AA 6200 HP NetServer AA 6200 Solution Release 3.0 Messages - Page 218

MtcMon FRU: Local hardware fault on IOP, Reboot the IOP.

Get HP NetServer AA 6200 PDF manuals and user guides View all HP NetServer AA 6200 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 218 highlights

Chapter 13 MtcMon Messages IOPn.MtcMon FRU: Local hardware fault on IOPx. Variables x - the ID of the IOP with the hardware error. Severity Error Description A fault was detected on the system disk used by the specified IOP, and the IOP has been removed from service. (Note that usually the IOP reporting the message is not the same as the IOP with the problem, since an IOP with a hardware error is usually unable to report an error to the event log.) Action • Reboot IOPx in maintenance or Offline I/O Processor mode. • Run CHKDSK or other Windows NT diagnostics in order to determine whether the device is faulty. • Examine the IOP Event Viewer log for device-specific errors. • Replace the disk or adapter if necessary. If the system disk failed, you may need to reinstall the Windows NT operating system and the Endurance software. • Reboot the IOP. IOPn.MtcMon FRU: Processing capability failure on unspecified CE. Severity Error Description An error occurred that originated from a CE, but the details were not sufficient to determine which CE caused the condition. Note: The CE removed as a result of this error may not be the source of the fault Related Messages Action The failure may have been caused by memory or other platform errors on a CE that were not detected at the time of the failure. However, in these cases, you may often have previous errors, either fatal or non-fatal, reported against one of the CEs. Examine the CE operating system or IOP event logs to locate these errors. IOPn.MtcMon FRU: Uncorrectable memory error on CEx IOPn.MtcMon FRU: Uncorrectable platform error on CEx IOPn.MtcMon Fault Handler status: CEx has reported n memory error(s). IOPn.MtcMon Fault Handler status: CEx has reported n platform error(s). • Run diagnostics on each CE to determine if one of them is faulty. • If this condition persists without other errors, contact your service provider for assistance. • Examine the CE or IOP error logs. If there are several recent memory errors reported against one of the CEs, then replace the memory. If there are several recent platform errors reported against one of the CEs, then consider replacing the CE. 208

  • 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
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
Chapter 13
MtcMon Messages
208
IOP
n
.MtcMon FRU: Local hardware fault on IOP
x
.
Variables
x
–
the ID of the IOP with the hardware error.
Severity
Error
Description
A fault was detected on the system disk used by the specified IOP, and the IOP has been
removed from service. (Note that usually the IOP reporting the message is
not
the same as the
IOP with the problem, since an IOP with a hardware error is usually unable to report an error
to the event log.)
Action
•
Reboot IOP
x
in maintenance or Offline I/O Processor mode.
•
Run CHKDSK or other Windows NT diagnostics in order to determine whether the device
is faulty.
•
Examine the IOP Event Viewer log for device-specific errors.
•
Replace the disk or adapter if necessary. If the system disk failed, you may need to
reinstall the Windows NT operating system and the Endurance software.
•
Reboot the IOP.
IOP
n
.MtcMon FRU: Processing capability failure on unspecified CE.
Severity
Error
Description
An error occurred that originated from a CE, but the details were not sufficient to determine
which CE caused the condition.
Note:
The CE removed as a result of this error may not be the source of the fault
The failure may have been caused by memory or other platform errors on a CE that were not
detected at the time of the failure. However, in these cases, you may often have previous errors,
either fatal or non-fatal, reported against one of the CEs. Examine the CE operating system or
IOP event logs to locate these errors.
Related Messages
IOPn.MtcMon FRU: Uncorrectable memory error on CEx
IOPn.MtcMon FRU: Uncorrectable platform error on CEx
IOPn.MtcMon Fault Handler status: CEx has reported n memory error(s).
IOPn.MtcMon Fault Handler status: CEx has reported n platform error(s).
Action
•
Run diagnostics on each CE to determine if one of them is faulty.
•
If this condition persists without other errors, contact your service provider for assistance.
•
Examine the CE or IOP error logs. If there are several recent memory errors reported
against one of the CEs, then replace the memory. If there are several recent platform errors
reported against one of the CEs, then consider replacing the CE.