HP Integrity rx2800 HP Insight Management WBEM Provider Events Reference Guide - Page 44

Waiting for the XBC Global Semaphore has timed out. Probable Cause: XBC Key

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

Page 44 highlights

7658 7660 7661 7663 7664 7666 7667 7669 7671 7673 7674 7684 Error Warning Warning Error Error Error Error Error Error Error Error Warning 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. 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. An unexpected XBC forward progress state was continually found until timing out. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PDCheck the XBC chips seating reset the system replace either cells/system backplane. WBEM EventID: 601. WBEM ProviderName: FPL_IndicationProvider. During remote routing, the current port's neighbor is not healthy. Probable Cause: An XBC port is not healthy. Recommended Action: Check for hardware failure: flex cables, crossbar chips, etc. WBEM EventID: 602. WBEM ProviderName: FPL_IndicationProvider. The CC to XBC link is not viable. Probable Cause: The CC to XBC link is not operational. Recommended Action: Reset the cell Reset the system backplane Contact HP Support personnel to troubleshoot problem. WBEM EventID: 603. WBEM ProviderName: FPL_IndicationProvider. Remote routing a crossbar failed. Probable Cause: A failure was encountered while performing remote routing on an XBC, most likely due to a problem with the system backplane or local cell. Recommended Action: Check for hardware failure: CC, XBC to CC link, flex cables, crossbar chip, etc. WBEM EventID: 604. WBEM ProviderName: FPL_IndicationProvider. Too many XBC-to-XBC were broken in the complex. Probable Cause: Port status indicated that two or more ports on a XBC had errors. Recommended Action: Check for hardware failure: flex cables, crossbar chip, etc. WBEM EventID: 605. WBEM ProviderName: FPL_IndicationProvider. This cell did not get the XBC Global Semaphore. Probable Cause: Another cell won the race and got the semaphore before this cell. This would be apparent in chassis codes. Recommended Action: None. WBEM EventID: 606. WBEM ProviderName: FPL_IndicationProvider. Attempted an XBC SM4 takeover and timed out trying to unlock the SM4. Probable Cause: Cannot takeover an XBC semaphore that has been held for a long time. Recommended Action: Try forcing firmware to reroute the fabric by cycling 48V power on the cabinets. Look for other fabric chassis codes that explain why the current owner of the SM4 was unable to release it. Look for fabric problems on the backplane. WBEM EventID: 607. WBEM ProviderName: FPL_IndicationProvider. Waiting for the XBC Global Semaphore has timed out. Probable Cause: XBC Key Contention. Hardware Failure. Recommended Action: Look for other chassis codes that indicate XBC Key contention. Check XBC. Check Links/Flex Cables. WBEM EventID: 608. WBEM ProviderName: FPL_IndicationProvider. A timeout occurred while attempting to release the XBC semaphore. Probable Cause: XBC Key Contention. Hardware Failure. Recommended Action: Look for additional chassis codes that would explain the failure. Check XBC. Check Link/Flex Cables. WBEM EventID: 609. WBEM ProviderName: FPL_IndicationProvider. Management Processor Firmware Battery Failure or NVRAM change. Probable Cause: Determine if the firmware was recently upgraded. This is often the reason for the NVRAM to change. If not, and the A/C power has been removed, than it's possible the battery is indeed going bad and would need to be replaced. WBEM EventID: 610. WBEM ProviderName: FPL_IndicationProvider. 44 WBEM Provider Event Tables

  • 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
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
An unexpected XBC forward progress state was continually found until timing out.
Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate
all of the cells connectivity to the PDCheck the XBC chips seating reset the system
replace either cells/system backplane. WBEM EventID: 601. WBEM ProviderName:
FPL_IndicationProvider.
Warning
7661
During remote routing, the current port's neighbor is not healthy. Probable Cause:
An XBC port is not healthy. Recommended Action: Check for hardware failure: flex
cables, crossbar chips, etc. WBEM EventID: 602. WBEM ProviderName:
FPL_IndicationProvider.
Error
7663
The CC to XBC link is not viable. Probable Cause: The CC to XBC link is not
operational. Recommended Action: Reset the cell Reset the system backplane Contact
HP Support personnel to troubleshoot problem. WBEM EventID: 603. WBEM
ProviderName: FPL_IndicationProvider.
Error
7664
Remote routing a crossbar failed. Probable Cause: A failure was encountered while
performing remote routing on an XBC, most likely due to a problem with the system
backplane or local cell. Recommended Action: Check for hardware failure: CC, XBC
to CC link, flex cables, crossbar chip, etc. WBEM EventID: 604. WBEM ProviderName:
FPL_IndicationProvider.
Error
7666
Too many XBC-to-XBC were broken in the complex. Probable Cause: Port status
indicated that two or more ports on a XBC had errors. Recommended Action: Check
for hardware failure: flex cables, crossbar chip, etc. WBEM EventID: 605. WBEM
ProviderName: FPL_IndicationProvider.
Error
7667
This cell did not get the XBC Global Semaphore. Probable Cause: Another cell won
the race and got the semaphore before this cell. This would be apparent in chassis
codes. Recommended Action: None. WBEM EventID: 606. WBEM ProviderName:
FPL_IndicationProvider.
Error
7669
Attempted an XBC SM4 takeover and timed out trying to unlock the SM4. Probable
Cause: Cannot takeover an XBC semaphore that has been held for a long time.
Recommended Action: Try forcing firmware to reroute the fabric by cycling 48V
power on the cabinets. Look for other fabric chassis codes that explain why the current
owner of the SM4 was unable to release it. Look for fabric problems on the backplane.
WBEM EventID: 607. WBEM ProviderName: FPL_IndicationProvider.
Error
7671
Waiting for the XBC Global Semaphore has timed out. Probable Cause: XBC Key
Contention. Hardware Failure. Recommended Action: Look for other chassis codes
that indicate XBC Key contention. Check XBC. Check Links/Flex Cables. WBEM
EventID: 608. WBEM ProviderName: FPL_IndicationProvider.
Error
7673
A timeout occurred while attempting to release the XBC semaphore. Probable Cause:
XBC Key Contention. Hardware Failure. Recommended Action: Look for additional
chassis codes that would explain the failure. Check XBC. Check Link/Flex Cables.
WBEM EventID: 609. WBEM ProviderName: FPL_IndicationProvider.
Error
7674
Management Processor Firmware Battery Failure or NVRAM change. Probable Cause:
Determine if the firmware was recently upgraded. This is often the reason for the
NVRAM to change. If not, and the A/C power has been removed, than it's possible
the battery is indeed going bad and would need to be replaced. WBEM EventID: 610.
WBEM ProviderName: FPL_IndicationProvider.
Warning
7684
44
WBEM Provider Event Tables