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

If the condition is due to mirror set differences, then the removal and rejoining of an IOP

Page 213 highlights

Chapter 13 MtcMon Messages IOPn.MtcMon FRU: IOP1 IOP2 interconnect fault. Severity Error Description An unqualified failure has occurred in the communication path between two IOPs. Generally, this is a failure in the IL path. The fault may be caused by: • An improperly configured or failed Ethernet adapter • A faulty cable between the adapters • An IOP that is faulted • An IOP that has become hung in a device driver Action • Check the cabling between the IOPs. • Run diagnostics on the adapters that support the IL on each of the IOPs. • If the IOP that is removed as a result of this error does not shut down cleanly (that is, if it hangs or crashes), then reboot the IOP and examine its log for indications of device or driver failure. IOPn.MtcMon FRU: IOP1 or IOP2 processing capability failure or data set divergence. Severity Error Description The IOPs' response(s) to a request made by the CE's operating system are different. This may be due to either a software or hardware malfunction in an IOP, or a difference in the disk data between members of a mirror set. If the condition is due to mirror set differences, then the removal and rejoining of an IOP selected for removal as part of this message causes both mirror sets to be equivalent. If this message occurs around the time of a system state transition, it could also be the result of a software malfunction on an IOP, or a difference in the network configuration between the IOPs. Action • Use diagnostics to test whether the disk subsystem on the IOPs is functioning properly. • Also, check the Windows NT event log to see if there are disk messages logged against a particular SCSI device, and replace that device if this is the case. • If the condition persists and there is no other indication of a faulty component, contact your service provider for assistance. • Make sure that the network cards on your IOPs are identical models and are identically configured. 203

  • 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

203
Chapter 13
MtcMon Messages
IOP
n
.MtcMon FRU: IOP1 <-> IOP2 interconnect fault.
Severity
Error
Description
An unqualified failure has occurred in the communication path between two IOPs. Generally,
this is a failure in the IL path. The fault may be caused by:
An improperly configured or failed Ethernet adapter
A faulty cable between the adapters
An IOP that is faulted
An IOP that has become hung in a device driver
Action
Check the cabling between the IOPs.
Run diagnostics on the adapters that support the IL on each of the IOPs.
If the IOP that is removed as a result of this error does not shut down cleanly (that is, if it
hangs or crashes), then reboot the IOP and examine its log for indications of device or
driver failure.
IOP
n
.MtcMon FRU: IOP1 or IOP2 processing capability failure or data set divergence.
Severity
Error
Description
The IOPs
response(s) to a request made by the CE
s operating system are different. This may
be due to either a software or hardware malfunction in an IOP, or a difference in the disk data
between members of a mirror set.
If the condition is due to mirror set differences, then the removal and rejoining of an IOP
selected for removal as part of this message causes both mirror sets to be equivalent.
If this message occurs around the time of a system state transition, it could also be the result of
a software malfunction on an IOP, or a difference in the network configuration between the
IOPs.
Action
Use diagnostics to test whether the disk subsystem on the IOPs is functioning properly.
Also, check the Windows NT event log to see if there are disk messages logged against a
particular SCSI device, and replace that device if this is the case.
If the condition persists and there is no other indication of a faulty component, contact
your service provider for assistance.
Make sure that the network cards on your IOPs are identical models and are identically
configured.