0010002 |
Microprocessor not supported. |
- (Trained service technician) Complete the following steps:
- Remove microprocessor 2 and restart the server (see Removing a microprocessor and heat sink and Installing a microprocessor and heat sink).
- If the problem remains, remove microprocessor 1 and install microprocessor
2 in the connector for microprocessor 1; then, restart the server
(see Removing a microprocessor and heat sink and Installing a microprocessor and heat sink).
- If the problem goes away, microprocessor 1 might have failed;
replace the microprocessor.
- (Trained service technician) Replace the following components
one at a time in the order shown, restarting the server each time:
|
0011000 |
Invalid microprocessor type |
- Update the server firmware (see Updating firmware and device drivers.
- (Trained service technician) Remove and replace the affected microprocessor
with a supported type (see Removing a microprocessor and heat sink and Installing a microprocessor and heat sink). Use light
path diagnostic LEDs to determine the affected processor (Light path diagnostics LEDs).
|
0011002 |
Microprocessor mismatch. |
- Run the Setup utility and view the microprocessor information
to compare the installed microprocessor specifications.
- (Trained service technician) Remove and replace one of the microprocessors
so that they both match (see Removing a microprocessor and heat sink and Installing a microprocessor and heat sink).
|
0011004 |
Microprocessor failed BIST. |
- Update the server firmware (see Updating firmware and device drivers).
- (Trained service technician) Complete the following steps:
- Reseat the microprocessor (see Removing a microprocessor and heat sink and Installing a microprocessor and heat sink).
- Replace the following components one at a time in the order shown,
restarting the server each time:
- Microprocessor (see Removing a microprocessor and heat sink and Installing a microprocessor and heat sink).
- System board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
001100A |
Microcode update failed |
- Update the server firmware (see Updating firmware and device drivers).
- (Trained service technician only) Replace the microprocessor (see Removing a microprocessor and heat sink and Installing a microprocessor and heat sink).
|
0050001 |
DIMM disabled. |
- Check the system event log for any memory errors that might be
related to the specified DIMM and resolve those errors.
Note: If
the system event log is full, new events will not be posted to the
log. You can clear the system event log through the Setup Utility
(see Using the Setup utility). Select System Event Logs and
then select Clear System Event Log.
- Enable the DIMM connector (slot) for the specified
DIMM using the Setup utility (see Using the Setup utility) or the Advanced Settings
Utility (see Using the Advanced Settings Utility (ASU)).
To enable
the DIMM connector using the Setup utility, select System Settings and
then select Memory.
- Reseat the affected DIMM (see Removing a DIMM - BladeCenter HX5 and Installing a DIMM - BladeCenter HX5) and enable the
DIMM connector (see step 2).
- Save the settings and exit from the Setup utility.
|
0051003 |
Uncorrectable runtime DIMM error |
- Refer to TIP H21455 for minimum code level.
- Check the IBM support website for an applicable retain tip or
firmware update that applies to this memory error.
- Swap one of the DIMMs with a DIMM of the same size and type from
another channel (see Installing a DIMM - BladeCenter HX5. For example, if
a problem occurs on DIMM 1 and DIMM 4, swap DIMM 1 with a similar
DIMM in slot 9.
- Enable all affected DIMMs using the Setup utility.
- If the failure remains on the original DIMM slots, replace the
DIMM that was not moved. If the failure follows the DIMM that was
moved, replace the DIMM that was swapped.
- If the problem occurs on the same DIMM connector, check the DIMM
connector. If the connector is damaged, (Trained service technician
only) replace the system-board assembly (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
0051006 |
DIMM mismatch detected. |
Make sure that the DIMMs match and have been installed
in the correct order (see Installing a DIMM - BladeCenter HX5). If you receive
this error code for a blade server configuration that includes an IBM MAX5 expansion
blade, multiple DIMMs might have been disabled. After you replace
the mismatched DIMM, make sure that all DIMMs have been enabled using
the Setup utility (see Using the Setup utility) or using the Advanced Settings
Utility (see Using the Advanced Settings Utility (ASU)).
|
0051009 |
No memory detected. |
- Make sure that the server contains the correct number of DIMMs,
in the correct order (see Installing a DIMM - BladeCenter HX5).
- Reseat the DIMMs (see Removing a DIMM - BladeCenter HX5 and Installing a DIMM - BladeCenter HX5).
- Turn off the blade server. Then turn on the blade server and immediately
turn it off (before POST completes) four times, using either the power
button on the front of the blade server or the advanced management
module web interface.
Note: Make sure that you turn off the blade
server immediately after starting it. Turning on the blade server
and immediately turning it off four times will cause UEFI to be start
using default settings the next time the server is started.
If
the problem is resolved, run the Setup utility, select Load Default
Settings, and save the settings to recover the server firmware.
- Remove the battery and reinstall the battery to
clear CMOS memory and NVRAM. The real time clock will also be reset.
- Remove all DIMM pairs and make sure that a pair of DIMMs that
are known to be operational are installed in DIMM connectors 1 and
4). Then, restart the blade server.
If the problem is resolved,
continue adding DIMM pairs back to the system (see Installing a DIMM - BladeCenter HX5), restarting the
blade server each time a DIMM pair is added. Note: If the
blade server fails to start after adding a DIMM pair, replace one
of the DIMMs with a DIMM of the same size and type (see Removing a DIMM - BladeCenter HX5 and Installing a DIMM - BladeCenter HX5).
If the issue is resolved, continue to add additional DIMM pairs. If
the problem remains, replace the second DIMM of the pair with the
original removed DIMM. If the problem remains, continue to Step 6.
- (Trained service technician only). If there are two processors
installed in the system, swap microprocessors (see Removing a microprocessor and heat sink and Installing a microprocessor and heat sink).
- (Trained service technician only) Replace the system board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
005100A |
No usable memory detected. |
- Make sure that the server contains the correct number of DIMMs,
in the correct order (see Installing a DIMM - BladeCenter HX5).
- Reseat the DIMMs (see Removing a DIMM - BladeCenter HX5 and Installing a DIMM - BladeCenter HX5).
- Turn off the blade server. Then turn on the blade server and immediately
turn it off (before POST completes) four times, using either the power
button on the front of the blade server or the advanced management
module web interface.
Note: Make sure that you turn off the blade
server immediately after starting it. Turning on the blade server
and immediately turning it off four times will cause UEFI to be start
using default settings the next time the server is started.
If
the problem is resolved, run the Setup utility, select Load Default
Settings, and save the settings to recover the server firmware.
- Remove the battery and reinstall the battery to
clear CMOS memory and NVRAM. The real time clock will also be reset.
- Remove all DIMM pairs and make sure that a pair of DIMMs that
are known to be operational are installed in DIMM connectors 1 and
4). Then, restart the blade server.
If the problem is resolved,
continue adding DIMM pairs back to the system (see Installing a DIMM - BladeCenter HX5), restarting the
blade server each time a DIMM pair is added. Note: If the
blade server fails to start after adding a DIMM pair, replace one
of the DIMMs with a DIMM of the same size and type (see Removing a DIMM - BladeCenter HX5 and Installing a DIMM - BladeCenter HX5).
If the issue is resolved, continue to add additional DIMM pairs.
If the problem remains, replace the second DIMM of the pair with the
original removed DIMM. If the problem remains, continue to Step 6.
- (Trained service technician only). If there are two processors
installed in the system, swap microprocessors (see Removing a microprocessor and heat sink and Installing a microprocessor and heat sink).
- (Trained service technician only) Replace the system board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
0058001 |
Memory predictive failure analysis (PFA) threshold
exceeded. |
- Refer to TIP H21455 for minimum code level.
- Check the IBM support website for an applicable retain tip or
firmware update that applies to this memory error.
- Swap the affected DIMMs (as indicated by the error LEDs on the
system board or the event logs) to a different memory channel or microprocessor
(see Installing a DIMM - BladeCenter HX5 for
memory population sequence).
- If the error still occurs on the same DIMM, replace the affected
DIMM (as indicated by the error LEDs on the system board or the event
logs).
- If the problem occurs on the same DIMM connector, check the DIMM
connector. If the connector is damaged, (trained service technician
only) replace the system-board assembly (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
0058007 |
DIMM population is unsupported |
- Make sure that the server contains the correct number of DIMMs,
in the correct order (see Installing a DIMM - BladeCenter HX5).
- Check the system event log for any memory errors that might be
related to specified DIMM pair and resolve those errors.
Note: If
the system event log is full, new events will not be posted to the
log. You can clear the system event log through the Setup Utility
(see Using the Setup utility). Select System Event Logs and
then select Clear System Event Log.
- Reseat the DIMMs (see Removing a DIMM - BladeCenter HX5 and Installing a DIMM - BladeCenter HX5) and restart the
blade server.
- Remove the specified DIMM pair and replace the DIMM pair with
an identical pair of known good DIMMs, and then restart the server.
Repeat as necessary. If the failures continue, go to step 5.
- (Trained service technician only) Replace the system
board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
0058008 |
DIMM failed memory test |
- Refer to TIP H21455 for minimum code level.
- Check the IBM support website for an applicable retain tip or
firmware update that applies to this memory error.
- Swap the affected DIMMs (as indicated by the error LEDs on the
system board or the event logs) to a different memory channel or microprocessor
(see Installing a DIMM - BladeCenter HX5 for
memory population sequence).
- Enable all affected DIMMs using the Setup utility.
- If the failure remains on the original DIMM slots, replace the
DIMM that was not moved. If the failure follows the DIMM that was
moved, replace the DIMM that was swapped.
- If the problem occurs on the same DIMM connector, check the DIMM
connector. If the connector is damaged, (Trained service technician
only) replace the system-board assembly (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
00580A1 |
Invalid DIMM population for mirroring mode. |
- Make sure that the server contains the correct number of DIMMs,
in the correct order (see Installing a DIMM - BladeCenter HX5).
- Check the system event log for any memory errors that might be
related to the specified DIMM and resolve those errors.
Note: If
the system event log is full, new events will not be posted to the
log. You can clear the system event log through the Setup Utility
(see Using the Setup utility). Select System Event Logs and
then select Clear System Event Log.
- Reseat the DIMMs (see Removing a DIMM - BladeCenter HX5 and Installing a DIMM - BladeCenter HX5) and restart the
blade server.
- Remove the specified DIMM pair and replace the DIMM pair with
an identical pair of known good DIMMs, and then restart the server.
Repeat as necessary. If the failures continue, go to step 5.
- (Trained service technician only) Replace the
system board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
00580A4 |
Memory population changed. |
Information only. Memory has been added, moved,
or changed. |
00580A5 |
Mirror failover complete |
Information only. Memory redundancy has been lost.
Check the system-event log for uncorrected DIMM failure events. |
00580B0 |
Memory SMI link failure |
- Check the IBM support website for an applicable retain tip or
firmware update that applies to this memory error.
- Check the DIMM connector and the associated microprocessor connector
(make sure you use the microprocessor installation and removal tool).
- (Trained service technician only) If the connector is damaged,
replace the system board assembly (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
00580B1 |
Memory SMI lane fail down |
Information only. |
0068002 |
CMOS battery cleared. |
- Reseat the battery.
- Clear the CMOS memory (see System-board switches).
- Replace the following components one at a time in the order shown,
restarting the server each time:
- Battery (see Removing the battery and Installing the battery).
- (Trained service technician only) System board. See Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5.
|
2011001 |
PCI-X SERR |
- Use light path diagnostic LEDs to determine whether an I/O fault
LED is lit (Light path diagnostics LEDs).
If it is, resolve the problem.
- Check the system-event log to determine which I/O expansion cards
are affected.
- Reseat all affected I/O-expansion cards.
- If you have recently updated the device drivers for the affected
I/O-expansion cards, revert to a previous device driver.
- Update the firmware and device drivers for the PCI device.
- Remove the I/O-expansion cards from the system board.
- Replace the following components one at a time in the order shown,
restarting the server each time:
- The I/O-expansion cards
- (Trained service technician only) System board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
2018001 |
PCI Express uncorrectable error |
- Turn off the blade server. Then turn on the blade
server and immediately turn it off (before POST completes) four times,
using either the power button on the front of the blade server or
the advanced management module web interface.
Note: Make sure that
you turn off the blade server immediately after starting it. Turning
on the blade server and immediately turning it off four times will
cause UEFI to be start using default settings.
- Remove the battery and reinstall the battery to
clear CMOS memory and NVRAM. The real time clock will also be reset.
- Remove any recently installed hardware.
- Update the server firmware through the advanced management module
web interface.
|
2018002 |
Option ROM resource allocation failure. |
Informational message that some devices might
not be initialized.
- Run the Setup utility (see Using the Setup utility). Select Start Options from
the menu and modify the boot sequence so that you change the load
order of the optional-device ROM code.
- Run the Setup utility (see Using the Setup utility) and disable unused resource
to make more space available:
- Select Start Options
- Select Planar Ethernet (PXE/DHCP) to disable the integrated
Ethernet controller ROM.
- Select Advanced Functions, followed by PCI Bus Control,
and then PCI ROM Control Execution to disable the ROM of the
adapters in the PCI slots.
- Select Devices and I/O Ports to disable any of the integrated
devices.
- Replace the following components one at a time in the order shown,
restarting the server each time:
- Expansion cards (see Removing an I/O expansion card and Installing an I/O expansion card).
- (Trained service technician only) System board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
3xx0007 (xx can
be 00-19) |
Firmware fault detected, system halted. |
- Recover the server firmware to the latest level. Run the Setup
utility, select Load Default Settings, and save the settings
to recover the server firmware.
- Undo any recent configuration changes, or clear CMOS memory to
restore the settings to the default values.
- Remove any recently installed hardware.
|
3038003 |
Firmware corrupted. |
- Revert to a previous version of the firmware for the blade server.
- If the blade server will not start, switch to the backup UEFI
image. Set switch 7 to the on position. See System-board switches for the location
of switch 7.
- Restart the server until you see F1 Setup or the Boot Device selection.
- Power down the server.
- (Trained service technician only) Replace the system board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
3048005 |
Booted secondary (backup) server firmware image. |
Information only. The backup switch was used to
boot the secondary bank. |
3048006 |
Booted secondary (backup) UEFI image because of
automatic boot failure recovery |
- Run the Setup utility (see Using the Setup utility). Select Load Default Settings and
save the settings to recover the server firmware.
- Remove the blade server from the chassis.
- Install the blade server into the chassis and turn on the blade
server.
|
305000A |
Real time clock (RTC) date/time is incorrect |
- Run the Setup utility (see Using the Setup utility) to adjust the date and time.
Then, restart the blade server.
- Reseat the battery.
- Replace the following components one at a time in the order shown,
restarting the blade server each time:
- Battery
- (Trained service technician only) System board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
3058001 |
System configuration is not valid |
- Run the Setup utility (see Using the Setup utility). Select Load Default Settings and
save the settings.
- Reseat the following components one at a time in the order shown,
restarting the blade server each time:
- Battery
- Failing device. If the device is a field replaceable unit (FRU),
it must be replaced by a trained service technician.
- Replace the following components one at a time in the order shown,
restarting the blade server each time:
- Battery
- Failing device. If the device is a field replaceable unit (FRU),
it must be replaced by a trained service technician.
- (Trained service technician only) System board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5)
|
3058004 |
Three boot failures |
- Undo any recent system changes, such as new settings or newly
installed devices.
- Check the advanced management module event log for any power related
issues and resolve them. You can access the event log through the
advanced management module web interface. For more information see the Advanced Management Module Installation
and User's Guide. the ../com.ibm.bladecenter.advmgtmod.doc/adv_man_mod_printable_doc.html.
- Remove all hardware that is not listed on the ServerProven website.
- Run the Setup utility (see Using the Setup utility). Select Load Default Settings and
save the settings. Then, restart the blade server.
|
3108007 |
System configuration restored to default settings |
Information only. This is message is usually associated
with the CMOS battery clear event. |
3138002 |
Boot configuration error |
- Run the Setup utility and remove any recent changes made to the
settings (see Using the Setup utility).
- Run the Setup utility (see Using the Setup utility). Select Load Default Settings and
save the settings.
|
3008000 |
IMM communication failure. |
- Remove the blade server from the chassis for 30 seconds and then
install the blade server into the chassis (see Removing the blade server from the BladeCenter chassis and Installing a blade server in a BladeCenter chassis).
- Restart the blade server.
- Update the blade server firmware (see Updating firmware and device drivers).
- (Trained service technician only) Replace the system board (see Removing the system-board assembly - BladeCenter HX5 and Installing the system-board assembly - BladeCenter HX5).
|
3008002 |
Error updating system configuration to IMM |
- Remove the blade server from the chassis for 30 seconds and then
install the blade server into the chassis (see Removing the blade server from the BladeCenter chassis and Installing a blade server in a BladeCenter chassis).
- Restart the blade server.
- Run the Setup utility (see Using the Setup utility). Select Load Default Settings and
save the settings. Then, restart the blade server.
- Update the server firmware (see Updating firmware and device drivers).
|
3008003 |
Error retrieving system configuration from IMM |
- Remove the blade server from the chassis for 30 seconds and then
install the blade server into the chassis (see Removing the blade server from the BladeCenter chassis and Installing a blade server in a BladeCenter chassis).
- Restart the blade server.
- Run the Setup utility (see Using the Setup utility). Select Load Default Settings and
save the settings. Then, restart the blade server.
- Update the server firmware (see Updating firmware and device drivers).
|
3008004 |
IMM system event log full. |
- Run the Setup utility.
- Select System Event Logs.
- Select Clear System Event Log.
- Restart the server.
|
3818001 |
Core Root of Trust Measurement (CRTM) update failed |
- Revert to a previous version of the firmware for the blade server.
- If the blade server will not start, switch to the backup UEFI
image. Set switch 7 to the on position. See System-board switches for the location
of switch 7.
- Update the firmware for the server. Make sure that you are using
the latest firmware from http://www.ibm.com/support/
fixcentral/systemx/groupView? query.productGroup=ibm%2FBladeCenter.
- Set switch 7 to the off position. See System-board switches for the location
of switch 7.
|
3818002 |
Core Root of Trust Measurement (CRTM) update aborted |
- Revert to a previous version of the firmware for the blade server.
- If the blade server will not start, switch to the backup UEFI
image. Set switch 7 to the on position. See System-board switches for the location
of switch 7.
- Update the firmware for the server. Make sure that you are using
the latest firmware from http://www.ibm.com/support/
fixcentral/systemx/groupView? query.productGroup=ibm%2FBladeCenter.
- Set switch 7 to the off position. See System-board switches for the location
of switch 7.
|
3818003 |
Core Root of Trust Measurement (CRTM) flash lock
failed |
- Revert to a previous version of the firmware for the blade server.
- If the blade server will not start, switch to the backup UEFI
image. Set switch 7 to the on position. See System-board switches for the location
of switch 7.
- Update the firmware for the server. Make sure that you are using
the latest firmware from http://www.ibm.com/support/
fixcentral/systemx/groupView? query.productGroup=ibm%2FBladeCenter.
- Set switch 7 to the off position. See System-board switches for the location
of switch 7.
|
3818004 |
Core Root of Trust Measurement (CRTM) system error |
- Revert to a previous version of the firmware for the blade server.
- If the blade server will not start, switch to the backup UEFI
image. Set switch 7 to the on position. See System-board switches for the location
of switch 7.
- Update the firmware for the server. Make sure that you are using
the latest firmware from http://www.ibm.com/support/
fixcentral/systemx/groupView? query.productGroup=ibm%2FBladeCenter.
- Set switch 7 to the off position. See System-board switches for the location
of switch 7.
|
3818005 |
Current Bank Core Root of Trust Measurement (CRTM)
capsule signature invalid |
- Revert to a previous version of the firmware for the blade server.
- If the blade server will not start, switch to the backup UEFI
image. Set switch 7 to the on position. See System-board switches for the location
of switch 7.
- Update the firmware for the server. Make sure that you are using
the latest firmware from http://www.ibm.com/support/
fixcentral/systemx/groupView? query.productGroup=ibm%2FBladeCenter.
- Set switch 7 to the off position. See System-board switches for the location
of switch 7.
|
3818006 |
Opposite bank CRTM capsule signature invalid |
- Revert to a previous version of the firmware for the blade server.
- If the blade server will not start, switch to the backup UEFI
image. Set switch 7 to the on position. See System-board switches for the location
of switch 7.
- Update the firmware for the server. Make sure that you are using
the latest firmware from http://www.ibm.com/support/
fixcentral/systemx/groupView? query.productGroup=ibm%2FBladeCenter.
- Set switch 7 to the off position. See System-board switches for the location
of switch 7.
|
3818007 |
CRTM update capsule signature invalid |
- Revert to a previous version of the firmware for the blade server.
- If the blade server will not start, switch to the backup UEFI
image. Set switch 7 to the on position. See System-board switches for the location
of switch 7.
- Update the firmware for the server. Make sure that you are using
the latest firmware from http://www.ibm.com/support/
fixcentral/systemx/groupView? query.productGroup=ibm%2FBladeCenter.
- Set switch 7 to the off position. See System-board switches for the location
of switch 7.
|
3828004 |
AEM power capping disabled |
- Check the settings and the event logs.
- Make sure that the Active Energy Manager feature is enabled in
the Setup utility. Select .
- Update the UEFI firmware.
- Update the IMM firmware.
|