HP Integrity rx4640 Windows Integrity Management Agents Reference - Page 84

explain the failure. Check XBC. Check Link/Flex, An I2C Communication failure with

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

Page 84 highlights

7658 7660 7661 7663 7664 7666 7667 7669 7671 7673 7674 7684 7685 7686 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 During routing, when a XBC to XBC port is found backplane(s) involved. If the suspect XBC port to be in error, or was previously marked in error, uses the hardwire link built into the system it is routed around. This chassis code indicates backplane, replace the system backplane that which XBC port was routed around. involved. An XBC is indicating a port failure Validate all of the cells connectivity to the PD Check the XBC chips seating reset the system replace either cells/system backplane An XBC is indicating a port failure Validate all of the cells connectivity to the PD Check the XBC chips seating reset the system replace either cells/system backplane An XBC port is not healthy. Check for hardware failure: flex cables, crossbar chips, etc. The CC to XBC link is not operational. Reset the cell Reset the system backplane Contact HP Support personnel to troubleshoot problem A failure was encountered while performing remote routing on an XBC, most likely due to a Check for hardware failure: CC, XBC to CC link, problem with the system backplane or local cell. flex cables, crossbar chip, etc. Port status indicated that two or more ports on Check for hardware failure: flex cables, crossbar a XBC had errors. chip, etc. XBC write or read failure. check XBC, check link, check CC 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 Cannot takeover an XBC semaphore that has been owner of the SM4 was unable to release it. Look held for a long time. for fabric problems on the backplane. XBC Key Contention. Hardware Failure Look for other chassis codes that indicate XBC Key contention. Check XBC. Check Links/Flex Cables XBC Key Contention. Hardware Failure Look for additional chassis codes that would explain the failure. Check XBC. Check Link/Flex Cables 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. 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. 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. 84 Management Agents 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
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
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 backplane
An XBC is indicating a port failure
7660
Validate all of the cells connectivity to the PD
Check the XBC chips seating reset the system
replace either cells/system backplane
An XBC is indicating a port failure
7661
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 problem
The 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 CC
XBC 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
Cables
XBC Key Contention. Hardware Failure
7673
Look for additional chassis codes that would
explain the failure. Check XBC. Check Link/Flex
Cables
XBC Key Contention. Hardware Failure
7674
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