HP Integrity rx4640 Windows Integrity Management Agents Reference - Page 104

Fabric Access Failure. Could not write to the XBC., Hardware problem. Possible bad XBC or Cell

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 104 highlights

9742 9744 9745 9746 9750 9751 9753 9754 9755 9768 9769 9774 Cells exist in both cabinets, but one of the cabinets has no cells powered on. If a 2 cabinet configuration is desired, shutdown any active partitions and power off both cabinets and then power them both on, including at least 1 cell in each cabinet. (Note: it is possible to get this event ID and have both cabinets powered on. In this event, no action is required.) An error occurred while collecting the PCI error No action can be taken. The result is some or all logs PCI error logs will be unavailable. An error occurred while collecting the SBA error No action can be taken. The result is some or all logs SBA error logs will be unavailable. Hardware problem. Possible bad XBC or Cell Controller Check for hardware failures. Reset backplane to re-initialize fabric. You will receive this message if the system is correcting a lot of ECC single bit errors. It may mean that the module is about to fail, or environmental conditions in the server are causing more errors than usual. This event message will be generated for one of the following conditions 1000 single-bit errors on the same address in a 48 hour time period. 50 single-bit errors on the same DIMM (not the same address) in a 24 hour time period. 100 single-bit If you receive this message, contact your support errors on the same DIMM (not the same address) provider to determine if a predictive repair in a 1 week time period. should be made. You will receive this message if the system is correcting a lot of ECC single bit errors. It may mean that the module is about to fail, or environmental conditions in the server are causing more errors than usual. This event message will be generated for one of the following conditions 1500 single-bit errors on the same address in a 72 hour time period. 120 single-bit errors on the same DIMM (not the same address) in a 24 hour time period. 130 single-bit If you receive this message, contact your support errors on the same DIMM (not the same address) provider to determine if a predictive repair in a 1 week time period. should be made. An unexpected but random error occurred. Reboot the system. There is a problem with the system bus. Contact your HP representative to check the system bus. An unexpected but random error occurred. Reboot the system. An unexpected but random error occurred. Reboot the system. There is a problem with the system bus. Contact your HP representative to check the system bus. Check the system forward progress log (available from the Management Processor) for additional information about this problem. FW tried to read the first boot token and received AC power cycle the system . If this doesn't work, a failure. contact HP support. other cell is an IA cell replace IA cell with PA cell or reconfigure partition to exclude the IA cell. Fabric Access Failure. Could not write to the XBC. This could indicate a hardware problem. Include the FABRIC_ERRORS_XBC_CLEAR_WR_ADDR Contact HP Support personnel to analyze the event log and its data in any reports. fabric. 104 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
Cells exist in both cabinets, but one of the cabinets
has no cells powered on. If a 2 cabinet
configuration is desired, shutdown any active
partitions and power off both cabinets and then
power them both on, including at least 1 cell in
each cabinet. (Note: it is possible to get this event
ID and have both cabinets powered on. In this
event, no action is required.)
9742
No action can be taken. The result is some or all
PCI error logs will be unavailable.
An error occurred while collecting the PCI error
logs
9744
No action can be taken. The result is some or all
SBA error logs will be unavailable.
An error occurred while collecting the SBA error
logs
9745
Check for hardware failures. Reset backplane to
re-initialize fabric.
Hardware problem. Possible bad XBC or Cell
Controller
9746
If you receive this message, contact your support
provider to determine if a predictive repair
should be made.
You will receive this message if the system is
correcting a lot of ECC single bit errors. It may
mean that the module is about to fail, or
environmental conditions in the server are
causing more errors than usual. This event
message will be generated for one of the
following conditions 1000 single-bit errors on the
same address in a 48 hour time period. 50
single-bit errors on the same DIMM (not the same
address) in a 24 hour time period. 100 single-bit
errors on the same DIMM (not the same address)
in a 1 week time period.
9750
If you receive this message, contact your support
provider to determine if a predictive repair
should be made.
You will receive this message if the system is
correcting a lot of ECC single bit errors. It may
mean that the module is about to fail, or
environmental conditions in the server are
causing more errors than usual. This event
message will be generated for one of the
following conditions 1500 single-bit errors on the
same address in a 72 hour time period. 120
single-bit errors on the same DIMM (not the same
address) in a 24 hour time period. 130 single-bit
errors on the same DIMM (not the same address)
in a 1 week time period.
9751
An unexpected but random error occurred.
Reboot the system. There is a problem with the
system bus. Contact your HP representative to
check the system bus.
9753
Reboot the system.
An unexpected but random error occurred.
9754
An unexpected but random error occurred.
Reboot the system. There is a problem with the
system bus. Contact your HP representative to
check the system bus. Check the system forward
progress log (available from the Management
Processor) for additional information about this
problem.
9755
AC power cycle the system . If this doesn't work,
contact HP support.
FW tried to read the first boot token and received
a failure.
9768
replace IA cell with PA cell or reconfigure
partition to exclude the IA cell.
other cell is an IA cell
9769
Contact HP Support personnel to analyze the
fabric.
Fabric Access Failure. Could not write to the XBC.
This could indicate a hardware problem. Include
the FABRIC_ERRORS_XBC_CLEAR_WR_ADDR
event log and its data in any reports.
9774
104
Management Agents Event Tables