HP Integrity rx4640 Windows Integrity Management Agents Reference - Page 83

Reset the BMC. Update BMC FW. Contact your, Analyze the Deadlock Recovery logs like MCA

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

5812 5813 5823 5824 5825 5827 5832 5833 5834 5836 5837 5853 5896 6002 6074 6146 6180 6730 6795 7652 7653 7655 7657 It is likely the GSP is not present or the device specified is not present. Solve these problems and try again. Most likely cause is a bad cpu module connection on the cell board. Replace the cell board. panic occurred fault/panic panic, mca, or INIT path: attempt to write out the dump is complete No action required A PAL call made by SFW has failed. Reboot if necessary, if problem persists contact your HP representative for support. BMC failed. Reset the BMC. Update BMC FW. Contact your HP representative to check the BMC. SAL failure. Reset the system. Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. BMC failure. Reset the BMC. Update BMC FW. Contact your HP representative concerning the BMC. SAL failure. Reboot the system. Update SFW. If problem persists, contact HP support to troubleshoot the problem. SAL is not in ADMIN or USER mode. Reboot the system. Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. panic path forward progress Coherency controller (CC) resources are deadlocked and the CC is resetting the cell. Analyze the Deadlock Recovery logs (like MCA logs) to determine the cause of the failure. Poorly seated DIMM Reseat DIMM Incorrect loading of the DIMMs on the cell Install the DIMMs in the correct order. DIMMs are installed in ranks of DIMMs , starting with DIMM 0A, 0B, etc. Subsequent ranks are loaded in ascending order , i.e., rank 1, 2, 3, 4, 5, 6 and 7. At start of memory refresh, timing out waiting Contact HP Support personnel to troubleshoot for ready bit to be set the problem Memory extender and baseboard are incompatible Contact HP support to troubleshoot the problem There is a fabric topology mismatch with XBC in Contact HP Support personnel to analyze the cell, complex. XBC flex cables, system backplane Loss of Lockstep Reset Defective XBC link Defective XBC Check XBC link connections Reset the system backplane Contact HP Support personnel to troubleshoot problem Another cell already attempted routing for the Check for hardware failure: flex cables, crossbar XBC and found an error. chip, etc. The error event will not be logged. A port was landmined so it had to be routed around. Check flex cables Platform Events - Table 2 (Windows System Log Event ID, Cause, Recommended Action) 83

  • 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
It is likely the GSP is not present or the device
specified is not present. Solve these problems and
try again.
5812
Most likely cause is a bad cpu module connection
on the cell board. Replace the cell board.
5813
panic occurred
5823
fault/panic
5824
No action required
panic, mca, or INIT path: attempt to write out the
dump is complete
5825
Reboot if necessary, if problem persists contact
your HP representative for support.
A PAL call made by SFW has failed.
5827
Reset the BMC. Update BMC FW. Contact your
HP representative to check the BMC.
BMC failed.
5832
Reset the system. Upgrade system firmware. If
problem persists, contact HP support to
troubleshoot the problem.
SAL failure.
5833
Reset the BMC. Update BMC FW. Contact your
HP representative concerning the BMC.
BMC failure.
5834
Reboot the system. Update SFW. If problem
persists, contact HP support to troubleshoot the
problem.
SAL failure.
5836
Reboot the system. Upgrade system firmware. If
problem persists, contact HP support to
troubleshoot the problem.
SAL is not in ADMIN or USER mode.
5837
panic path forward progress
5853
Analyze the Deadlock Recovery logs (like MCA
logs) to determine the cause of the failure.
Coherency controller (CC) resources are
deadlocked and the CC is resetting the cell.
5896
Reseat DIMM
Poorly seated DIMM
6002
Install the DIMMs in the correct order. DIMMs
are installed in ranks of DIMMs , starting with
DIMM 0A, 0B, etc. Subsequent ranks are loaded
in ascending order , i.e., rank 1, 2, 3, 4, 5, 6 and 7.
Incorrect loading of the DIMMs on the cell
6074
Contact HP Support personnel to troubleshoot
the problem
At start of memory refresh, timing out waiting
for ready bit to be set
6146
Contact HP support to troubleshoot the problem
Memory extender and baseboard are
incompatible
6180
Contact HP Support personnel to analyze the cell,
XBC flex cables, system backplane
There is a fabric topology mismatch with XBC in
complex.
6730
Reset
Loss of Lockstep
6795
Check XBC link connections Reset the system
backplane Contact HP Support personnel to
troubleshoot problem
Defective XBC link Defective XBC
7652
Check for hardware failure: flex cables, crossbar
chip, etc.
Another cell already attempted routing for the
XBC and found an error.
7653
The error event will not be logged.
7655
Check flex cables
A port was landmined so it had to be routed
around.
7657
Platform Events – Table 2 (Windows System Log Event ID, Cause, Recommended Action)
83