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

Preserve the Fault Handler, the ID of the IOP that is driving the CE boot

Page 241 highlights

Chapter 13 MtcMon Messages IOPn.MtcMon status: An unknown packet has been received by the Monitor. Packet command = x. Variables x - the transport command type of the received event Severity Error Description If this message is generated if an IOP receives a message over the ESI or IL that has an illegal transport command type. The Fault Handler is invoked, and an IOP or a CE may be removed as a result of this message. Related Messages IOPn.MtcMon status: IOPx has been removed from service. IOPn.MtcMon status: CEx has been removed from service. IOPn.MtcMon status: IOPx is faulted and requires repair. IOPn.MtcMon status: CEx is faulted and requires repair. Hardware/Software Usually, this message is the result of a software error. In rare cases, this message can be caused by a hardware error that results in the corruption of data on an IOP or CE. Action • Preserve the Fault Handler's event log information and examine it to gather additional information related to the message. • If the IOP is removed, a crash dump may be generated. • Contact your service provider for assistance in the analysis of the crash dump. IOPn.MtcMon status: CE boot failed because the Monitor's ConfigurationArcTree Registry entry on IOPx is invalid. Variables x - the ID of the IOP that is driving the CE boot Severity Error Description This message is generated during an attempt to boot the Windows NT operating system on the CE(s). The boot failed because the ARC configuration tree passed to the CE(s) during boot was not valid. Related Messages IOPn.MtcMon status: The boot process has started for CEx. IOPn.MtcMon status: The synchronization process has failed for CEx. IOPn.MtcMon status: CEx has been removed from service. Hardware/Software This message is generated as a result of a software configuration error on the specified IOP Action • Recommit the configuration using the Endurance Configuration Utility. • Reinstall the Endurance software on IOPx. This recreates the configuration ARC tree which is stored in the Windows NT Registry on IOPx. • If the problem persists after a reinstallation on the IOP, contact your service provider for assistance. 231

  • 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

231
Chapter 13
MtcMon Messages
IOP
n
.MtcMon status: An unknown packet has been received by the Monitor. Packet command =
x
.
Variables
x
the transport command type of the received event
Severity
Error
Description
If this message is generated if an IOP receives a message over the ESI or IL that has an illegal
transport command type. The Fault Handler is invoked, and an IOP or a CE may be removed
as a result of this message.
Related Messages
IOP
n
.MtcMon status: IOP
x
has been removed from service.
IOP
n
.MtcMon status: CE
x
has been removed from service.
IOP
n
.MtcMon status: IOP
x
is faulted and requires repair.
IOP
n
.MtcMon status: CE
x
is faulted and requires repair.
Hardware/Software
Usually, this message is the result of a software error. In rare cases, this message can be caused
by a hardware error that results in the corruption of data on an IOP or CE.
Action
Preserve the Fault Handler
s event log information and examine it to gather additional
information related to the message.
If the IOP is removed, a crash dump may be generated.
Contact your service provider for assistance in the analysis of the crash dump.
IOP
n
.MtcMon status: CE boot failed because the Monitor's ConfigurationArcTree Registry entry on IOP
x
is invalid.
Variables
x
the ID of the IOP that is driving the CE boot
Severity
Error
Description
This message is generated during an attempt to boot the Windows NT operating system on the
CE(s). The boot failed because the ARC configuration tree passed to the CE(s) during boot was
not valid.
Related Messages
IOP
n
.MtcMon status: The boot process has started for CE
x
.
IOP
n
.MtcMon status: The synchronization process has failed for CE
x
.
IOP
n
.MtcMon status: CE
x
has been removed from service.
Hardware/Software
This message is generated as a result of a software configuration error on the specified IOP
Action
Recommit the configuration using the Endurance Configuration Utility.
Reinstall the Endurance software on IOP
x
. This recreates the configuration ARC tree
which is stored in the Windows NT Registry on IOP
x
.
If the problem persists after a reinstallation on the IOP, contact your service provider for
assistance.