Windows Integrity Management Agents Reference

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.
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.7658
Validate all of the cells connectivity to the PD
Check the XBC chips seating reset the system
replace either cells/system backplaneAn XBC is indicating a port failure7660
Validate all of the cells connectivity to the PD
Check the XBC chips seating reset the system
replace either cells/system backplaneAn XBC is indicating a port failure7661
Check for hardware failure: flex cables, crossbar
chips, etc.An XBC port is not healthy.7663
Reset the cell Reset the system backplane Contact
HP Support personnel to troubleshoot problemThe CC to XBC link is not operational.7664
Check for hardware failure: CC, XBC to CC link,
flex cables, crossbar chip, etc.
A failure was encountered while performing
remote routing on an XBC, most likely due to a
problem with the system backplane or local cell.7666
Check for hardware failure: flex cables, crossbar
chip, etc.
Port status indicated that two or more ports on
a XBC had errors.7667
check XBC, check link, check CCXBC write or read failure.7669
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.
Cannot takeover an XBC semaphore that has been
held for a long time.7671
Look for other chassis codes that indicate XBC
Key contention. Check XBC. Check Links/Flex
CablesXBC Key Contention. Hardware Failure7673
Look for additional chassis codes that would
explain the failure. Check XBC. Check Link/Flex
CablesXBC Key Contention. Hardware Failure7674
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.7684
A software error was detected and is being
logged. The internal data is connected to the
location and module where the error occurred.
The Forward Progress Log will receive additional
(lower alert level) event entries with more data
associated with this event.7685
An I2C Communication failure with the
Baseboard Management Controller was detected.
Without I2C communication, the system cannot
be powered on/off or reset. Check the I2C
communication via the 'SR' command or the 'PS'
command. If it is indeed down, look for hardware
reasons. It's possible resetting the Management
Processor firmware ("XD" command option 'r')
or completely cycling AC power of the system
will restore the communication.7686
84 Management Agents Event Tables