HP Integrity rx8620 HP Insight Manager WBEM Provider Events Reference - Page 39

An invalid XBC to XBC port was found. Probable Cause: Loss of Lockstep

Get HP Integrity rx8620 PDF manuals and user guides View all HP Integrity rx8620 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 39 highlights

Event ID Event Severity Event Description 5896 Error Coherency controller (CC) registers indicate a Deadlock Recovery Reset. Probable Cause: Coherency controller (CC) resources are deadlocked and the CC is resetting the cell. Recommended Action: Analyze the Deadlock Recovery logs (like MCA logs) to determine the cause of the failure. WBEM EventID: 1019. WBEM ProviderName: FPL_IndicationProvider 6002 Error A memory address parity error has been detected. The physical location can be located in the data field. Probable Cause: Poorly seated memory extender Recommended Action: Reseat memory extender WBEM EventID: 5268. WBEM ProviderName: FPL_IndicationProvider 6074 Error A DIMM loading order error has occurred. Probable Cause: Incorrect loading of the DIMMs on the cell Recommended Action: Install the DIMMs in the correct order. DIMMs are installed in ranks of DIMMs , starting with DIMM 0A, 0B, etc. Subsequent ranks are loaded in ascending order , i.e., rank 1, 2, 3, 4, 5, 6 and 7. WBEM EventID: 590. WBEM ProviderName: FPL_IndicationProvider 6146 Warning Refresh Control Error Timeout. Probable Cause: At start of memory refresh, timing out waiting for ready bit to be set Recommended Action: Contact HP Support personnel to troubleshoot the problem WBEM EventID: 591. WBEM ProviderName: FPL_IndicationProvider 6180 Warning memory extender/baseboard FRU mismatch. Probable Cause: Memory extender and baseboard are incompatible Recommended Action: Contact HP support to troubleshoot the problem WBEM EventID: 592. WBEM ProviderName: FPL_IndicationProvider 6730 Error Fabric topology mismatch with XBCs in complex. Probable Cause: There is a fabric topology mismatch with XBC in complex. Recommended Action: Contact HP Support personnel to analyze the cell, XBC flex cables, system backplane WBEM EventID: 593. WBEM ProviderName: FPL_IndicationProvider 6795 Warning An invalid XBC to XBC port was found. Probable Cause: Loss of Lockstep Recommended Action: Reset WBEM EventID: 594. WBEM ProviderName: FPL_IndicationProvider 7652 Warning Could not get neighbor information. Probable Cause: Defective XBC link Defective XBC Recommended Action: Check XBC link connections Reset the system backplane Contact HP Support personnel to troubleshoot problem WBEM EventID: 595. WBEM ProviderName: FPL_IndicationProvider 7653 Error The XBC's routing state was marked as in ERROR. Probable Cause: Another cell already attempted routing for the XBC and found an error. Recommended Action: Check for hardware failure: flex cables, crossbar chip, etc. WBEM EventID: 596. WBEM ProviderName: FPL_IndicationProvider 7655 Warning It indicates that there is no NVM error space left for logging an Error Event. Probable Cause: The error event will not be logged. WBEM EventID: 597. WBEM ProviderName: FPL_IndicationProvider 7657 Error An XBC port found to have an unexpected error. Probable Cause: A port was landmined so it had to be routed around. Recommended Action: Check flex cables WBEM EventID: 598. WBEM ProviderName: FPL_IndicationProvider 7658 Error A XBC port route around has occurred. Probable Cause: During routing, when a XBC to XBC port is found to be in error, or was previously marked in error, it is routed around. This chassis code indicates that which XBC port was routed around. Recommended Action: Reset the system backplane to clear the error If the suspect XBC port uses a flex cable, check / replace the flex cable and then the system backplane(s) involved. If the suspect XBC port uses the hardwire link built into the system backplane, replace the system backplane involved. WBEM EventID: 599. WBEM ProviderName: FPL_IndicationProvider 7660 Warning During routing a crossbar is found to be in an unexpected routing state. Probable Cause: An XBC is indicating a port failure Recommended Action: Validate all of the cells connectivity to the PD Check the XBC chips seating reset the system replace either cells/system backplane WBEM EventID: 600. WBEM ProviderName: FPL_IndicationProvider Platform Events 39

  • 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
