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

MtcMon status: Removing CE

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 277 highlights

Chapter 13 MtcMon Messages IOPn.MtcMon status: No ECC or parity memory detected on CEx. Chipset: vendor chipset. Memory mode: mode. IPMI found: Y/N Variables x - the ID of the CE that has no ECC or parity memory Y - IPMI was found in CEx N - IPMI was not found in CEx Severity Warning Description The CE software has determined that no ECC or parity memory exists on the CE. The lack of this type of memory increases the risk of the CEs having data corruption or divergence. This information is logged on the IOP that controls the booting and synchronizing of the CEs. Hardware/Software This message occurs as a result of CE hardware configuration information. Action • No action is required. However, Marathon recommends that you configure your Endurance server so that it has ECC or parity memory. • If you need help in determining whether you are using a qualified CE in your Endurance server, contact your service provider. IOPn.MtcMon status: Removing CEx so crash dump can proceed with only one active CE. Variables x - the ID of the CE being removed Severity Warning Description The Windows NT operating system running on the CE(s) has crashed and is attempting to generate a crash dump. This occurs if Windows NT initiates a crash dump and you configured Windows NT to generate a crash dump on system failures. All but one active CE is removed from service while the crash dump is being performed. Related Messages IOPn.MtcMon status: A crash dump is being taken for the Windows NT operating system running on the CEs. IOPn.MtcMon status: CEx has been removed from service. Hardware/Software This message is generated as a result of a hardware or software failure on the CE(s) that resulted in a crash of Windows NT. Action No action is required if the crash was intentional. The CE(s) automatically reboot and resynchronize when the crash dump completes. • Save the resulting memory.dmp file for offsite analysis. • Repair the hardware or software failure at the next opportunity. 267

  • 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
267
Chapter 13
MtcMon Messages
IOP
n
.MtcMon status: No ECC or parity memory detected on CE
x
.
Chipset:
vendor chipset
.
Memory mode:
mode
.
IPMI found:
Y/N
Variables
x
–
the ID of the CE that has no ECC or parity memory
Y
–
IPMI was found in CE
x
N
–
IPMI was not found in CE
x
Severity
Warning
Description
The CE software has determined that no ECC or parity memory exists on the CE. The lack of
this type of memory increases the risk of the CEs having data corruption or divergence.
This information is logged on the IOP that controls the booting and synchronizing of the CEs.
Hardware/Software
This message occurs as a result of CE hardware configuration information.
Action
•
No action is required. However, Marathon recommends that you configure your
Endurance server so that it has ECC or parity memory.
•
If you need help in determining whether you are using a qualified CE in your Endurance
server, contact your service provider.
IOP
n
.MtcMon status: Removing CE
x
so crash dump can proceed with only one active CE.
Variables
x
–
the ID of the CE being removed
Severity
Warning
Description
The Windows NT operating system running on the CE(s) has crashed and is attempting to
generate a crash dump. This occurs if Windows NT initiates a crash dump and you configured
Windows NT to generate a crash dump on system failures. All but one active CE is removed
from service while the crash dump is being performed.
Related Messages
IOP
n
.MtcMon status: A crash dump is being taken for the Windows NT
operating system running on the CEs.
IOP
n
.MtcMon status: CE
x
has been removed from service.
Hardware/Software
This message is generated as a result of a hardware or software failure on the CE(s) that
resulted in a crash of Windows NT.
Action
No action is required if the crash was intentional. The CE(s) automatically reboot and
resynchronize when the crash dump completes.
•
Save the resulting
memory.dmp
file for offsite analysis.
•
Repair the hardware or software failure at the next opportunity.