-
I.11002 [I.11002] A processor
mismatch has been detected between one or more processors in the system.
Explanation: One
or More Mismatched Processors Detected
- Severity
- Info
- User Response
- Complete the following steps:
- This message could occur with messages about other processor configuration
problems. Resolve those messages first.
- If the problem persists, ensure that matching processors are installed
(i.e., matching option part numbers, etc)
- Verify that the processors are installed in the correct sockets.
If not, correct that problem.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this processor error.
- Replace mismatching processor. Inspect the processor socket and
replace the system board first if the socket is damaged.
- Related links
-
-
I.18005 [I.18005] A discrepancy
has been detected in the number of cores reported by one or more processor
packages within the system.
Explanation: Processors have mismatched
number of cores
- Severity
- Info
- User Response
- Complete the following steps:
- If this is a newly installed option, ensure that matching processors
are installed in the correct processor sockets.
- Check the IBM support site for an applicable service bulletin
that applies to this processor error.
- Replace the processor. Inspect the processor socket and replace
the system board first if the socket is damaged.
- Related links
-
-
I.18006 [I.18006] A mismatch
between the maximum allowed QPI link speed has been detected for one
or more processor packages.
Explanation: Processors have mismatched
QPI Speed
- Severity
- Info
- User Response
- Complete the following steps:
- If this is a newly installed option, ensure that matching processors
are installed in the correct processor sockets.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this processor error.
- Replace the processor. Inspect the processor socket and replace
the system board first if the socket is damaged.
- Related links
-
-
I.18007 [I.18007] A power
segment mismatch has been detected for one or more processor packages.
Explanation: Processors
have mismatched Power Segments
- Severity
- Info
- User Response
- Complete the following steps:
- Processors installed do not have the same power requirements
- Ensure that all Processors have matching power requirements (such
as 65, 95, or 130 Watts)
- If power requirements match, check the IBM support site for an
applicable service bulletin or firmware update that applies to this
processor error.
- Replace the processor. Inspect the processor socket and replace
the system board first if the socket is damaged
- Related links
-
-
I.18008 [I.18008] Currently,
there is no additional information for this event.
Explanation: Processors
have mismatched Internal DDR3 Frequency
- Severity
- Info
- User Response
- Complete the following steps:
- Verify that matching DIMMs are installed in the correct population
sequence. Correct any configuration issues found.
- Replace the associated processor. Inspect the processor socket
and replace the system board first if the socket is damaged
- Related links
-
-
I.18009 [I.18009] A core
speed mismatch has been detected for one or more processor packages.
Explanation: Processors
have mismatched Core Speed
- Severity
- Info
- User Response
- Complete the following steps:
- Verify that matching processors are installed in the correct
processor sockets. Correct any mismatch issues found.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this processor error.
- Replace the processor. Inspect the processor socket and replace
the system board first if the socket is damaged.
- Related links
-
-
I.1800A [I.1800A] A mismatch
has been detected between the speed at which a QPI link has trained
between two or more processor packages.
Explanation: Processors
have mismatched Bus Speed
- Severity
- Info
- User Response
- Complete the following steps:
- Verify that the processor is a valid option that is listed as
a Server Proven device for this system. If not, remove the Processor
and install one listed on the Server Proven website.
- Verify that matching processors are installed in the correct
processor sockets. Correct any mismatch found.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this processor error.
- Replace the processor. Inspect the processor socket and replace
the system board first if the socket is damaged
- Related links
-
-
I.1800B [I.1800B] A cache
size mismatch has been detected for one or more processor packages.
Explanation: Processors
have one or more cache levels with mismatched size
- Severity
- Info
- User Response
- Complete the following steps:
- Verify that matching processors are installed in the correct
processor sockets. Correct any mismatch found.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this processor error.
- Replace the system board.
- Related links
-
-
I.1800C [I.1800C] A cache
type mismatch has been detected for one or more processor packages.
Explanation: Processors
have one or more cache levels with mismatched type
- Severity
- Info
- User Response
- Complete the following steps:
- Verify that matching processors are installed in the correct
processor sockets.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this processor error.
- Replace the system board.
- Related links
-
-
I.1800D [I.1800D] A cache
associativity mismatch has been detected for one or more processor
packages.
Explanation: Processors have one or more cache levels
with mismatched associativity
- Severity
- Info
- User Response
- Complete the following steps:
- Verify that matching processors are installed in the correct
processor sockets.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this processor error.
- Replace the system board.
- Related links
-
-
I.1800E [I.1800E] A processor
model mismatch has been detected for one or more processor packages.
Explanation: Processors
have mismatched Model Number
- Severity
- Info
- User Response
- Complete the following steps:
- Verify that matching processors are installed in the correct
processor sockets.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this Processor error.
- Replace the system board.
- Related links
-
-
I.1800F [I.1800F] A processor
family mismatch has been detected for one or more processor packages.
Explanation: Processors
have mismatched Family
- Severity
- Info
- User Response
- Complete the following steps:
- Verify that matching processors are installed in the correct
processor sockets.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this processor error.
- Replace the system board.
- Related links
-
-
I.18010 [I.18010] A processor
stepping mismatch has been detected for one or more processor packages.
Explanation: Processors
of the same model have mismatched Stepping ID
- Severity
- Info
- User Response
- Complete the following steps:
- Verify that matching processors are installed in the correct
processor sockets.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this processor error.
- Replace the system board.
- Related links
-
-
I.2018002 [I.2018002]
The device found at Bus % Device % Function % could not be configured
due to resource constraints. The Vendor ID for the device is % and
the Device ID is %.
Explanation: OUT_OF_RESOURCES (PCI Option ROM)
- Severity
- Info
- User Response
- Complete the following steps:
- If this PCIe device and/or any attached cables were recently
installed, moved, serviced or upgraded, reseat the adapter and any
attached cables.
- Check the IBM support site for any applicable service bulletin
or UEFI or adapter firmware update that applies to this error.
NOTE:
It may be necessary to disable unused option ROMs from UEFI F1 setup
or ASU or using adapter manufacturer utilities so that adapter firmware
can be updated.
- Move the adapter to a different slot. If a slot is not available
or error recurs, replace the adapter.
- If the adapter was moved to a different slot and the error did
not recur, verify that this is not a system limitation. Then replace
the system board. Also, if this is not the initial installation
and the error persists after adapter replacement, replace the system
board.
- Related links
-
-
I.2018003 [I.2018003]
A bad option ROM checksum was detected for the device found at Bus
% Device % Function %. The Vendor ID for the device is % and the Device
ID is %.
Explanation: ROM CHECKSUM ERROR
- Severity
- Info
- User Response
- Complete the following steps:
- If this PCIe device and/or any attached cables were recently
installed, moved, serviced or upgraded, reseat the adapter and any
attached cables.
- Move the adapter to a different system slot, if available.
- Check the IBM support site for any applicable service bulletin
or UEFI or adapter firmware update that applies to this error.
NOTE:
It may be necessary to configure slot to Gen1 or to use special utility
software so that adapter firmware can be upgraded. Gen1/Gen2 settings
can be configured via F1 Setup -> System Settings ->
Devices and I/O Ports -> PCIe Gen1/Gen2/Gen3 Speed Selection, or
the ASU Utility.
- Replace the adapter.
- Related links
-
-
I.3048005 [I.3048005]
UEFI has booted from the backup flash bank.
Explanation: Booting Backup
UEFI Image
- Severity
- Info
- User Response
- Complete the following steps:
Return
the system to primary bank.
- Related links
-
-
I.3808004 [I.3808004]
The IMM System Event log (SEL) is full.
Explanation: IPMI System
Event Log is Full
- Severity
- Info
- User Response
- Complete the following steps:
- Use the IMM Web Interface to clear the event log.
- If IMM communication is unavailable, use the Setup Utility to
access the System Event Logs Menu and choose Clear IMM System Event
Log and Restart Server.
- Related links
-
-
I.3818001 [I.3818001]
The firmware image capsule signature for the currently booted flash
bank is invalid.
Explanation: Current Bank CRTM Capsule Update Signature
Invalid
- Severity
- Info
- User Response
- Complete the following steps:
- Reboot the system. Will come up on backup UEFI image. Update
the primary UEFI image.
- If error does not persist no additional recovery action is required.
- If error persists, or boot is unsuccessful, replace the system
board.
- Related links
-
-
I.3818002 [I.3818002]
The firmware image capsule signature for the non-booted flash bank
is invalid.
Explanation: Opposite Bank CRTM Capsule Update Signature
Invalid
- Severity
- Info
- User Response
- Complete the following steps:
- Update the backup UEFI image.
- If error does not persist, no additional recovery action is required.
- If error persists, or boot is unsuccessful, replace the system
board.
- Related links
-
-
I.3818003 [I.3818003]
The CRTM flash driver could not lock the secure flash region.
Explanation: CRTM
Could not lock secure flash region
- Severity
- Info
- User Response
- Complete the following steps:
- If system failed to boot successfully, DC cycle the system.
- If system boots to F1 setup, update the UEFI image and reset
bank to primary (if required). If the system boots without error,
recovery is complete and no additional action is required.
- If system fails to boot, or if the firmware update attempt fails,
replace the system board.
- Related links
-
-
I.3868000 [I.3868000]
BOFM: System reset performed to reset adapters.
Explanation: BOFM:
System reset performed to reset adapters
- Severity
- Info
- User Response
- Complete the following steps:
Information
only; no action is required.
-
I.3868003 [I.3868003]
BOFM: Configuration to large for compatibility mode.
Explanation: BOFM:
Configuration too large for compatibility mode
- Severity
- Info
- User Response
- Complete the following steps:
Information
only; no action is required.
-
I.58015 [I.58015] Memory
spare copy initiated.
Explanation: Spare Copy Started
- Severity
- Info
- User Response
- Complete the following steps:
Information
only; no action is required.
-
I.580A4 [I.580A4] Memory
population change detected.
Explanation: DIMM Population Change
Detected
- Severity
- Info
- User Response
- Complete the following steps:
Check
system event log for uncorrected DIMM failures and replace those DIMMs.
- Related links
-
-
I.580A5 [I.580A5] Mirror
Fail-over complete. DIMM number % has failed over to to the mirrored
copy.
Explanation: DIMM Mirror Fail-over Detected
- Severity
- Info
- User Response
- Complete the following steps:
Check
the system-event log for uncorrected DIMM failures and replace those
DIMMs.
- Related links
-
-
I.580A6 [I.580A6] Memory
spare copy has completed successfully.
Explanation: Spare Copy Complete
- Severity
- Info
- User Response
- Complete the following steps:
Check
system log for related DIMM failures and replace those DIMMs.
- Related links
-
-
S.1100C [S.1100C] An
uncorrectable error has been detected on processor %.
Explanation: Uncorrectable
processor error detected
- Severity
- Error
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Reboot the system. If problem persists, contact Support.
-
S.2011001 [S.2011001]
An Uncorrected PCIe Error has Occurred at Bus % Device % Function
%. The Vendor ID for the device is % and the Device ID is %.
Explanation: PCI
SERR Detected
- Severity
- Error
- User Response
- Complete the following steps:
- If this compute node and/or any attached cables were recently
installed, moved, serviced or upgraded,
- Reseat the adapter and any attached cables.
- Reload the device driver.
- If device is not recognized, reconfiguring slot to Gen1 or Gen2
may be required. Gen1/Gen2 settings can be configured via F1 Setup
-> System Settings -> Devices and I/O Ports ->
PCIe Gen1/Gen2/Gen3 Speed Selection, or the ASU Utility.
- Check the IBM support site for an applicable device driver, firmware
update, or other information that applies to this error. Load the
new device driver and install any required firmware
updates.
- If the problem persists, remove the adapter. If system reboots
successfully without the adapter, replace that adapter.
- Replace the processor.
- Related links
-
-
S.2018001 [S.2018001]
An Uncorrected PCIe Error has Occurred at Bus % Device % Function
%. The Vendor ID for the device is % and the Device ID is %.
Explanation: PCIe
Uncorrected Error Detected
- Severity
- Error
- User Response
- Complete the following steps:
- If this compute node and/or any attached cables were recently
installed, moved, serviced or upgraded:
- Reseat the adapter and any attached cables.
- Reload the device driver.
- If device is not recognized, reconfiguring slot to Gen1 or Gen2
may be required. Gen1/Gen2 settings can be configured via F1 Setup
-> System Settings -> Devices and I/O Ports ->
PCIe Gen1/Gen2/Gen3 Speed Selection, or the ASU Utility.
- Check the IBM support site for an applicable device driver, firmware
update, or other information that applies to this error. Load the
new device driver and install any required firmware
updates.
- If the problem persists, remove the adapter. If the system reboots
successfully without the adapter, replace that adapter.
- Replace the processor.
- Related links
-
-
S.3020007 [S.3020007]
A firmware fault has been detected in the UEFI image.
Explanation: Internal
UEFI Firmware Fault Detected, System halted
- Severity
- Error
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the UEFI image.
- Replace the system board.
- Related links
-
-
S.3028002 [S.3028002]
Boot permission timeout detected.
Explanation: Boot Permission Negotiation
Timeout
- Severity
- Error
- User Response
- Complete the following steps:
- Check CMM/IMM logs for communication errors and resolve.
- Reseat the system.
- If problem persists, contact Support.
-
S.3030007 [S.3030007]
A firmware fault has been detected in the UEFI image.
Explanation: Internal
UEFI Firmware Fault Detected, System halted
- Severity
- Error
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the UEFI image.
- Replace the system board.
- Related links
-
-
S.3040007 [S.3040007]
A firmware fault has been detected in the UEFI image.
Explanation: Internal
UEFI Firmware Fault Detected, System halted
- Severity
- Error
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the UEFI image.
- Replace the system board.
- Related links
-
-
S.3050007 [S.3050007]
A firmware fault has been detected in the UEFI image.
Explanation: Internal
UEFI Firmware Fault Detected, System halted
- Severity
- Error
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the UEFI image.
- Replace the system board.
- Related links
-
-
S.3058004 [S.3058004]
A Three Strike boot failure has occurred. The system has booted with
default UEFI settings.
Explanation: POST failure has occurred! System
booted with default settings.
- Severity
- Error
- User Response
- Complete the following steps:
- This event resets UEFI to the default settings for the next boot.
If successful, the Setup Utility is displayed. The original UEFI
settings are still present.
- If you did not intentionally trigger the reboots, check logs
for probable cause.
- Undo recent system changes (settings or devices added). If there
were no recent system changes, remove all options, and then remove
the CMOS battery for 30 seconds to clear CMOS contents.
Verify that the system boots. Then, re-install the options one at
a time to locate the problem.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the UEFI firmware.
- Remove and re-install CMOS battery for 30 seconds to clear CMOS
contents
- Replace the system board.
- Related links
-
-
S.3060007 [S.3060007]
A firmware fault has been detected in the UEFI image.
Explanation: Internal
UEFI Firmware Fault Detected, System halted
- Severity
- Error
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the UEFI image.
- Replace the system board.
- Related links
-
-
S.3070007 [S.3070007]
A firmware fault has been detected in the UEFI image.
Explanation: Internal
UEFI Firmware Fault Detected, System halted
- Severity
- Error
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the UEFI image.
- Replace the system board.
- Related links
-
-
S.3108007 [S.3108007
] The default system settings have been restored.
Explanation: System
Configuration Restored to Defaults
- Severity
- Error
- User Response
- Complete the following steps:
Check
the IBM support site for an applicable service bulletin or firmware
update that applies to this error.
- Related links
-
-
S.3818004 [S.3818004]
The CRTM flash driver could not successfully flash the staging area.
A failure occurred.
Explanation: CRTM Update Failed
- Severity
- Error
- User Response
- Complete the following steps:
- Continue booting the system. If the system does not reset, manually
reset the system.
- If the error is not reported on the subsequent boot, no additional
recovery action is required.
- If the error persists, continue booting system and update the
UEFI image.
- Replace the system board.
- Related links
-
-
S.3818007 [S.3818007]
The firmware image capsules for both flash banks could not be verified.
Explanation: CRTM
image capsule could not be verified
- Severity
- Error
- User Response
- Complete the following steps:
- If system failed to boot successfully, DC cycle system.
- If system boots to F1 setup, update the UEFI image and reset
bank to primary (if required). If the system boots without error,
recovery is complete and no additional action is required.
- If system fails to boot, or if the firmware update attempt fails,
replace the system board.
- Related links
-
-
S.51003 [S.51003] An
uncorrectable memory error was detected in DIMM slot % on rank %.
Explanation: [S.51003]
An uncorrectable memory error was detected on processor % channel
%. The failing DIMM within the channel could not be determined.[S.51003]
An uncorrectable memory error has been detected during POST. Fatal
Memory Error Occurred
- Severity
- Error
- User Response
- Complete the following steps:
- Prior to replacing memory DIMM, refer to TIP H212154 for minimum code level.
- If the compute node has recently been installed, moved, serviced,
or upgraded, verify that the DIMM is properly seated and visually
verify that there is no foreign material in any DIMM
connector on that memory channel. If either of these conditions is
found, correct and retry with the same DIMM. (Note:
The event Log might contain a recent 00580A4 event denoting detected
change in DIMM population that could be related to this problem.)
- If no problem is observed on the DIMM connectors or the problem
persists, replace the DIMM identified by LightPath and/or event log
entry.
- If problem recurs on the same DIMM connector, replace the other
DIMMs on the same memory channel.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this memory error.
- If problem recurs on the same DIMM connector, inspect connector
for damage. If found, replace the system board.
- Replace the affected Processor.
- Replace system board.
- Related links
-
-
S.51006 [S.51006] A memory
mismatch has been detected. Please verify that the memory configuration
is valid.
Explanation: One or More Mismatched DIMMs Detected
- Severity
- Error
- User Response
- Complete the following steps:
- Could follow an uncorrectable memory error or failed memory test.
Check the log and service that event first. DIMMs disabled by other
errors or actions could cause this event.
- Verify that the DIMMs are installed in the correct population
sequence.
- Disable memory mirroring and sparing. If this action eliminates
the mismatch, check the IBM Support site for information related to
this problem.
- Update UEFI firmware.
- Replace the DIMM
- Replace the processor.
- Related links
-
-
S.51009 [S.51009] No
system memory has been detected.
Explanation: No Memory Detected
- Severity
- Error
- User Response
- Complete the following steps:
- If any memory errors are logged other than this one, take actions
indicated for those codes first.
- If no other memory diagnostic codes appear in the logs, verify
that all DIMM connectors are enabled using the Setup utility or the
Advanced Settings Utility (ASU).
- If the problem remains, shut down and remove node from chassis
and physically verify that one or more DIMMs are installed and that
all DIMMs are installed in the correct population sequence.
- If DIMMs are present and properly installed, check for any lit
DIMM-connector LEDs, and if found, reseat those DIMMs.
- Reinstall node in chassis, power on node, then check logs for
memory diagnostic codes.
- If the problem remains, replace the processor.
- If the problem remains, replace the system board.
- Related links
-
-
S.58008 [S.58008] A DIMM
has failed the POST memory test.
Explanation: DIMM Failed Memory
Test
- Severity
- Error
- User Response
- Complete the following steps:
- Prior to replacing memory DIMM, refer to TIP H212154 for minimum code level.
- You must AC-cycle the system to re-enable the affected DIMM connector
or re-enable manually using the Setup utility.
- If the compute node has been recently installed, serviced, moved,
or upgraded, check to ensure that DIMMs are firmly seated and that
no foreign material can be seen in the DIMM connector.
If either condition is observed, correct and retry with the same
DIMM. (Note: The event Log might contain a recent 00580A4
event denoting detected change in DIMM population that could be related
to this problem.)
- If problem persists, replace the DIMM identified by LightPath
and/or event log entry.
- If problem recurs on the same DIMM connector, swap the other
DIMMs on the same memory channel across channels one at a time to
a different memory channel or processor. If problem follows
a moved DIMM to a different memory channel, replace that DIMM.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this memory error.
- If problem stays with the original DIMM connector, re-inspect
DIMM connector for foreign material and remove, if found. If connector
is damaged, replace system board.
- Remove the affected processor and inspect the processor socket
pins for damaged or mis-aligned pins. If damage is found, or this
is an upgrade processor, replace the system board. If
there are multiple processors, swap them to move affected procesor
to another processor socket and retry. If problem follows the
affected processor (or there is only one processor), replace
the affected processor.
- Replace the system board.
- Related links
-
-
S.68005 [S.68005] An
error has been detected by the the IIO core logic on Bus %. The Global
Fatal Error Status register contains %. The Global Non-Fatal Error
Status register contains %. Please check error logs for the presence
of additional downstream device error data.
Explanation: Critical IOH-PCI
Error
- Severity
- Error
- User Response
- Complete the following steps:
- Check the log for a separate error related to an associated PCIe
device and resolve that error.
- Check the IBM support site for an applicable service bulletin
or firmware update for the system or adapter that applies to this
error.
- Replace the system board.
- Related links
-
-
S.680B8 [S.680B8] Internal
QPI Link Failure Detected.
Explanation: Internal QPI Link Failure Detected
- Severity
- Error
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Inspect the processor socket for foreign debris or damage. If
debris is found, remove the debris.
- If error recurs, or socket damage is found, replace the system
board.
- Related links
-
-
S.680B9 [S.680B9] External
QPI Link Failure Detected.
Explanation: External QPI Link Failure Detected
- Severity
- Error
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Inspect the processor socket for foreign debris or damage. If
debris is found, remove the debris.
- If error recurs, or socket damage is found, replace the system
board.
- Related links
-
-
W.11004 [W.11004] A processor
within the system has failed the BIST.
Explanation: Processor Self
Test Failure Detected
- Severity
- Warning
- User Response
- Complete the following steps:
- If the processor or firmware was just updated, check the IBM
support site for an applicable service bulletin or firmware update
that applies to this processor error.
- If there are multiple Processors, swap Processors to move affected
processor to another processor socket and retry. If problem follows
the affected processor, or this is a single processor
system, replace the processor. Inspect the processor socket on each
processor removal and replace system board first if
the processor socket is damaged or mis-aligned pins are found.
- Replace the system board.
- Related links
-
-
W.3048006 [W.3048006]
UEFI has booted from the backup flash bank due to an Automatic Boot
Recovery (ABR) event.
Explanation: Automated Boot Recovery, Booting
Backup UEFI Image
- Severity
- Warning
- User Response
- Complete the following steps:
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the primary UEFI image.
- Replace the system board.
- Related links
-
-
W.305000A [W.305000A]
An invalid date and time have been detected.
Explanation: RTC Date and
Time Incorrect
- Severity
- Warning
- User Response
- Complete the following steps:
- Check IMM/chassis event log. This event should immediately precede
0068002 error. Resolve that event or any other battery related errors.
- Use F1 Setup to reset date and time. If problem returns after
a system reset, replace CMOS battery.
- If problem persists then check the IBM support site for an applicable
service bulletin or firmware update that applies to this error.
- Replace the system board.
- Related links
-
-
W.3058009 [W.3058009]
DRIVER HEALTH PROTOCOL: Missing Configuraiton. Requires Change Settings
From F1.
Explanation: DRIVER HEALTH PROTOCOL: Missing Configuration.
Requires Change Settings From F1
- Severity
- Warning
- User Response
- Complete the following steps:
- Go to the Setup Utility (System Settings -> Settings ->
Driver Health Status List) and find a driver/controller reporting
Configuration Required status.
- Search for the driver menu from System Settings and change settings
appropriately.
- Save settings and restart system.
- Related links
-
-
W.305800A [W.305800A]
DRIVER HEALTH PROTOCOL: Reports 'Failed' Status Controller.
Explanation: DRIVER
HEALTH PROTOCOL: Reports 'Failed' Status Controller
- Severity
- Warning
- User Response
- Complete the following steps:
- Reboot the system.
- If problem persists, switch to backup UEFI or update the current
UEFI image.
- Replace the system board.
- Related links
-
-
W.305800B [W.305800B]
DRIVER HEALTH PROTOCOL: Reports 'Reboot' Required Controller.
Explanation: DRIVER
HEALTH PROTOCOL: Reports 'Reboot' Required Controller
- Severity
- Warning
- User Response
- Complete the following steps:
- No action required. The system will reboot at the end of POST.
- If the problem persists, switch to the backup UEFI image or update
the current UEFI image.
- Replace the system board.
- Related links
-
-
W.305800C [W.305800C]
DRIVER HEALTH PROTOCOL: Reports 'System Shutdown' Required Controller.
Explanation: DRIVER
HEALTH PROTOCOL: Reports 'System Shutdown' Required Controller
- Severity
- Warning
- User Response
- Complete the following steps:
- Reboot the system.
- If problem persists, switch to the backup UEFI image or update
the current UEFI image.
- Replace system board.
- Related links
-
-
W.305800D [W.305800D]
DRIVER HEALTH PROTOCOL: Disconnect Controller Failed. Requires 'Reboot'.
Explanation: DRIVER
HEALTH PROTOCOL: Disconnect Controller Failed. Requires 'Reboot'
- Severity
- Warning
- User Response
- Complete the following steps:
- Reboot the system to reconnect the controller.
- If problem persists, switch to the backup UEFI image or update
the current UEFI image.
- Replace the system board.
- Related links
-
-
W.305800E [W.305800E]
DRIVER HEALTH PROTOCOL: Reports Invalid Health Status Driver.
Explanation: DRIVER
HEALTH PROTOCOL: Reports Invalid Health Status Driver
- Severity
- Warning
- User Response
- Complete the following steps:
- Reboot the system.
- If problem persists, switch to the backup UEFI image or update
the current UEFI image.
- Replace the system board.
- Related links
-
-
W.3808000 [W.3808000]
An IMM communication failure has occurred.
Explanation: IMM Communication
Failure
- Severity
- Warning
- User Response
- Complete the following steps:
- Reset the IMM from the CMM.
- Use the CMM to remove auxilliary power from the compute node.
This will reboot the compute node.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the UEFI Firmware.
- Replace the system board.
- Related links
-
-
W.3808002 [W.3808002]
An error occurred while saving UEFI settings to the IMM.
Explanation: Error
Updating System Configuration to IMM
- Severity
- Warning
- User Response
- Complete the following steps:
- Use the Setup Utility to verify and save the settings (which
will recover the settings).
- Reset the IMM from the CMM.
- Use CMM to remove auxilliary power from the compute node. This
will reboot the compute node.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the IMM Firmware.
- Remove and re-install CMOS battery for 30 seconds to clear CMOS
contents.
- Replace the system board.
- Related links
-
-
W.3808003 .[W.3808003]
Unable to retrieve the system configuration from the IMM.
Explanation: Error
Retrieving System Configuration from IMM
- Severity
- Warning
- User Response
- Complete the following steps:
- Use the Setup Utility to verify and save the settings (which
will recover the settings).
- Reset the IMM from the CMM.
- Use CMM to remove auxilliary power from the compute node. This
will reboot the compute node.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Update the IMM Firmware.
- Remove and re-install CMOS battery for 30 seconds to clear CMOS
contents.
- Replace the system board.
- Related links
-
-
W.3818005 [W.3818005]
The CRTM flash driver could not successfully flash the staging area.
The update was aborted
Explanation: CRTM Update Aborted
- Severity
- Warning
- User Response
- Complete the following steps:
- Continue booting system. If system does not reset, manually
reset the system.
- If the error is not reported on the subsequent boot, no additional
recovery action is required.
- If the event persists, continue booting system and update the
UEFI image.
- Replace the system board.
- Related links
-
-
W.3868001 [W.3868001]
BOFM: Reset loop avoided - Multiple resets not allowed.
Explanation: BOFM:
Reset loop avoided - Multiple resets not allowed
- Severity
- Warning
- User Response
- Complete the following steps:
- Update all firmware (including adapter firmware) to the latest
levels.
- If problem persists, contact Support.
- Related links
-
-
W.3868002 [W.3868002]
BOFM: Error communicating with the IMM - BOFM may not be deployed
correctly.
Explanation: BOFM: Error communicating with the IMM -
BOFM may not be deployed correctly
- Severity
- Warning
- User Response
- Complete the following steps:
- Update all firmware (including adapter firmware) to the latest
levels.
- If problem persists, contact Support.
- Related links
-
-
W.3938002 [W.3938002]
A boot configuration error has been detected.
Explanation: Boot Configuration
Error
- Severity
- Warning
- User Response
- Complete the following steps:
- F1 Setup -> Save Settings.
- Retry the configuration update.
- Related links
-
-
W.50001 [W.50001] A DIMM
has been disabled due to an error detected during POST.
Explanation: DIMM
Disabled
- Severity
- Warning
- User Response
- Complete the following steps:
- If the DIMM was disabled because of a memory fault, follow the
procedure for that event.
- If no memory fault is recorded in the logs and no DIMM connector
error LEDs are lit, re-enable the DIMM through the Setup utility or
the Advanced Settings Utility (ASU).
- If the problem persists, Power cycle the compute node from the
management console.
- Reset the IMM to default settings.
- Reset UEFI to default settings.
- Update IMM and UEFI firmware.
- Replace the system board.
- Related links
-
-
W.58001 [W.58001] The
PFA Threshold limit (correctable error logging limit) has been exceeded
on DIMM number % at address %. MC5 Status contains % and MC5 Misc
contains %.
Explanation: DIMM PFA Threshold Exceeded
- Severity
- Warning
- User Response
- Complete the following steps:
- Prior to replacing memory DIMM, refer to TIP H212154 for minimum code level.
- If the compute node has recently been installed, moved, serviced,
or upgraded, verify that the DIMM is properly seated and
visually verify that there is no foreign material in any DIMM
connector on that memory channel. If either of these conditions is
found, correct and retry with the same DIMM. (Note:
The event Log might contain a recent 00580A4 event denoting detected
change in DIMM population that could be related to this problem.)
- Check the IBM support site for an applicable firmware update
that applies to this memory error. The release notes will list the
known problems the update addresses.
- If the previous steps do not resolve the problem, at the next
maintenance opportunity, replace the affected DIMM (as indicated by
LightPath and/or failure log entry).
- If PFA re-occurs on the same DIMM connector, swap the other DIMMs
on the same memory channel one at a time to a different memory channel
or processor. If PFA follows a moved DIMM to any DIMM
connector on the different memory channel, replace the moved DIMM.
- Check the IBM support site for an applicable Service Bulletins
(Service bulletins) that applies to this memory error. (Link to IBM
support service bulletins)
- If problem continues to re-occur on the same DIMM connector,
inspect DIMM connector for foreign material and remove, if found.
If connector is damaged, replace system board.
- Remove the affected processor and inspect the processor socket
pins for damaged or mis-aligned pins. If damage is found or the processor
is an upgrade part, replace the system board.
- Replace affected processor.
- Replace the system board.
- Related links
-
-
W.58007 [W.58007] Invalid
memory configuration (Unsupported DIMM Population) detected. Please
verify memory configuration is valid.
Explanation: Unsupported DIMM
Population
- Severity
- Warning
- User Response
- Complete the following steps:
- This event could follow an uncorrectable memory error or failed
memory test. Check the log and resolve that event first. DIMMs disabled
by other errors or actions could cause this event.
- Ensure that the DIMM connectors are populated in the correct
sequence.
- Related links
-
-
W.580A1 [W.580A1] Invalid
memory configuration for Mirror Mode. Please correct memory configuration.
Explanation: Unsupported
DIMM Population for Mirror Mode
- Severity
- Warning
- User Response
- Complete the following steps:
- If a DIMM connector error LED is lit, resolve the failure.
- Make sure that the DIMM connectors are correctly populated for
mirroring mode.
- Related links
-
-
W.580A2 [W.580A2] Invalid
memory configuration for Sparing Mode. Please correct memory configuration.
Explanation: Unsupported
DIMM Population for Spare Mode
- Severity
- Warning
- User Response
- Complete the following steps:
Make
sure that the DIMM connectors are correctly populated for sparing
mode.
- Related links
-
-
W.68002 [W.68002] A CMOS
battery error has been detected
Explanation: CMOS Battery Fault
- Severity
- Warning
- User Response
- Complete the following steps:
- If the system was recently installed, moved, or serviced, make
sure the battery is properly seated.
- Check the IBM support site for an applicable service bulletin
or firmware update that applies to this error.
- Replace the CMOS battery
- Replace the system board.
- Related links
-