Coherency controller (CC) registers indicate a Deadlock Recovery Reset. Probable
Cause: Coherency controller (CC) resources are deadlocked and the CC is resetting
the cell. Recommended Action: Analyze the Deadlock Recovery logs (like MCA logs)
to determine the cause of the failure. WBEM EventID: 1019. WBEM ProviderName:
FPL_IndicationProvider
Error
5896
A memory address parity error has been detected. The physical location can be located
in the data field. Probable Cause: Poorly seated memory extender Recommended
Action: Reseat memory extender WBEM EventID: 5268. WBEM ProviderName:
FPL_IndicationProvider
Error
6002
A DIMM loading order error has occurred. Probable Cause: Incorrect loading of the
DIMMs on the cell Recommended Action: Install the DIMMs in the correct order.
DIMMs are installed in ranks of DIMMs , starting with DIMM 0A, 0B, etc. Subsequent
ranks are loaded in ascending order , i.e., rank 1, 2, 3, 4, 5, 6 and 7. WBEM EventID:
590. WBEM ProviderName: FPL_IndicationProvider
Error
6074
Refresh Control Error Timeout. Probable Cause: At start of memory refresh, timing
out waiting for ready bit to be set Recommended Action: Contact HP Support
personnel to troubleshoot the problem WBEM EventID: 591. WBEM ProviderName:
FPL_IndicationProvider
Warning
6146
memory extender/baseboard FRU mismatch. Probable Cause: Memory extender and
baseboard are incompatible Recommended Action: Contact HP support to
troubleshoot the problem WBEM EventID: 592. WBEM ProviderName:
FPL_IndicationProvider
Warning
6180
Fabric topology mismatch with XBCs in complex. Probable Cause: There is a fabric
topology mismatch with XBC in complex. Recommended Action: Contact HP Support
personnel to analyze the cell, XBC flex cables, system backplane WBEM EventID:
593. WBEM ProviderName: FPL_IndicationProvider
Error
6730
An invalid XBC to XBC port was found. Probable Cause: Loss of Lockstep
Recommended Action: Reset WBEM EventID: 594. WBEM ProviderName:
FPL_IndicationProvider
Warning
6795
Could not get neighbor information. Probable Cause: Defective XBC link Defective
XBC Recommended Action: Check XBC link connections Reset the system backplane
Contact HP Support personnel to troubleshoot problem WBEM EventID: 595. WBEM
ProviderName: FPL_IndicationProvider
Warning
7652
The XBC's routing state was marked as in ERROR. Probable Cause: Another cell
already attempted routing for the XBC and found an error. Recommended Action:
Check for hardware failure: flex cables, crossbar chip, etc. WBEM EventID: 596.
WBEM ProviderName: FPL_IndicationProvider
Error
7653
It indicates that there is no NVM error space left for logging an Error Event. Probable
Cause: The error event will not be logged. WBEM EventID: 597. WBEM
ProviderName: FPL_IndicationProvider
Warning
7655
An XBC port found to have an unexpected error. Probable Cause: A port was
landmined so it had to be routed around. Recommended Action: Check flex cables
WBEM EventID: 598. WBEM ProviderName: FPL_IndicationProvider
Error
7657
A XBC port route around has occurred. Probable Cause: During routing, when a
XBC to XBC port is found to be in error, or was previously marked in error, it is
routed around. This chassis code indicates that which XBC port was routed around.
Recommended Action: Reset the system backplane to clear the error If the suspect
XBC port uses a flex cable, check / replace the flex cable and then the system
backplane(s) involved. If the suspect XBC port uses the hardwire link built into the
system backplane, replace the system backplane involved. WBEM EventID: 599.
WBEM ProviderName: FPL_IndicationProvider
Error
7658
During routing a crossbar is found to be in an unexpected routing state. Probable
Cause: An XBC is indicating a port failure Recommended Action: Validate all of the
cells connectivity to the PD Check the XBC chips seating reset the system replace
either cells/system backplane WBEM EventID: 600. WBEM ProviderName:
FPL_IndicationProvider
Warning
7660
Platform Events
39