HP Insight Management WBEM Provider Events Reference Guide

Table #2 — Event ID numbers 7,000 through 15,738
Event DescriptionEvent
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. WBEM EventID: 595. WBEM
ProviderName: FPL_IndicationProvider.Warning7652
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.Error7653
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.Warning7655
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.Error7657
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.Error7658
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.Warning7660
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.Warning7661
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.Error7663
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.Error7664
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.Error7666
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.Error7667
This cell did not get the XBC Global Semaphore. Probable Cause: XBC write or read
failure. Recommended Action: check XBC, check link, check CC. WBEM EventID:
606. WBEM ProviderName: FPL_IndicationProvider.Error7669
40 WBEM Provider Event Tables