HP Integrity rx4640 Windows Integrity Management Agents Reference - Page 80

A Prototype CPU is installed., Replace CPU with a production CPU.

Page 80 highlights

5728 5729 5730 5731 5732 5733 5734 5735 5737 5738 5740 5741 5742 5743 5744 5745 5746 5747 5749 5750 5751 Check for other errors in the system first. Unable to properly initialize a system firmware Invalidate NVM and retry to boot. Get the latest node firmware release. This is likely to be a symptom of an earlier problem, or the system is out of malloc space. Contact system firmware team. This is usually a symptom of an earlier problem. Check to be sure the pdh node was initialized into the tree correctly. This is usually due to a memory allocation problem. Verify that sram is usable and there is memory available. May be out of malloc space or a previous tree error prevented this from being successful. Check for earlier errors. Possibly out of memory or an earlier error left the tree in an unusable state. Installed processors are not of compatible models Replace processors with compatible ones if all or families processors are to be used. Processors with different cache sizes are installed Replace processors with compatible ones if all in the system. processors are to be used. The monarch processor was not the lowest stepping processor installed within the cell. No action is required. FW takes action automatically. To avoid this event, be sure that the monarch processor is the lowest stepping of processor in the system. The monarch processor has a stepping that is greater than a slave processor installed in the system. No action is needed. If problem persists, update System FW or contact your HP representative for support. FSB speed faster than the capabilities of the processors If multiple CPU's report this issue, check the BMC. If only one reports this issue, replace the CPU. If problem persists, contact HP support. An early version of CPU or a bad info ROM. Reboot. If problem persists contact your HP representative for support. PAL_A has not been executed. Contact your HP representative for support. PAL_B has not been executed. Contact your HP representative for support. A Prototype CPU is installed. Replace CPU with a production CPU. A watchdog timer has expired and determined that a monarch is dead. Reboot, if problem persists, replace CPU. A CPU failed supplemental selftests. Replace the offending CPU. Possibly bad link or cell connection. Reset partition, and check hardware associated with event data. Firmware error Reset cell The communication with the system ID is lost Reset the BMC using the 'rb' command from the MP. If this doesn't work (or no MP available), unplug power from the system for 10 seconds and try rebooting the system. BMC failure Unplug power from the system for 10 seconds and try rebooting the system. 80 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

Check for other errors in the system first.
Invalidate NVM and retry to boot. Get the latest
firmware release.
Unable to properly initialize a system firmware
node
5728
Contact system firmware team.
This is likely to be a symptom of an earlier
problem, or the system is out of malloc space.
5729
This is usually a symptom of an earlier problem.
Check to be sure the pdh node was initialized
into the tree correctly.
5730
This is usually due to a memory allocation
problem. Verify that sram is usable and there is
memory available.
5731
May be out of malloc space or a previous tree
error prevented this from being successful. Check
for earlier errors.
5732
Possibly out of memory or an earlier error left
the tree in an unusable state.
5733
Replace processors with compatible ones if all
processors are to be used.
Installed processors are not of compatible models
or families
5734
Replace processors with compatible ones if all
processors are to be used.
Processors with different cache sizes are installed
in the system.
5735
No action is required. FW takes action
automatically. To avoid this event, be sure that
the monarch processor is the lowest stepping of
processor in the system.
The monarch processor was not the lowest
stepping processor installed within the cell.
5737
No action is needed. If problem persists, update
System FW or contact your HP representative for
support.
The monarch processor has a stepping that is
greater than a slave processor installed in the
system.
5738
If multiple CPU's report this issue, check the
BMC. If only one reports this issue, replace the
CPU. If problem persists, contact HP support.
FSB speed faster than the capabilities of the
processors
5740
Reboot. If problem persists contact your HP
representative for support.
An early version of CPU or a bad info ROM.
5741
Contact your HP representative for support.
PAL_A has not been executed.
5742
Contact your HP representative for support.
PAL_B has not been executed.
5743
Replace CPU with a production CPU.
A Prototype CPU is installed.
5744
Reboot, if problem persists, replace CPU.
A watchdog timer has expired and determined
that a monarch is dead.
5745
A CPU failed supplemental selftests. Replace the
offending CPU.
5746
Reset partition, and check hardware associated
with event data.
Possibly bad link or cell connection.
5747
Reset cell
Firmware error
5749
Reset the BMC using the 'rb' command from the
MP. If this doesn't work (or no MP available),
unplug power from the system for 10 seconds
and try rebooting the system.
The communication with the system ID is lost
5750
Unplug power from the system for 10 seconds
and try rebooting the system.
BMC failure
5751
80
Management Agents Event Tables