HP Integrity Superdome SX1000 HP Insight Manager WBEM Provider Events Referenc - Page 27

LBA has unexpected number of I/O Slots. Probable Cause: Unsupported I/O

Page 27 highlights

Event ID Event Severity Event Description 5511 Error Error Processing encountered an unrecoverable error. Probable Cause: Decode the ASCII message and correct the problem. WBEM EventID: 416. WBEM ProviderName: FPL_IndicationProvider 5514 Error System is unable to complete the Reset For Reconfiguration request. Probable Cause: Delay the request for reconfiguration until after the PD has been released from Sinc BIB. WBEM EventID: 417. WBEM ProviderName: FPL_IndicationProvider 5515 Error The cell is not able to reach all requested cells through the fabric. Probable Cause: Fabric wasn't able to route to all cells described in the complex profile correctly due to a hardware problem. Some of the cells are unreachable. Update the complex profile or correct the hardware problem. WBEM EventID: 418. WBEM ProviderName: FPL_IndicationProvider 5518 Warning LBA has unexpected number of I/O Slots. Probable Cause: Unsupported I/O configuration. Recommended Action: Remove the I/O cards below the specified PCI-to-PCI bridge. WBEM EventID: 419. WBEM ProviderName: FPL_IndicationProvider 5521 Error Console device failed to connect. Probable Cause: Debugging event, not for release. WBEM EventID: 420. WBEM ProviderName: FPL_IndicationProvider 5525 Warning Copying memory test code failed. Probable Cause: Memory test code located in main memory has been corrupted Recommended Action: Contact HP support personnel to troubleshoot the problem WBEM EventID: 421. WBEM ProviderName: FPL_IndicationProvider 5527 Error A remote cell is in an unknown state of PD rendezvous. Probable Cause: Reset the PD. WBEM EventID: 2430. WBEM ProviderName: FPL_IndicationProvider 5528 Error Multiple Core Cells have been discovered in the same PD. Probable Cause: Verify that the complex profile is correct and reset the partition. WBEM EventID: 423. WBEM ProviderName: FPL_IndicationProvider 5529 Error The utilities component encountered an error when sending a command to the MP. Probable Cause: Verify the utilities system is connected correctly and reset. WBEM EventID: 424. WBEM ProviderName: FPL_IndicationProvider 5530 Warning Error received after issuing the Retrieve Cell Slot State command. Probable Cause: Make sure the GSP is connected and reset. WBEM EventID: 1007. WBEM ProviderName: FPL_IndicationProvider 5546 Error This indicates that all the cpus in the cell did not rendezvous during the MCA. Probable Cause: When this happens the cell will step through some of the error logging code on its own and then reset itself. WBEM EventID: 426. WBEM ProviderName: FPL_IndicationProvider 5547 Error This indicates that it does not have any access to the PD. Probable Cause: Forward Progress indicator; the cell will independently step through the error logging steps before it resets itself. WBEM EventID: 427. WBEM ProviderName: FPL_IndicationProvider 5548 Error This indicates the loss of lockstep during the MCA path. Probable Cause: The cell will take up a few more error logging steps independently before resetting itself. WBEM EventID: 428. WBEM ProviderName: FPL_IndicationProvider 5550 Error The PD level cell rendezvous failed. Probable Cause: This means that the cells will independently step through some of the error logging code and then reset themselves. WBEM EventID: 429. WBEM ProviderName: FPL_IndicationProvider 5556 Error It stands for diagnosis of catastrophic errors in the PIN block of concorde. Probable Cause: This means that the cell will be reset. WBEM EventID: 557. WBEM ProviderName: FPL_IndicationProvider 5557 Error The cell monarch cpu has failed. Probable Cause: The monarch cpu will be deconfigured. WBEM EventID: 1020. WBEM ProviderName: FPL_IndicationProvider Platform Events 27

  • 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

Event Description
Event Severity
Event ID
Error Processing encountered an unrecoverable error. Probable Cause: Decode the
ASCII message and correct the problem. WBEM EventID: 416. WBEM ProviderName:
FPL_IndicationProvider
Error
5511
System is unable to complete the Reset For Reconfiguration request. Probable Cause:
Delay the request for reconfiguration until after the PD has been released from Sinc
BIB. WBEM EventID: 417. WBEM ProviderName: FPL_IndicationProvider
Error
5514
The cell is not able to reach all requested cells through the fabric. Probable Cause:
Fabric wasn't able to route to all cells described in the complex profile correctly due
to a hardware problem. Some of the cells are unreachable. Update the complex profile
or correct the hardware problem. WBEM EventID: 418. WBEM ProviderName:
FPL_IndicationProvider
Error
5515
LBA has unexpected number of I/O Slots. Probable Cause: Unsupported I/O
configuration. Recommended Action: Remove the I/O cards below the specified
PCI-to-PCI bridge. WBEM EventID: 419. WBEM ProviderName:
FPL_IndicationProvider
Warning
5518
Console device failed to connect. Probable Cause: Debugging event, not for release.
WBEM EventID: 420. WBEM ProviderName: FPL_IndicationProvider
Error
5521
Copying memory test code failed. Probable Cause: Memory test code located in main
memory has been corrupted Recommended Action: Contact HP support personnel
to troubleshoot the problem WBEM EventID: 421. WBEM ProviderName:
FPL_IndicationProvider
Warning
5525
A remote cell is in an unknown state of PD rendezvous. Probable Cause: Reset the
PD. WBEM EventID: 2430. WBEM ProviderName: FPL_IndicationProvider
Error
5527
Multiple Core Cells have been discovered in the same PD. Probable Cause: Verify
that the complex profile is correct and reset the partition. WBEM EventID: 423. WBEM
ProviderName: FPL_IndicationProvider
Error
5528
The utilities component encountered an error when sending a command to the MP.
Probable Cause: Verify the utilities system is connected correctly and reset. WBEM
EventID: 424. WBEM ProviderName: FPL_IndicationProvider
Error
5529
Error received after issuing the Retrieve Cell Slot State command. Probable Cause:
Make sure the GSP is connected and reset. WBEM EventID: 1007. WBEM
ProviderName: FPL_IndicationProvider
Warning
5530
This indicates that all the cpus in the cell did not rendezvous during the MCA.
Probable Cause: When this happens the cell will step through some of the error
logging code on its own and then reset itself. WBEM EventID: 426. WBEM
ProviderName: FPL_IndicationProvider
Error
5546
This indicates that it does not have any access to the PD. Probable Cause: Forward
Progress indicator; the cell will independently step through the error logging steps
before it resets itself. WBEM EventID: 427. WBEM ProviderName:
FPL_IndicationProvider
Error
5547
This indicates the loss of lockstep during the MCA path. Probable Cause: The cell
will take up a few more error logging steps independently before resetting itself.
WBEM EventID: 428. WBEM ProviderName: FPL_IndicationProvider
Error
5548
The PD level cell rendezvous failed. Probable Cause: This means that the cells will
independently step through some of the error logging code and then reset themselves.
WBEM EventID: 429. WBEM ProviderName: FPL_IndicationProvider
Error
5550
It stands for diagnosis of catastrophic errors in the PIN block of concorde. Probable
Cause: This means that the cell will be reset. WBEM EventID: 557. WBEM
ProviderName: FPL_IndicationProvider
Error
5556
The cell monarch cpu has failed. Probable Cause: The monarch cpu will be
deconfigured. WBEM EventID: 1020. WBEM ProviderName: FPL_IndicationProvider
Error
5557
Platform Events
27