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

HP NetServer AA Solution Administrator, Guide, HP NetServer AA 6200 Solution Release Notes

Page 238 highlights

Chapter 13 MtcMon Messages IOPn.MtcMon status: An error occurred on IOPx reading the thresholding database during IOP joining. Variables x - the ID of the IOP that had an error Severity Error Description An error occurred while attempting to read the thresholding database on an active IOP while a remote IOP was joining. This message can be due to either a resource problem, such as a lack of available free pool, or a threshold database corruption error. Related Messages IOPn.MtcMon status: The join process has failed for IOPx. Hardware/Software This message indicates a software error. Action The active IOP has a corrupted threshold database. This results in potential problems during fault handling. No other IOP can be joined until this condition is resolved. • Reconfigure the Endurance server software on the active IOP. • Then reboot it. IOP joining then takes place. Refer to Chapter 9 in HP NetServer AA Solution Administrator's Guide for information about how to reboot an IOP. IOPn.MtcMon status: An invalid BOOT REQUEST packet has been received from CEx. Variables x - the ID of the CE that generated an invalid boot request Severity Error Description The specified CE generated an invalid request to be booted or synchronized. Hardware/Software This message may be generated as a result of either a hardware failure or the incorrect revision of the MIC BIOS running in the CE. Action If the CE subsequently boots or synchronizes, no action is necessary. If it does not boot or synchronize: • Verify that the specified CE is running the correct version of the MIC BIOS, as specified in HP NetServer AA 6200 Solution Release Notes (Release 3.0 Service Pack 1) for the version of the Endurance software that is installed on the IOP that generated this message. • If the incorrect version is running, reset the MIC and use the MTCFLASH utility to update the MIC BIOS. Refer to Chapter 7 in HP NetServer AA Solution Administrator's Guide for information about how to use MTCFLASH. • If the revision of the MIC BIOS is correct and the problem persists, replace the MIC adapter in the CE. • If the problem persists, contact your service provider for assistance. 228

  • 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
228
IOP
n
.MtcMon status: An error occurred on
IOP
x
reading the thresholding database during IOP joining.
Variables
x
the ID of the IOP that had an error
Severity
Error
Description
An error occurred while attempting to read the thresholding database on an active IOP while a
remote IOP was joining. This message can be due to either a resource problem, such as a lack
of available free pool, or a threshold database corruption error.
Related Messages
IOP
n
.MtcMon status: The join process has failed for
IOP
x
.
Hardware/Software
This message indicates a software error.
Action
The active IOP has a corrupted threshold database. This results in potential problems during
fault handling. No other IOP can be joined until this condition is resolved.
Reconfigure the Endurance server software on the active IOP.
Then reboot it.
IOP joining then takes place. Refer to
Chapter 9
in
HP NetServer AA Solution Administrator
s
Guide
for information about how to reboot an IOP.
IOP
n
.MtcMon status: An invalid BOOT REQUEST packet has been received from CE
x
.
Variables
x
the ID of the CE that generated an invalid boot request
Severity
Error
Description
The specified CE generated an invalid request to be booted or synchronized.
Hardware/Software
This message may be generated as a result of either a hardware failure or the incorrect revision
of the MIC BIOS running in the CE.
Action
If the CE subsequently boots or synchronizes, no action is necessary. If it does not boot or
synchronize:
Verify that the specified CE is running the correct version of the MIC BIOS, as specified
in
HP NetServer AA 6200 Solution Release Notes
(Release 3.0 Service Pack 1)
for the
version of the Endurance software that is installed on the IOP that generated this message.
If the incorrect version is running, reset the MIC and use the MTCFLASH utility to update
the MIC BIOS. Refer to
Chapter 7
in
HP NetServer AA Solution Administrator
s Guide
for
information about how to use MTCFLASH.
If the revision of the MIC BIOS is correct and the problem persists, replace the MIC
adapter in the CE.
If the problem persists, contact your service provider for assistance.