HP Integrity Superdome SX2000 Windows Integrity Management Agents Reference - Page 39

Probable Cause: An XBC is indicating a port failure Recommended Action: Validate

Page 39 highlights

Event ID Event Severity Event Description 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 SNMP Trap: hpevtFabricGetNeighborInfoError - 7652 in HPIFPTRAP.MIB. 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. SNMP Trap: hpevtXbcRoutingErrorState - 7653 in HPIFPTRAP.MIB. 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. SNMP Trap: hpevtNoNvmErrLogSpace - 7655 in HPIFPTRAP.MIB. 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 SNMP Trap: hpevtXbcPortError - 7657 in HPIFPTRAP.MIB. 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. SNMP Trap: hpevtXbcPortRouteAround - 7658 in HPIFPTRAP.MIB. 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 SNMP Trap: hpevtXbcUnexpectedState - 7660 in HPIFPTRAP.MIB. 7661 Warning 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 SNMP Trap: hpevtXbcRoutingStateTimeout 7661 in HPIFPTRAP.MIB. 7663 Error 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. SNMP Trap: hpevtXbcNeighborPortNotRoutable - 7663 in HPIFPTRAP.MIB. 7664 Error 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 SNMP Trap: hpevtFabricCcToXbcError - 7664 in HPIFPTRAP.MIB. 7666 Error 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. SNMP Trap: hpevtFabricRouteXbcError 7666 in HPIFPTRAP.MIB. 7667 Error 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. SNMP Trap: hpevtFabricMaxBrokenLinks - 7667 in HPIFPTRAP.MIB. 7669 Error This cell did not get the XBC Global Semaphore. Probable Cause: XBC write or read failure. Recommended Action: check XBC, check link, check CC SNMP Trap: hpevtXbcSemaphoreTakeoverFailed - 7669 in HPIFPTRAP.MIB. Platform Agent 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
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127

Event Description
Event Severity
Event ID
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 SNMP Trap:
hpevtFabricGetNeighborInfoError - 7652 in HPIFPTRAP.MIB.
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. SNMP Trap:
hpevtXbcRoutingErrorState - 7653 in HPIFPTRAP.MIB.
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. SNMP Trap: hpevtNoNvmErrLogSpace
- 7655 in HPIFPTRAP.MIB.
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
SNMP Trap: hpevtXbcPortError - 7657 in HPIFPTRAP.MIB.
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. SNMP Trap:
hpevtXbcPortRouteAround - 7658 in HPIFPTRAP.MIB.
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 SNMP Trap: hpevtXbcUnexpectedState - 7660 in
HPIFPTRAP.MIB.
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 SNMP Trap: hpevtXbcRoutingStateTimeout -
7661 in HPIFPTRAP.MIB.
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. SNMP Trap: hpevtXbcNeighborPortNotRoutable - 7663
in HPIFPTRAP.MIB.
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 SNMP Trap: hpevtFabricCcToXbcError
- 7664 in HPIFPTRAP.MIB.
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. SNMP Trap: hpevtFabricRouteXbcError -
7666 in HPIFPTRAP.MIB.
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. SNMP Trap:
hpevtFabricMaxBrokenLinks - 7667 in HPIFPTRAP.MIB.
Error
7667
This cell did not get the XBC Global Semaphore. Probable Cause: XBC write or read
failure. Recommended Action: check XBC, check link, check CC SNMP Trap:
hpevtXbcSemaphoreTakeoverFailed - 7669 in HPIFPTRAP.MIB.
Error
7669
Platform Agent Events
39