Ibm коды ошибок

Resolving The Problem

The following sections list the error codes and messages that
are generated when a problem is detected:

• POST error
  codes
• IMM2 error
  messages
• DSA
  messages

POST error codes

Follow the suggested actions in the order in which they are
listed in the Action column until the problem is solved.

• If an action step is preceded by “(Trained technician
  only),” that step must be performed only by a trained
  technician.
• Go to the IBM support website at http://www.ibm.com/supportportal/
  to check for technical information, hints, tips, and new device
  drivers or to submit a request for information.

Diagnostic code: I.11002

Message: [I.11002] A processor mismatch has
been detected between one or more processors in the system.

Description: One or More Mismatched Processors
Detected.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverprovencompat/us.
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type

Diagnostic code: W.11004

Message: [W.11004] A processor within the
system has failed the BIST.

Description: Processor Self Test Failure
Detected.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
2. (Trained technician only) If there are more than one
   microprocessor installed, swap the microprocessors. If the problem
   follows the affected microprocessor or there is only one
   microprocessor installed, replace the affected microprocessor.
3. (Trained technician only) Replace the system board.

Diagnostic code: S.1100C

Message: [S.1100C] An uncorrectable error has
been detected on processor %.

Description: Processors have mismatched number
of cores.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. Restart the server.
3. Contact your IBM service representative for support.
   (% = microprocessor number).

Diagnostic code: I.18005

Message: [I.18005] A discrepancy has been
detected in the number of cores reported by one or more processor
packages within the system.

Description: Processors have mismatched number
of cores.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: I.18006

Message: [I.18006] A mismatch between the
maximum allowed QPI link speed has been detected for one or more
processor packages.

Description:Processors have mismatched QPI
Speed.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type

Diagnostic code: I.18007

Message: [I.18007] A power segment mismatch has
been detected for one or more processor packages..

Description: Processors have mismatched Power
Segments.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type

Diagnostic code: I.18008

Message: [I.18008] Currently, there is no
additional information for this event.

Description: Processors have mismatched
Internal DDR3 Frequency.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: I.18009

Message: [I.18009] A core speed mismatch has
been detected for one or more processor packages.

Description: Processors have mismatched Core
Speed.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: I.1800A

Message: [I.1800A] A mismatch has been detected
between the speed at which a QPI link has trained between two or
more processor packages.

Description: Processors have mismatched Bus
Speed.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: I.1800B

Message: [I.1800B] A cache size mismatch has
been detected for one or more processor packages.

Description: Processors have one or more cache
levels with mismatched size.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: I.1800C

Message: [I.1800C] A cache type mismatch has
been detected for one or more processor packages.

Description: Processors have one or more cache
levels with mismatched type.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: I.1800D

Message: [I.1800D] A cache associativity
mismatch has been detected for one or more processor packages.

Description: Processors have one or more cache
levels with mismatched associativity.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: I.1800E

Message: [I.1800E] A processor model mismatch
has been detected for one or more processor packages.

Description: Processors have mismatched Model
Number.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: I.1800F

Message: [I.1800F] A processor family mismatch
has been detected for one or more processor packages.

Description: Processors have mismatched
Family.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: I.18010

Message: [I.18010] A processor stepping
mismatch has been detected for one or more processor packages.

Description: Processors of the same model have
mismatched Stepping ID.

Action:

1. Make sure that the microprocessor is on the ServerProven
   website at
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
   .
2. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
3. (Trained technician only) Remove and replace the affected
   microprocessor (error LED is lit) with a supported type.

Diagnostic code: W.50001

Message: [W.50001] A DIMM has been disabled due
to an error detected during POST.

Description: DIMM Disabled.

Action:

Note: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10 seconds
before restarting the server.

1. Make sure the DIMM is installed correctly.
2. If the DIMM was disabled because of a memory fault, follow the
   suggested actions for that error event.
3. If no memory fault is recorded in the logs and no DIMM
   connector error LED is lit, you can re-enable the DIMM through the
   Setup utility or the Advanced Settings Utility (ASU).

Diagnostic code: S.51003

Message:

[S.51003] An uncorrectable memory error was detected in DIMM
slot % on rank %.
[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.

Description: Fatal Memory Error Occurred.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this problem.
2. If the problem remains, replace the affected DIMMs.
3. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. If the connector contains
   any foreign material or is damaged, replace the system board.
4. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found, replace the system board.
5. (Trained technician only) Replace the affected
   microprocessor.

Diagnostic code: S.51006

Message: [S.51006] A memory mismatch has been
detected. Please verify that the memory configuration is valid.

Description: One or More Mismatched DIMMs
Detected.

Action:

Note: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10 seconds
before restarting the server.Make sure that the DIMMs match and are
installed in the correct sequence

Diagnostic code: S.51009

Message: [S.51009] No system memory has been
detected.

Description: One or More Mismatched DIMMs
Detected.

Action:

1. Make sure that there is at least one DIMM installed in the
   server.
2. If there are no memory fault recorded in the logs and no DIMM
   connector error LEDs are lit, make sure that all DIMM connectors
   are enabled by using the Setup utility or the Advance Settings
   Utility (ASU).
3. Reinstall all DIMMs in the correct population sequence.

Diagnostic code: W.58001

Message: [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 %.

Description: DIMM PFA Threshold Exceeded.

Action:

Note: Each time you install or remove a DIMM,
you must disconnect the server from the power source; then, wait 10
seconds before restarting the server.

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. Swap the affected DIMMs (as indicated by the error LEDs on the
   system board or the event logs) to a different memory channel.
3. If the error still occurs on the same DIMM, replace the
   affected DIMM.
4. If the problem occurs on the same DIMM connector, swap other
   DIMMs (in the same memory channel) to a different memory channel or
   microprocessor . If the problem follows a
   moved DIMM to a different memory channel, replace the affected
   DIMM.
5. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. Remove any foreign
   material on the DIMM connector, if found. If the connector is
   damaged, replace the system board.
6. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found or the microprocessor is an upgrade part, replace
   the system board.
7. (Trained technician only) Replace the affected
   microprocessor.
8. (Trained technician only) Replace the system board.

Diagnostic code: W.58007

Message: [W.58007] Invalid memory configuration
(Unsupported DIMM Population) detected. Please verify memory
configuration is valid.

Description: Unsupported DIMM Population.

Action:

Note: Each time you install or remove a DIMM,
you must disconnect the server from the power source; then, wait 10
seconds before restarting the server.

1. Reseat the DIMMs, and then restart the server.
2. Make sure that the DIMMs are installed in the proper
   sequence

Diagnostic code: S.58008

Message: [S.58008] A DIMM has failed the POST
memory test.

Description: DIMM Failed Memory Test.

Action:

Note: Each time you install or remove a DIMM,
you must disconnect the server from the power source; then, wait 10
seconds before restarting the server.

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. Make sure that the DIMMs are firmly seated and no foreign
   material is found in the DIMM connector. Then, retry with the same
   DIMM.
3. If the problem is related to a DIMM, replace the failing DIMM
   indicated by the error LEDs
4. If the problem occurs on the same DIMM connector, 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.
5. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. If the connector contains
   any foreign material or is damaged, replace the system board.
6. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found, replace the system board.
7. (Trained technician only) Swap the affected microprocessor, if
   there are more than one microprocessor installed. If the problem
   follows the microprocessor, replace the affected
   microprocessor.
8. (Trained technician only) Replace the system board.

Diagnostic code: W.580A1

Message: [W.580A1] Invalid memory configuration
for Mirror Mode. Please correct memory configuration.

Description: Unsupported DIMM Population for
Mirror Mode.

Action:

1. If a DIMM connector error LED is lit on the system board, check
   the event logs and follow the procedure for that event and restart
   the server.
2. Make sure that the DIMMs have been installed in the correct
   sequence for mirrored channel mode.

Diagnostic code: W.580A2

Message: [W.580A2] Invalid memory configuration
for Sparing Mode. Please correct memory configuration.

Description: Unsupported DIMM Population for
Spare Mode.

Action:

Make sure that the DIMMs have been installed in the correct
sequence for rank sparing mode.

Diagnostic code: I.580A4

Message: [W.580A2] Invalid memory configuration
for Sparing Mode. Please correct memory configuration.

Description: DIMM Population Change
Detected.

Action:

Information only. Memory has been added, moved, or changed.

Diagnostic code: I.580A5

Message: [I.580A5] Mirror Fail-over complete.
DIMM number % has failed over to to the mirrored copy.

Description: DIMM Mirror Fail-over
Detected.

Action:

Information only. Memory redundancy has been lost. Check the
event log for uncorrected DIMM failure events.

Diagnostic code: I.580A6

Message: [I.580A6] Memory spare copy has
completed successfully.

Description: Spare Copy Complete.

Action:

Information only. Memory redundancy or spare rank has been lost.
Check the event log for uncorrected DIMM failure events.

Diagnostic code: I.58015

Message: [I.58015] Memory spare copy
initiated.

Description: Spare Copy Started.

Action:

No action; information only.

Diagnostic code: W.68002

Message: [W.68002] A CMOS battery error has
been detected.

Description: CMOS Battery Fault.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. Replace the CMOS battery.
3. (Trained technician only) Replace the system board.

Diagnostic code: S.68005

Message: [S.68005] An error has been detected
by 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.

Description: Critical IOH-PCI Error.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. Replace the following components one at a time in the order
   shown, restarting the server each time:
   1. PCI express adapter.
   2. (Trained technician only) System board.

Diagnostic code: S.680B8

Message: [S.680B8] Internal QPI Link Failure
Detected.

Description: Internal QPI Link Failure
Detected.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. Inspect the microprocessor socket for foreign material, if the
   microprocessor socket contains any foreign material, remove the
   foreign material. If it is found damaged, (trained technician only)
   replace the system board.

Diagnostic code: S.680B9

Message: [S.680B9] External QPI Link Failure
Detected.

Description: External QPI Link Failure
Detected.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. Inspect the microprocessor socket for foreign material, if the
   microprocessor socket contains any foreign material, remove the
   foreign material. If it is found damaged, (trained technician only)
   replace the system board.

Diagnostic code: S.2011001

Message: [S.2011001] An Uncorrected PCIe Error
has Occurred at Bus % Device % Function %. The Vendor ID for the
device is % and the Device ID is %.

Description: PCI SERR Detected.

Action:

1. Check the PCI riser slot LEDs on the system board.
2. Reseat all affected adapters and PCI-X riser-card
   assembly.
3. Update the adapter firmware.
4. Replace the affected adapters and riser cards.
5. (Trained technician only) Replace the system board.

Diagnostic code: S.2018001

Message: [S.2018001] An Uncorrected PCIe Error
has Occurred at Bus % Device % Function %. The Vendor ID for the
device is % and the Device ID is %.

Description: PCIe Uncorrected Error
Detected.

Action:

1. Check the PCI riser slot LEDs on the system board.
2. Reseat all affected adapters and PCI-X riser-card
   assembly.
3. Update the adapter firmware.
4. Replace the affected adapters and riser cards.
5. (Trained technician only) Replace the system board.

Diagnostic code: I.2018002

Message: [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
%.

Description: OUT_OF_RESOURCE (PCI Option
ROM)

Action:

1. Run the Setup utility. Select Startup Options from the menu and
   modify the boot sequence to change the load order of the
   optional-device ROM code.
2. Informational message that some devices might not be
   initialized.
3. See RETAIN tip H197144 for more
   information.

Diagnostic code: I.2018003

Message: [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 %.

Description: ROM CHECKSUM ERROR.

Action:

1. Check the riser-card LEDs.
2. Reseat all affected adapters and riser cards.
3. Move the affected adapter to a different slot.
4. Update the PCI adapter firmware.
5. Replace the affected adapters and riser cards.

Diagnostic code: S.3020007

Message: [S.3020007] A firmware fault has been
detected in the UEFI image.

Description: Internal UEFI Firmware Fault
Detected, System halted.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. Recover the server firmware.
3. (Trained technician only) replace the system board.

Diagnostic code: S.3028002

Message: [S.3028002] Boot permission timeout
detected.

Description: Boot Permission Negotiation
Timeout.

Action:

1. Check the IMM2 error messages for communication errors and
   follow the actions.
2. Restart the server.
3. If the problem remains, contact your IBM service representative
   for support.

Diagnostic code: S.3030007

Message: [S.3030007] A firmware fault has been
detected in the UEFI image.

Description: Internal UEFI Firmware Fault
Detected, System halted.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. Recover the server firmware.
3. (Trained technician only) Replace the system board.

Diagnostic code: S.3040007

Message: [S.3040007] A firmware fault has been
detected in the UEFI image.

Description: Internal UEFI Firmware Fault
Detected, System halted.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. Recover the server firmware.

Diagnostic code: I.3048005

Message: [I.3048005] UEFI has booted from the
backup flash bank.

Description: Booting Backup UEFI Image.

Action:

Information only. Set the JP2 jumper in the backup position
(pins 2 and 3) to allow the server to boot from the backup
UEFI.

Diagnostic code: W.3048006

Message: [W.3048006] UEFI has booted from the
backup flash bank due to an Automatic Boot Recovery (ABR)
event.

Description: Automated Boot Recovery, Booting
Backup UEFI Image.

Action:

1. Run the Setup utility. Select Load Default
   Settings and save the settings.
2. Recover the server firmware.

Diagnostic code: S.3050007

Message: [S.3050007] A firmware fault has been
detected in the UEFI image.

Description: Internal UEFI Firmware Fault
Detected, System halted.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. Recover the server firmware.

Diagnostic code: W.305000A

Message: [W.305000A] An invalid date and time
have been detected.

Description: RTC Date and Time Incorrect.

Action:

1. Run the Setup utility. Select Load Default
   Settings and save the settings.
2. Reseat the battery.
3. Replace the battery.

Diagnostic code: S.3058004

Message: [S.3058004] A Three Strike boot
failure has occurred. The system has booted with default UEFI
settings.

Description: POST failure has occurred! System
booted with default settings.

Action:

1. Undo any recent system changes, such as new settings or newly
   installed devices.
2. Make sure that the server is attached to a reliable power
   source.
3. Remove all hardware that is not listed on the ServerProven Web
   site at http://www.ibm.com/servers/eserver/serverproven/compat/us/.
4. Update the firmware to the latest level.
5. Make sure that the operating system is not corrupted.
6. Run the Setup utility, save the configuration, and then restart
   the server.
7. (Trained technician only) If the problem remains, replace the
   system board.

Diagnostic code: W.3058009

Message: [W.3058009] DRIVER HEALTH PROTOCOL:
Missing Configuraiton. Requires Change Settings From F1.

Description: DRIVER HEALTH PROTOCOL: Missing
Configuration. Requires Change Settings From F1.

Action:

1. Select System Settings →
   Settings → Driver Health Status
   List and find a driver/controller reportingconfiguration
   required status.
2. Search for the driver menu from System
   Settings and change the settings appropriately.
3. Save the settings and restart the system.

Diagnostic code: W.305800A

Message: [W.305800A] DRIVER HEALTH PROTOCOL:
Reports ‘Failed’ Status Controller.

Description: DRIVER HEALTH PROTOCOL: Reports
‘Failed’ Status Controller.

Action:

1. Restart the system.
2. If the problem persists, switch to the backup UEFI image or
   reload the current UEFI image.
3. (Trained technician only) Replace the system board.

Diagnostic code: W.305800B

Message: [W.305800B] DRIVER HEALTH PROTOCOL:
Reports ‘Reboot’ Required Controller.

Description: DRIVER HEALTH PROTOCOL: Reports
‘Reboot’ Required Controller.

Action:

1. No action required. The system will reboot at the end of
   POST.
2. If the problem persists, switch to the backup UEFI image or
   reload the current UEFI image.
3. (Trained technician only) Replace the system board.

Diagnostic code: W.305800C

Message: [W.305800C] DRIVER HEALTH PROTOCOL:
Reports ‘System Shutdown’ Required Controller.

Description: DRIVER HEALTH PROTOCOL: Reports
‘System Shutdown’ Required Controller.

Action:

1. Restart the system.
2. If the problem persists, switch to the backup UEFI image or
   reload the current UEFI image.
3. (Trained technician only) Replace the system board.

Diagnostic code: W.305800D

Message: [W.305800D] DRIVER HEALTH PROTOCOL:
Disconnect Controller Failed. Requires ‘Reboot’.

Description: DRIVER HEALTH PROTOCOL: Reports
‘System Shutdown’ Required Controller.

Action:

1. Restart the system.
2. If the problem persists, switch to the backup UEFI image or
   reload the current UEFI image.
3. (Trained technician only) Replace the system board.

Diagnostic code: W.305800E

Message: [W.305800E] DRIVER HEALTH PROTOCOL:
Reports Invalid Health Status Driver.

Description: DRIVER HEALTH PROTOCOL: Reports
Invalid Health Status Driver.

Action:

1. Restart the system.
2. If the problem persists, switch to the backup UEFI image or
   reload the current UEFI image.
3. (Trained technician only) Replace the system board.

Diagnostic code: S.3060007

Message: [S.3060007] A firmware fault has been
detected in the UEFI image.

Description: Internal UEFI Firmware Fault
Detected, System halted.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. Recover the server firmware.

Diagnostic code: S.3070007

Message: [S.3070007] A firmware fault has been
detected in the UEFI image.

Description: Internal UEFI Firmware Fault
Detected, System halted.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. Recover the server firmware.

Diagnostic code: S.3108007

Message: [S.3108007] The default system
settings have been restored.

Description: System Configuration Restored to
Defaults.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this error.
2. If the settings differ from defaults, run the Setup utility,
   select Load Default Settings, and save the
   settings.

Diagnostic code: W.3808000

Message: [W.3808000] An IMM communication
failure has occurred.

Description: IMM Communication Failure.

Action:

1. Shut down the system and remove the power cords from the server
   for 30 seconds; then, reconnect the server to power and restart
   it.
2. Update the IMM firmware to the latest level.
3. (Trained technician only) Replace the system board.

Diagnostic code: W.3808002

Message: [W.3808002] An error occurred while
saving UEFI settings to the IMM.

Description: Error Updating System
Configuration to IMM.

Action:

1. Run the Setup utility, select Save Settings,
   and restart the server.
2. Update the IMM firmware to the latest level.

Diagnostic code: W.3808003

Message: [I.3808004] The IMM System Event log
(SEL) is full.

Description: Error Retrieving System
Configuration from IMM.

Action:

1. Run the Setup utility, select Save Settings,
   and restart the server.
2. Update the IMM firmware to the latest level.

Diagnostic code: I.3808004

Message: [I.3808004] The IMM System Event log
(SEL) is full.

Description: IPMI System Event Log is Full.

Action:

Run the Setup utility to clear IMM logs and restart the
server

Diagnostic code: I.3818001

Message: [I.3818001] The firmware image capsule
signature for the currently booted flash bank is invalid.

Description: Current Bank CRTM Capsule Update
Signature Invalid.

Action:

1. Run the Setup utility, select Load Default
   Settings, and save the settings.
2. Recover the server firmware.

Diagnostic code: I.3818002

Message: [I.3818002] The firmware image capsule
signature for the non-booted flash bank is invalid.

Description: Current Bank CRTM Capsule Update
Signature Invalid.

Action:

1. Run the Setup utility, select Load Default
   Settings, and save the settings.
2. Recover the server firmware.

Diagnostic code: I.3818003

Message: [I.3818003] The CRTM flash driver
could not lock the secure flash region.

Description: Current Bank CRTM Capsule Update
Signature Invalid.

Action:

1. Run the Setup utility, select Load Default
   Settings, and save the settings.
2. Recover the server firmware.

Diagnostic code: S.3818004

Message: [S.3818004] The CRTM flash driver
could not successfully flash the staging area. A failure
occurred.

Description: CRTM Update Failed.

Action:

1. Run the Setup utility, select Load Default
   Settings, and save the settings.
2. Recover the server firmware.

Diagnostic code: W.3818005

Message: [W.3818005] The CRTM flash driver
could not successfully flash the staging area. The update was
aborted.

Description: CRTM Update Aborted.

Action:

1. Run the Setup utility, select Load Default
   Settings, and save the settings.
2. Recover the server firmware.

Diagnostic code: S.3818007

Message: [S.3818007] The firmware image
capsules for both flash banks could not be verified.

Description: CRTM image capsule could not be
verified.

Action:

1. Run the Setup utility, select Load Default
   Settings, and save the settings.
2. Recover the server firmware.

Diagnostic code: W.3938002

Message: [W.3938002] A boot configuration error
has been detected.

Description: Boot Configuration Error.

Action:

1. Run the Setup utility, select Load Default
   Settings, and save the settings.
2. Recover the server firmware.

Integrated management module II
(IMM2) error messages

• Follow the suggested actions in the order in which they are
  listed in the Action column until the problem is
  solved.
• If an action step is preceded by “(Trained technician
  only),” that step must be performed only by a trained
  technician.

Temperature and fan messages

Event ID: 80010701-0701xxxx

Message: Numeric sensor adapter Ambient Temp
going high (upper non-critical) has asserted.

Severity: Warning

Description: An upper non-critical sensor going
high has asserted.

Action:

1. Reduce the ambient temperature.
2. Check the server airflow. Make sure that nothing is blocking
   the air from coming into or preventing the air from exiting the
   server.

Event ID: 80010701-0c01xxxx

Message: Numeric sensor Ambient Temp going high
(upper non-critical) has asserted.

Severity: Warning

Description: An upper non-critical sensor going
high has asserted.

Action:

1. Reduce the ambient temperature.
2. Check the server airflow. Make sure that nothing is blocking
   the air from coming into or preventing the air from exiting the
   server.

Event ID: 80010901-0701xxxx

Message: Numeric sensor adapter Ambient Temp
going high (upper critical) has asserted.

Severity: Error

Description: An upper critical sensor going
high has asserted.

Action:

1. Reduce the ambient temperature.
2. Check the server airflow. Make sure that nothing is blocking
   the air from coming into or preventing the air from exiting the
   server.

Event ID: 80010901-0c01xxxx

Message: Numeric sensor Ambient Temp going high
(upper critical) has asserted.

Severity: Error

Description: An upper critical sensor going
high has asserted.

Action:

1. Reduce the ambient temperature.
2. Check the server airflow. Make sure that nothing is blocking
   the air from coming into or preventing the air from exiting the
   server.

Event ID: 80010b01-0c01xxxx

Message: Numeric sensor Ambient Temp going high
(upper non-recoverable) has asserted.

Severity: Error

Description: An upper non-recoverable sensor
going high has asserted.

Action:

Check the server airflow. Make sure that nothing is blocking the
air from coming into or preventing the air from exiting the
server.

Event ID: 81010701-0c01xxxx

Message: Numeric sensor Ambient Temp going high
(upper non-critical) has deasserted.

Severity: Info

Description: An upper non-critical sensor going
high has deasserted.

Action:

No action; information only.

Event ID: 81010901-0c01xxxx

Message: Numeric sensor Ambient Temp going high
(upper critical) has deasserted.

Severity: Info

Description: An upper non-critical sensor going
high has deasserted.

Action:

No action; information only.

Event ID: 81010b01-0c01xxxx

Message: Numeric sensor Ambient Temp going high
(upper non-recoverable) has deasserted.

Severity: Info

Description: An upper non-recoverable sensor
going high has deasserted.

Action:

No action; information only.

Event ID:
80010701-1401xxxx
80010701-1402xxxx

Message: Sensor CPU n VR Temp going high (upper
non-critical) has asserted. (n = microprocessor number)

Severity: Warning

Description: An upper non-critical sensor going
high has asserted.

Action:

1. Reduce the ambient temperature.
2. Check the server airflow. Make sure that nothing is blocking
   the air from coming into or preventing the air from exiting the
   server.

Event ID:
80010901-1401xxxx
80010901-1402xxxx

Message: Sensor CPU n VR Temp going high (upper
critical) has asserted. (n = microprocessor number)

Severity: Error

Description: An upper critical sensor going
high has asserted.

Action:

1. Reduce the ambient temperature.
2. Check the server airflow. Make sure that nothing is blocking
   the air from coming into or preventing the air from exiting the
   server.

Event ID:
80010b01-1401xxxx
80010b01-1402xxxx

Message: Sensor CPU n VR Temp going high (upper
non-recoverable) has asserted. (n = microprocessor number)

Severity: Error

Description: An upper non-recoverable sensor
going high has asserted.

Action:

Check the server airflow. Make sure that nothing is blocking the
air from coming into or preventing the air from exiting the
server.

Event ID: 80010701-2d01xxxx

Message: Numeric sensor PCH Temp going high
(upper non-critical) has asserted.

Severity: Warning

Description: An upper non-critical sensor going
high has asserted.

Action:

1. Reduce the ambient temperature.
2. Check the server airflow. Make sure that nothing is blocking
   the air from coming into or preventing the air from exiting the
   server.

Event ID: 80010901-2d01xxxx

Message: Numeric sensor PCH Temp going high
(upper critical) has asserted.

Severity: Error

Description: An upper critical sensor going
high has asserted.

Action:

1. Reduce the ambient temperature.
2. Check the server airflow. Make sure that nothing is blocking
   the air from coming into or preventing the air from exiting the
   server.

Event ID: 80010b01-2d01xxxx

Message: Numeric sensor PCH Temp going high
(upper non-recoverable) has asserted.

Severity: Error

Description: An upper non-recoverable sensor
going high has asserted.

Action:

Check the server airflow. Make sure that nothing is blocking the
air from coming into or preventing the air from exiting the
server.

Event ID: 81010701-2d01xxxx

Message: Numeric sensor PCH Temp going high
(upper non-critical) has deasserted.

Severity: Info

Description: An upper non-critical sensor going
high has deasserted.

Action:

No action; information only.

Event ID: 81010901-2d01xxxx

Message: Numeric sensor PCH Temp going high
(upper critical) has deasserted.

Severity: Info

Description: An upper critical sensor going
high has deasserted.

Action:

No action; information only.

Event ID: 81010b01-2d01xxxx

Message: Numeric sensor PCH Temp going high
(upper non-recoverable) has deasserted.

Severity: Info

Description: An upper non-recoverable sensor
going high has deasserted.

Action:

No action; information only.

Event ID:
80010204-1d01xxxx
80010204-1d02xxxx
80010204-1d03xxxx
80010204-1d04xxxx
80010204-1d05xxxx
80010204-1d06xxxx
80010204-1d07xxxx
80010204-1d08xxxx
80010204-1d09xxxx
80010204-1d0axxxx
80010204-1d0bxxxx
80010204-1d0cxxxx

Message: Numeric sensor Fan n A Tach going low
(lower critical) has asserted. (n = 1Aa, 1Ab, 2Aa, 2Ab, 3Aa,
3Ab)

Severity: Error

Description: A lower critical sensor going low
has asserted.

Action:

1. Reseat the failing fan n, which is indicated by a lit LED near
   the fan connector on the system board.
2. Replace the failing fan.
   (n = fan number)

Event ID:
800b010a-1e81xxxx
800b010a-1e82xxxx
800b010a-1e83xxxx

Message: Cooling Zone n redundancy lost has
asserted. (n = 1,2,3)

Severity: Error

Description: Redundancy lost has asserted.

Action:

1. Make sure that the connectors on fan n are not damaged.
2. Make sure that the fan n connectors on the system board are not
   damaged.
3. Make sure that the fans are correctly installed.
4. Reseat the fans.
5. Replace the failing fan.
   (n = fan number)

Event ID:
800b050a-1e81xxxx
800b050a-1e82xxxx
800b050a-1e83xxxx

Message: Cooling Zone n insufficient resources
has asserted. (n = 1,2,3)

Severity: Error

Description: There is no redundancy and
insufficient to continue operation.

Action:

1. Make sure that the connectors on fan n are not damaged.
2. Make sure that the fan n connectors on the system board are not
   damaged.
3. Make sure that the fans are correctly installed.
4. Reseat the fans.
5. Replace the failing fan.
   (n = fan number)

Event ID:
80070204-0a01xxxx
80070204-0a02xxxx

Message: Sensor PS n Fan Fault has transitioned
to critical from a less severe state. (n = power supply number)

Severity: Error

Description: A sensor has changed to Critical
state from a less severe state.

Action:

1. Make sure that there are no obstructions, such as bundled
   cables, to the airflow from the power-supply fan.
2. Replace power supply n.
   (n = power supply number)

Power messages

Event ID: 80010902-0701xxxx

Message: Numeric sensor Planar 3.3V going high
(upper critical) has asserted.

Severity: Error

Description: An upper critical sensor going
high has asserted.

Action:

(Trained technician only)

1. For the hot-swap power-supply systems, replace Power Paddle
   Card.
2. For the fixed power-supply systems, replace the power
   supply.
3. Replace System board.

Event ID: 80010202-0701xxxx

Message: Numeric sensor Planar 3.3V going high
(upper critical) has asserted.

Severity: Error

Description: A lower critical sensor going low
has asserted.

Action:

(Trained technician only)

1. For the hot-swap power-supply systems, replace Power Paddle
   Card.
2. For the fixed power-supply systems, replace the power
   supply.
3. Replace System board.

Event ID: 80010902-0701xxxx

Message: Numeric sensor Planar 5V going high
(upper critical) has asserted.

Severity: Error

Description: An upper critical sensor going
high has asserted.

Action:

(Trained technician only)

1. For the hot-swap power-supply systems, replace Power Paddle
   Card.
2. For the fixed power-supply systems, replace the power
   supply.
3. Replace System board

Event ID: 80010202-0701xxxx

Message: Numeric sensor Planar 5V going low
(lower critical) has asserted.

Severity: Error

Description: A lower critical sensor going low
has asserted.

Action:

(Trained technician only)

1. For the hot-swap power-supply systems, replace Power Paddle
   Card.
2. For the fixed power-supply systems, replace the power
   supply.
3. Replace System board

Event ID: 80010902-0701xxxx

Message: Numeric sensor Planar 12V going low
(lower critical) has asserted.

Severity: Error

Description: An upper critical sensor going
high has asserted.

Action:

1. Check power supply n LED.
2. Remove the failing power supply.
3. (Trained technician only) Replace the system board.
   (n = power supply number)

Event ID: 80010202-0701xxxx

Message: Numeric sensor Planar 12V going low
(lower critical) has asserted.

Severity: Error

Description: A lower critical sensor going low
has asserted.

Action:

1. Check power supply n LED.
2. Remove the failing power supply.
3. Use the IBM Power Configurator utility to determine current
   system power consumption. For more information and to download
   the
   utility, go to
   http://www-03.ibm.com/systems/bladecenter/resources/powerconfig.html
4. For hot-swap power-supply systems, follow actions listed in
   “Power problems” and “Solving power
   problems” in the Service Guide
5. (Trained technician only) Replace the system board.
   (n = power supply number)

Event ID: 80010002-0701xxxx

Message: Numeric sensor Planar VBAT going low
(lower non-critical) has asserted.

Severity: Warning

Description: A lower critical sensor going low
has asserted.

Action:

Replace the system battery

Event ID: 80010202-0701xxxx

Message: Numeric sensor Planar VBAT going low
(lower critical) has asserted.

Severity: Error

Description: A lower critical sensor going low
has asserted.

Action:

Replace the system battery

Event ID:
806f0008-0a01xxxx
806f0008-0a02xxxx

Message: The Power Supply (Power Supply n)
presence has been added to container. (n = power supply number)

Severity: Info

Description: Power supply n has been added. (n
= power supply number)

Action:

No action; information only.

Event ID: 806f0009-1301xxxx

Message: The Power Supply (Power Supply n) has
been turned off.

Severity: Info

Description: This message is for the use case
when an implementation has detected a Power Unit that has been
Disabled.

Action:

No action; information only.

Event ID:
806f0108-0a01xxxx
806f0108-0a02xxxx

Message: The Power Supply n has failed. (n =
power supply number)

Severity: Error

Description: Power supply n has failed. (n =
power supply number)

Action:

1. Reseat power supply n.
2. If the power-on LED is not lit and the power-supply error LED
   is lit, replace power supply n for both hot-swap power-supply
   systems and fixed power-supply systems.
3. If both the power-on LED and the power-supply error LED are not
   lit:
   • Use IBM power configurator utility to determine current system
     power consumption. For more information and to download the uility,
     go to
     http://www-03.ibm.com/systems/bladecenter/resources/powerconfig.html
   • For hot-swap power-supply systems, follow actions listed in
     “Power problems” and “Solving power
     problems” in the Service Guide.
     (n = power supply number)

Event ID: 806f0109-1301xxxx

Message: The Power Supply n has been Power
Cycled. (n = power supply number)

Severity: Info

Description: This message is for the use case
when an implementation has detected a Power Unit that has been
power cycled.

Action:

No action; information only.

Event ID: 806f0223-2101xxxx

Message: Powering off system %1 initiated by %2
(%1 = CIM_ComputerSystem.ElementName) (%2 =
CIM_Watchdog.ElementName)

Severity: Info

Description: This message is for the use case
when an implementation has detected a Poweroff by Watchdog has
occurred.

Action:

No action; information only.

Event ID:
806f0308-0a01xxxx
806f0308-0a02xxxx

Message: The Power Supply n has lost input. (n
= power supply number)

Severity: Info

Description: Power supply n AC has lost. (n =
power supply number)

Action:

1. Reconnect the power cords.
2. Check power supply n LED.
3. See “Power problems” and “Solving power
   problems” for more information.
   (n = power supply number)

Event ID:
80070208-0a01xxxx
80070208-0a02xxxx

Message: Sensor PS n Therm Fault has
transitioned to critical from a less severe state. (n = power
supply number)

Severity: Error

Description: A sensor has changed to Critical
state from a less severe state.

Action:

1. Make sure that there are no obstructions, such as bundled
   cables, to the airflow from the power-supply fan.
2. Use the IBM Power Configurator utility to determine current
   system power consumption. For more information and to download the
   utility, go to
   http://www-03.ibm.com/systems/bladecenter/resources/powerconfig.html.
3. Replace power supply n.
   (n = power supply number)

Event ID: 80070603-0701xxxx

Message: Sensor Pwr Rail 1 Fault has
transitioned to non-recoverable

Severity: Error

Description: A sensor has changed to
Nonrecoverable state.

Action:

See more information in “Power problems”and
“Solving power problems” in the Service Guide.

Event ID: 80070603-0701xxxx

Message: Sensor Pwr Rail 2 Fault has
transitioned to non-recoverable

Severity: Error

Description: A sensor has changed to
Nonrecoverable state.

Action:

See more information in “Power problems”and
“Solving power problems” in the Service Guide.

Event ID: 80070603-0701xxxx

Message: Sensor Pwr Rail 3 Fault has
transitioned to non-recoverable

Severity: Error

Description: A sensor has changed to
Nonrecoverable state.

Action:

See more information in “Power problems”and
“Solving power problems” in the Service Guide.

Event ID: 80070603-0701xxxx

Message: Sensor Pwr Rail 4 Fault has
transitioned to non-recoverable

Severity: Error

Description: A sensor has changed to
Nonrecoverable state.

Action:

See more information in “Power problems”and
“Solving power problems” in the Service Guide.

Event ID: 80070603-0701xxxx

Message: Sensor Pwr Rail 5 Fault has
transitioned to non-recoverable

Severity: Error

Description: A sensor has changed to
Nonrecoverable state.

Action:

See more information in “Power
problems”and“Solving power problems” in the
Service Guide.

Event ID:
80070608-0a01xxxx
80070608-0a02xxxx

Message: Sensor PS n 12V AUX Fault has
transitioned to non-recoverable from a less severe state. (n =
power supply number)

Severity: Error

Description: A sensor has changed to
non-recoverable state from a less severe state.

Action:

1. Check power supply n LED.
2. Replace power supply n.
   (n = power supply number)

Event ID:
80070608-0a01xxxx
80070608-0a02xxxx

Message: Sensor PS n 12V OC Fault has
transitioned to non-recoverable from a less severe state. (n =
power supply number)

Severity: Error

Description: A sensor has changed to
non-recoverable state from a less severe state.

Action:

1. Use the IBM Power Configurator utility to determine current
   system power consumption. For more information and to download the
   utility, go to
   http://www-03.ibm.com/systems/bladecenter/resources/powerconfig.html.
2. For the hot-swap power-supply systems, follow actions listed in
   “Power problems” and “Solving power
   problems” in the Service Guide.
3. Replace the power supply.

Event ID:
80070608-0a01xxxx
80070608-0a02xxxx

Message: Sensor PS n 12V OV Fault has
transitioned to non-recoverable from a less severe state. (n =
power supply number)

Severity: Error

Description: A sensor has changed to
non-recoverable state from a less severe state.

Action:

1. Check power supply n LED.
2. Remove the failing power supply.
3. (Trained technician only) Replace the system board.
   (n = power supply number)

Event ID:
80070608-0a01xxxx
80070608-0a02xxxx

Message: Sensor PS n 12V UV Fault has
transitioned to non-recoverable from a less severe state. (n =
power supply number)

Severity: Error

Description: A sensor has changed to
non-recoverable state from a less severe state.

Action:

1. Check power supply n LED.
2. Remove the failing power supply.
3. For the hot-swap power-supply systems, follow actions listed in
   “Power problems” and “Solving power
   problems” in the Service Guide.
   (n = power supply number)

Event ID: 800b0008-1301xxxx

Message: Power Unit has been fully
redundant.

Severity: Info

Description: Power unit redundancy has been
restored.

Action:

No action; information only.

Event ID: 800b0108-1301xxxx

Message: Power Unit redundancy lost has
asserted.

Severity: Error

Description: Power unit redundancy has been
restored.

Action:

1. Check the LEDs for both power supplies.
2. Follow the actions in “Power-supply LEDs” in the
   Service Guide.

Event ID: 806f0608-1301xx03

Message: Power supply PS Configuration error
with rating mismatch.

Severity: Error

Description: A power supply configuration error
(rating mismatch) has occurred.

Action:

1. Make sure that the power supplies installed are with the same
   rating or wattage.
2. Reinstall the power supplies with the same rating or
   wattage.

Microprocessor messages

Event ID:
806f0007-0301xxxx
806f0007-0302xxxx

Message: The Processor CPU n Status has Failed
with IERR. (n = microprocessor number)

Severity: Error

Description: A processor failed — IERR
condition has occurred.

Action:

1. Make sure that the latest levels of firmware and device drivers
   are installed for all adapters and standard devices, such as
   Ethernet, SCSI, and SAS.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
2. Update the firmware (UEFI and IMM) to the latest level.
3. Run the DSA program.
4. Reseat the adapter.
5. Replace the adapter.
6. (Trained technician only) Replace microprocessor n.
7. (Trained technician only) Replace the system board.
   (n = microprocessor number)

Event ID: 806f000f-22010cxx

Message: CPU voltage mismatch detected on %1.
(%1 = CIM_Processor.ElementName

Severity: Error

Description: This message is for the use case
when an implementation has detected a CPU voltage mismatch with the
socket voltage.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Event ID:
806f0107-0301xxxx
806f0107-0302xxxx

Message: The Processor CPU n Status has been
detected an over-temperature condition. (n = microprocessor
number)

Severity: Error

Description: An over temperature condition has
occurred.

Action:

1. Make sure that the latest levels of firmware and device drivers
   are installed for all adapters and standard devices, such as
   Ethernet, SCSI, and SAS.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
2. Update the firmware (UEFI and IMM) to the latest level.
3. Run the DSA program.
4. Re-seat the adapter.
5. Replace the adapter.
6. (Trained technician only) Replace microprocessor n .
7. (Trained technician only) Replace the system board.
   (n = microprocessor number)

Event ID:
806f0207-0301xxxx
806f0207-0302xxxx

Message: The Processor CPU n Status has Failed
with BIST condition. (n = microprocessor number)

Severity: Error

Description: A processor failed — BIST
condition has occurred.

Action:

1. Make sure that the fans are operating. There are no
   obstructions to the airflow (front and rear of the server), the air
   baffles are in place and correctly installed, and the server cover
   is installed and
   completely closed.
2. Make sure that the heat sink for microprocessor nis installed
   correctly.
3. (Trained technician only) Replace microprocessor n .
   (n = microprocessor number)

Event ID: 806f0207-2584xxxx

Message: All CPUs / one of the CPUs has failed
with FRB1/BIST condition.

Severity: Error

Description: A Processor Failed — FRB1/BIST
condition has been detected.

Action:

1. Reseat the microprocessor, and then restart the server.
2. Replace microprocessor n.
   (n = microprocessor number)

Event ID: 806f030c-2581xxxx

Message: Scrub Failure for All DIMMS / one of
the DIMMs on subsystem.

Severity: Error

Description: A memory scrub failure has been
detected.

Action:

1. Reseat the DIMM, and then restart the server
2. Replace DIMM n.
   (n = DIMM number)

Event ID:
806f0507-0301xxxx
806f0507-0302xxxx
806f0507-2584xxxx

Message: The Processor CPU n Status has a
Configuration Mismatch. (n = microprocessor number)

Severity: Error

Description: A processor configuration mismatch
has occurred.

Action:

1. Check the CPU LED. See more information about the CPU LED in
   “Server controls, LEDs, and power” in the Service
   Guide.
2. Check for a server firmware update.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
3. Make sure that the installed microprocessors are compatible
   with each other.
4. (Trained technician only) Reseat microprocessor n .
5. (Trained technician only) Replace microprocessor n .
   (n = microprocessor number)

Event ID:
806f0607-0301xxxx
806f0607-0302xxxx
806f0607-2584xxxx

Message: An SM BIOS Uncorrectable CPU complex
error for Processor n has asserted. (n = microprocessor number)

Severity: Error

Description: The system management handler has
detected an internal microprocessor error.

Action:

1. Make sure that the installed microprocessors are compatible
   with each other.
2. Update the server firmware to the latest level.
3. (Trained technician only) Replace the incompatible
   microprocessor.

Event ID:
806f0807-0301xxxx
806f0807-0302xxxx

Message: The Processor CPU n has been disabled.
(n = microprocessor number)

Severity: Info

Description: A processor has been disabled.

Action:

1. Update the firmware (UEFI and IMM) to the latest level.
2. Run the DSA program.
3. Reseat the adapter.
4. Replace the adapter.
5. (Trained technician only) Replace microprocessor n.
6. 6. (Trained technician only) Replace the system board.
   (n = microprocessor number)

Event ID: 806f0807-2584xxxx

Message: The Processor for One of the CPUs has
been disabled.

Severity: Info

Description: A processor has been disabled.

Action:

1. Update the firmware (UEFI and IMM) to the latest level.
2. Run the DSA program.
3. Reseat the adapter.
4. Replace the adapter.
5. (Trained technician only) Replace microprocessor n.
6. (Trained technician only) Replace the system board.
   (n = microprocessor number)

Event ID: 806f0807-2584xxxx

Message: The Processor for All CPUs has been
disabled.

Severity: Info

Description: A processor has been disabled.

Action:

1. Update the firmware (UEFI and IMM) to the latest level.
2. Run the DSA program.
3. Reseat the adapter.
4. Replace the adapter.
5. (Trained technician only) Replace microprocessor n.
6. (Trained technician only) Replace the system board.
   (n = microprocessor number)

Event ID:
806f0a07-0301xxxx
806f0a07-0302xxxx

Message: The Processor CPU n is operating in a
Degraded State. (n = microprocessor number)

Severity: Warning

Description: Throttling has occurred for
microprocessor n. (n = microprocessor number)

Action:

1. Make sure that the fans are operating, that there are no
   obstructions to the airflow (front and rear of the server), that
   the air baffles are in place and correctly installed, and that the
   server cover is installed and completely closed.
2. Check the ambient temperature. You must be operating within the
   specifications.
3. Make sure that the heat sink for microprocessor nis installed
   correctly.
4. (Trained technician only) Replace microprocessor n.
   (n = microprocessor number)

Event ID:
80070201-0301xxxx
80070201-0302xxxx

Message: Sensor CPU n OverTemp has transitioned
to critical from a less severe state. (n = microprocessor
number)

Severity: Error

Description: A sensor has changed to critical
state from a less severe state.

Action:

1. Make sure that the fans are operating, that there are no
   obstructions to the airflow (front and rear of the server), that
   the air baffles are in place and correctly installed, and that the
   server cover is installed and completely closed.
2. Check the ambient temperature. You must be operating within the
   specifications.
3. Make sure that the heat sink for microprocessor nis installed
   correctly.
4. (Trained technician only) Replace microprocessor n.
   (n = microprocessor number)

Event ID:
80070301-0301xxxx
80070301-0302xxxx

Message: Sensor CPU n OverTemp has transitioned
to non-recoverable from a less severe state. (n = microprocessor
number)

Severity: Error

Description: A sensor has changed to
non-recoverable state from a less severe state.

Action:

1. Make sure that the fans are operating, that there are no
   obstructions to the airflow (front and rear of the server), that
   the air baffles are in place and correctly installed, and that the
   server cover is installed and completely closed.
2. Check the ambient temperature. You must be operating within the
   specifications.
3. Make sure that the heat sink for microprocessor n is installed
   correctly.
4. (Trained technician only) Replace microprocessor n.
   (n = microprocessor number)

Event ID:
8007021b-0301xxxx
8007021b-0302xxxx

Message: Sensor CPU n QPI link error has
transitioned to critical from a less severe state. (n =
microprocessor number)

Severity: Error

Description: A sensor has changed to critical
state from a less severe state.

Action:

1. Remove cpu
2. Check cpu socket pins, any damage or contained or bending,
   replace the system board.
3. Check cpu damage, replace cpu.

Event ID: 806f0813-2584xxxx

Message: An Uncorrectable Bus Error has
occurred on system %1.(%1 = CIM_ComputerSystem. ElementName)

Severity: Error

Description: A bus uncorrectable error has
occurred. (Sensor = Critical Int CPU)

Action:

1. Check the system-event log.
2. (Trained technician only) Remove the failing microprocessor
   from the system board.
3. Check for a server firmware update.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
4. Make sure that the two microprocessors are matching.
5. (Trained technician only) Replace the system board.

Memory errors

Event ID: 806f000f-220101xx

Message: The System %1 has detected no memory
in the system. (%1 = CIM_ComputerSystem.ElementName)

Severity: Error

Description: This message is for the use case
when an implementation has detected that memory was detected in the
system.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Memory errors

Event ID: 806f000f-220102xx

Message: Subsystem %1 has insufficient memory
for operation. (%1 = CIM_Memory.ElementName)

Severity: Error

Description: This message is for the use case
when an implementation has detected that the usable Memory is
insufficient for operation.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Memory errors

Event ID: 806f0813-2581xxxx

Message: An Uncorrectable Bus Error has
occurred on system %1.(%1 = CIM_ComputerSystem. ElementName)

Severity: Error

Description: A bus uncorrectable error has
occurred. (Sensor = Critical Int DIMM)

Action:

1. Check the system-event log.
2. Check the DIMM error LEDs.
3. Remove the failing DIMM from the system board.
4. Check for a server firmware update.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
5. Make sure that the installed DIMMs are supported and configured
   correctly.
6. (Trained technician only) Replace the system board.

Memory errors

Event ID:
806f010c-2001xxxx
806f010c-2002xxxx
806f010c-2003xxxx
806f010c-2004xxxx
806f010c-2005xxxx
806f010c-2006xxxx
806f010c-2007xxxx
806f010c-2008xxxx
806f010c-2009xxxx
806f010c-200axxxx
806f010c-200bxxxx
806f010c-200cxxxx

Message: Memory uncorrectable error detected
for Memory DIMM n Status. (n = DIMM number)

Severity: Error

Description: A memory uncorrectable error has
occurred.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. 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.
3. If the problem follows the DIMM, replace the failing DIMM.
4. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. If the connector contains
   any foreign material or is damaged, replace the system board.
5. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found, replace the system board .
6. (Trained technician only) Replace the affected
   microprocessor.

Event ID: 806f010c-2581xxxx

Message: Memory uncorrectable error detected
for One of the DIMMs.

Severity: Error

Description: A memory uncorrectable error has
occurred.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. 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.
3. If the problem follows the DIMM, replace the failing DIMM.
4. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. If the connector contains
   any foreign material or is damaged, replace the system board.
5. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found, replace the system board.
6. (Trained technician only) Replace the affected
   microprocessor.

Event ID: 806f010c-2581xxxx

Message: Memory uncorrectable error detected
for All DIMMs.

Severity: Error

Description: A memory uncorrectable error has
occurred.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. 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.
3. If the problem follows the DIMM, replace the failing DIMM.
4. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. If the connector contains
   any foreign material or is damaged, replace the system board.
5. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found, replace the system board.
6. (Trained technician only) Replace the affected
   microprocessor.

Event ID:
806f030c-2001xxxx
806f030c-2002xxxx
806f030c-2003xxxx
806f030c-2004xxxx
806f030c-2005xxxx
806f030c-2006xxxx
806f030c-2007xxxx
806f030c-2008xxxx
806f030c-2009xxxx
806f030c-200axxxx
806f030c-200bxxxx
806f030c-200cxxxx

Message: Memory DIMM n Status Scrub failure
detected. (n = DIMM number)

Severity: Error

Description: A memory scrub failure has been
detected.

Action:

Note: Each time you install or remove a DIMM,
you must disconnect the server from the power source; then, wait 10
seconds before restarting the server.

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. Make sure that the DIMMs are firmly seated and no foreign
   material is found in the DIMM connector. Then, retry with the same
   DIMM.
3. If the problem is related to a DIMM, replace the failing DIMM
   indicated by the error LEDs.
4. If the problem occurs on the same DIMM connector, 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.
5. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. If the connector contains
   any foreign material or is damaged, replace the system board.
6. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found, replace the system board.
7. (Trained technician only) Swap the affected microprocessor, if
   there are more than one microprocessor installed. If the problem
   follows the microprocessor, replace the affected
   microprocessor.
8. (Trained technician only) Replace the system board.

Event ID:
806f040c-2001xxxx
806f040c-2002xxxx
806f040c-2003xxxx
806f040c-2004xxxx
806f040c-2005xxxx
806f040c-2006xxxx
806f040c-2007xxxx
806f040c-2008xxxx
806f040c-2009xxxx
806f040c-200axxxx
806f040c-200bxxxx
806f040c-200cxxxx

Message: Memory DIMM disabled for DIMM n
Status. (n = DIMM number)

Severity: Info

Description: DIMM disabled.

Action:

1. Make sure the DIMM is installed correctly.
2. If the DIMM was disabled because of a memory fault (memory
   uncorrectable error or memory logging limit reached), follow the
   suggested actions for that error event and restart the server.
3. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory event. If no memory
   fault is recorded in the logs and no DIMM connector error LED is
   lit, you can re-enable the DIMM through the Setup utility or the
   Advanced Settings Utility (ASU).

Event ID: 806f040c-2581xxxx

Message: Memory DIMM disabled for One of the
DIMMs.

Severity: Info

Description: DIMM disabled.

Action:

1. Make sure the DIMM is installed correctly.
2. If the DIMM was disabled because of a memory fault (memory
   uncorrectable error or memory logging limit reached), follow the
   suggested actions for that error event and restart the server.
3. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory event. If no memory
   fault is recorded in the logs and no DIMM connector error LED is
   lit, you can re-enable the DIMM through the Setup utility or the
   Advanced Settings Utility (ASU).

Event ID: 806f040c-2581xxxx

Message: Memory DIMM disabled for All
DIMMs.

Severity: Info

Description: DIMM disabled.

Action:

1. Make sure the DIMM is installed correctly.
2. If the DIMM was disabled because of a memory fault (memory
   uncorrectable error or memory logging limit reached), follow the
   suggested actions for that error event and restart the server.
3. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory event. If no memory
   fault is recorded in the logs and no DIMM connector error LED is
   lit, you can re-enable the DIMM through the Setup utility or the
   Advanced Settings Utility (ASU).

Event ID:
806f050c-2001xxxx
806f050c-2002xxxx
806f050c-2003xxxx
806f050c-2004xxxx
806f050c-2005xxxx
806f050c-2006xxxx
806f050c-2007xxxx
806f050c-2008xxxx
806f050c-2009xxxx
806f050c-200axxxx
806f050c-200bxxxx
806f050c-200cxxxx

Message: Memory Logging Limit Reached for DIMM
n Status. (n = DIMM number)

Severity: Error

Description: The memory logging limit has been
reached.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. 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.
3. If the error still occurs on the same DIMM, replace the
   affected DIMM.
4. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. If the connector contains
   any foreign material or is damaged, replace the system board.
5. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found, replace the system board.
6. (Trained technician only) Replace the affected
   microprocessor.

Event ID: 806f050c-2581xxxx

Message: Memory Logging Limit Reached for One
of the DIMMs.

Severity: Error

Description: The memory logging limit has been
reached.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. 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.
3. If the error still occurs on the same DIMM, replace the
   affected DIMM.
4. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. If the connector contains
   any foreign material or is damaged, replace the system board.
5. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found, replace the system board .
6. (Trained technician only) Replace the affected
   microprocessor.

Event ID: 806f050c-2581xxxx

Message: Memory Logging Limit Reached for All
DIMMs.

Severity: Error

Description: The memory logging limit has been
reached.

Action:

1. Check the IBM support website for an applicable retain tip or
   firmware update that applies to this memory error.
2. 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.
3. If the error still occurs on the same DIMM, replace the
   affected DIMM.
4. (Trained technician only) If the problem occurs on the same
   DIMM connector, check the DIMM connector. If the connector contains
   any foreign material or is damaged, replace the system board.
5. (Trained technician only) Remove the affected microprocessor
   and check the microprocessor socket pins for any damaged pins. If a
   damage is found, replace the system board.
6. (Trained technician only) Replace the affected
   microprocessor.

Event ID:
806f070c-2001xxxx
806f070c-2002xxxx
806f070c-2003xxxx
806f070c-2004xxxx
806f070c-2005xxxx
806f070c-2006xxxx
806f070c-2007xxxx
806f070c-2008xxxx
806f070c-2009xxxx
806f070c-200axxxx
806f070c-200bxxxx
806f070c-200cxxxx

Message: Memory DIMM Configuration Error for
DIMM n Status. (n = DIMM number)

Severity: Error

Description: A memory DIMM configuration error
has occurred.

Action:

Make sure that DIMMs are installed in the correct sequence and
have the same size, type, speed, and technology.

Event ID: 806f070c-2581xxxx

Message: Memory DIMM Configuration Error for
One of the DIMMs.

Severity: Error

Description: A memory DIMM configuration error
has occurred.

Action:

Make sure that DIMMs are installed in the correct sequence and
have the same size, type, speed, and technology

Event ID: 806f070c-2581xxxx

Message: Memory DIMM Configuration Error for
All DIMMs.

Severity: Error

Description: A memory DIMM configuration error
has occurred.

Action:

Make sure that DIMMs are installed in the correct sequence and
have the same size, type, speed, and technology.

Event ID:
806f090c-2001xxxx
806f090c-2002xxxx
806f090c-2003xxxx
806f090c-2004xxxx
806f090c-2005xxxx
806f090c-2006xxxx
806f090c-2007xxxx
806f090c-2008xxxx
806f090c-2009xxxx
806f090c-200axxxx
806f090c-200bxxxx
806f090c-200cxxxx

Message: Memory DIMM for DIMM n Status has been
automatically throttled. (n = DIMM number)

Severity: Warning

Description: A memory DIMM has been
throttled.

Action:

1. Reseat the DIMM, and then restart the server.
2. Replace DIMM n.
   (n = DIMM number)

Event ID:
806f0a0c-2001xxxx
806f0a0c-2002xxxx
806f0a0c-2003xxxx
806f0a0c-2004xxxx
806f0a0c-2005xxxx
806f0a0c-2006xxxx
806f0a0c-2007xxxx
806f0a0c-2008xxxx
806f0a0c-2009xxxx
806f0a0c-200axxxx
806f0a0c-200bxxxx
806f0a0c-200cxxxx

Message: An Over-Temperature condition has been
detected on the DIMM n Status. (n = DIMM number)

Severity: Error

Description: An over-temperature condition has
occurred for DIMM n. (n = DIMM number)

Action:

1. Make sure that the fans are operating, that there are no
   obstructions to the airflow, that the air baffles are in place and
   correctly installed, and that the server cover is installed and
   completely closed.
2. Make sure that ambient temperature is within the
   specifications.
3. If a fan has failed, complete the action for a fan
   failure.
4. Replace DIMM n.
   (n = DIMM number)

Event ID: 800b010c-2581xxxx

Message: Backup Memory redundancy lost has
asserted.

Severity: Error

Description: Redundancy has been lost.

Action:

1. Check the system-event log for DIMM failure events
   (uncorrectable or PFA) and correct the failures.
2. Re-enable mirroring in the Setup utility.

Event ID: 800b030c-2581xxxx

Message: Backup Memory sufficient resources
from redundancy degraded has asserted.

Severity: Warning

Description: There is no redundancy. The state
has been transitioned from redundancy to sufficient resources.

Action:

1. Check the system-event log for DIMM failure events
   (uncorrectable or PFA) and correct the failures.
2. Re-enable mirroring in the Setup utility.

Event ID: 800b050c-2581xxxx

Message: Backup Memory insufficient resources
has asserted.

Severity: Error

Description: There is no redundancy and
insufficient to continue operation.

Action:

1. Check the system-event log for DIMM failure events
   (uncorrectable or PFA) and correct the failures.
2. Re-enable mirroring in the Setup utility.

Recovery messages

Event ID:
816f000d-0400xxxx
816f000d-0401xxxx
816f000d-0402xxxx
816f000d-0403xxxx
816f000d-0404xxxx
816f000d-0405xxxx
816f000d-0406xxxx
816f000d-0407xxxx

Message: The Drive n Status has been removed
from unit. (n = hard disk drive number)

Severity: Error

Description: A drive has been removed.

Action:

1. Reseat hard disk drive n.(n = hard disk drive number). Wait 1
   minute or more before reinstalling the drive.
2. Replace the hard disk drive.
3. Make sure that the disk firmware and RAID controller firmware
   is at the latest level.
4. Check the SAS cable.

Event ID:
806f010d-0400xxxx
806f010d-0401xxxx
806f010d-0402xxxx
806f010d-0403xxxx
806f010d-0404xxxx
806f010d-0405xxxx
806f010d-0406xxxx
806f010d-0407xxxx

Message: The Drive n Status has been disabled
due to a detected fault. (n = hard disk drive number)

Severity: Error

Description: A drive has been disabled because
of a fault.

Action:

1. Run the hard disk drive diagnostic test on drive n.
2. Reseat the following components:
   1. Hard disk drive (wait 1 minute or more before
      reinstalling the drive).
   2. Cable from the system board to the backplane
3. Replace the following components one at a time, in the order
   shown, restarting the server each time:
   1. Hard disk drive
   2. Cable from the system board to the backplane
   3. Hard disk drive backplane
      (n = hard disk drive number)

Event ID:
806f020d-0400xxxx
806f020d-0401xxxx
806f020d-0402xxxx
806f020d-0403xxxx
806f020d-0404xxxx
806f020d-0405xxxx
806f020d-0406xxxx
806f020d-0407xxxx

Message: The Drive n Status has a predictive
failure. (n = hard disk drive number)

Severity: Error

Description: A predictive failure has been
detected for drive n. (n = hard disk drive number)

Action:

1. Replace the hard drive n.
   (n = hard disk drive number)

Event ID:
806f020d-0400xxxx
806f020d-0401xxxx
806f020d-0402xxxx
806f020d-0403xxxx
806f020d-0404xxxx
806f020d-0405xxxx
806f020d-0406xxxx
806f020d-0407xxxx

Message: The Drive n Status has a predictive
failure. (n = hard disk drive number)

Severity: Error

Description: A predictive failure has been
detected for drive n. (n = hard disk drive number)

Action:

1. Replace the hard drive n.
   (n = hard disk drive number)

Event ID:
806f050d-0400xxxx
806f050d-0401xxxx
806f050d-0402xxxx
806f050d-0403xxxx
806f050d-0404xxxx
806f050d-0405xxxx
806f050d-0406xxxx
806f050d-0407xxxx

Message: Array %1 is in critical condition.(%1
= CIM_ComputerSystem. ElementName)

Severity: Error

Description: An array is in a critical state.
(Sensor = Drive n Status) (n = hard disk drive number)

Action:

1. Make sure that the RAID adapter firmware and hard disk drive
   firmware is at the latest level.
2. Make sure that the SAS cable is connected correctly.
3. Replace the SAS cable.
4. Replace the RAID adapter.
5. Replace the hard disk drive that is indicated by a lit status
   LED.

Event ID:
806f060d-0400xxxx
806f060d-0401xxxx
806f060d-0402xxxx
806f060d-0403xxxx
806f060d-0404xxxx
806f060d-0405xxxx
806f060d-0406xxxx
806f060d-0407xxxx

Message: Array %1 has failed. (%1 =
CIM_ComputerSystem. ElementName)

Severity: Error

Description: An array is in a failed state.
(Sensor = Drive n Status) (n = hard disk drive number)

Action:

1. Make sure that the RAID adapter firmware and hard disk drive
   firmware is at the latest level.
2. Make sure that the SAS cable is connected correctly.
3. Replace the SAS cable.
4. Replace the RAID adapter.
5. Replace the hard disk drive that is indicated by a lit status
   LED.

Event ID:
806f070d-0400xxxx
806f070d-0401xxxx
806f070d-0402xxxx
806f070d-0403xxxx
806f070d-0404xxxx
806f070d-0405xxxx
806f070d-0406xxxx
806f070d-0407xxxx

Message: The Drive n Status rebuilt has been in
progress. (n = hard disk drive number)

Severity: Info

Description: The Drive n has rebuilt in
progress. (n = hard disk drive number)

Action:

No action; information only.

PCI messages

Event ID: 806f0021-3001xxxx

Message: PCI fault has been detected for PCI n.
(n = PCI slot number)

Severity: Error

Description: A PCI fault has been detected.

Action:

1. Check the PCI LED. See more information about the PCI LED in
   “Server controls, LEDs, and power” in the Service
   Guide.
2. Reseat the affected adapters and riser card.
3. Update the server firmware (UEFI and IMM) and adapter
   firmware.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
4. Remove both adapters.
5. Replace the riser cards.
6. (Trained technicians only) Replace the system board.

Event ID: 806f0021-2582xxxx

Message: PCI fault has been detected for One of
PCI Error.

Severity: Error

Description: A PCI fault has been detected.

Action:

1. Check the PCI LED. See more information about the PCI LED in
   “Server controls, LEDs, and power” in the Service
   Guide.
2. Reseat the affected adapters and riser cards.
3. Update the server firmware (UEFI and IMM) and adapter
   firmware.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
4. Remove both adapters.
5. Replace the riser cards.
6. (Trained technicians only) Replace the system board.

Event ID: 806f0023-2101xxxx

Message: Watchdog Timer expired for IPMI
Watchdog.

Severity: Info

Description: This message is for the use case
when an implementation has detected a Watchdog Timer Expired.

Action:

No action; information only.

Event ID: 806f0113-0301xxxx

Message: A bus timeout has occurred on system
CPU 1 PECI.

Severity: Error

Description: This message is for the use case
when an implementation has detected a Bus Timeout.

Action:

1. Reseat the microprocessor, and then restart the server.
2. Replace microprocessor n.
   (n = microprocessor number)

Event ID: 806f0113-0302xxxx

Message: A bus timeout has occurred on system
CPU 2 PECI

Severity: Error

Description: This message is for the use case
when an implementation has detected a Bus Timeout.

Action:

1. Reseat the microprocessor, and then restart the server.
2. Replace microprocessor n.
   (n = microprocessor number)

Event ID: 06f0413-2582xxxx

Message: A PCI PERR has occurred on system
%1.(%1 = CIM_ComputerSystem. ElementName)

Severity: Error

Description: A PCI PERR has occurred. (Sensor =
PCIs)

Action:

1. Check the PCI LED. See more information about the PCI LED in
   “Server controls, LEDs, and power” in the Service
   Guide
2. Reseat the affected adapters and riser cards.
3. Update the server firmware (UEFI and IMM) and adapter
   firmware.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
4. Replace the adapters.
5. Replace the riser cards.

Event ID: 806f0513-2582xxxx

Message: A PCI SERR has occurred on system
%1.(%1 = CIM_ComputerSystem. ElementName)

Severity: Error

Description: A PCI SERR has occurred. (Sensor =
PCIs)

Action:

1. Check the PCI LED. See more information about the PCI LED in
   “Server controls, LEDs, and power” in the Service
   Guide.
2. Reseat the affected adapters and riser card.
3. Update the server firmware (UEFI and IMM) and adapter
   firmware.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
4. Make sure that the adapter is supported. For a list of
   supported optional devices, see
   http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/.
5. Replace the adapters.
6. Replace the riser cards.

Event ID: 806f0813-2582xxxx

Message: An Uncorrectable Bus Error has
occurred on system %1.(%1 = CIM_ComputerSystem.ElementName)

Severity: Error

Description: A bus uncorrectable error has
occurred. (Sensor = Critical Int PCI)

Action:

1. Check the system-event log.
2. Check the PCI LED. See more information about the PCI LED in
   “Server controls, LEDs, and power” in the Service
   Guide.
3. Remove the adapter from the indicated PCI slot.
4. Check for a server firmware update.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
5. (Trained technician only) Replace the system board.

Event ID:
806f0125-0B01xxxx
806f0125-0B02xxxx

Message: The entity of PCI riser has been
detected absent for PCI n. (n = PCI slot number)

Severity: Info

Description: The entity of PCI riser n has been
detected absent. (n = PCI slot number)

Action:

No action; information only.

General messages

Event ID: 80030006-2101xxxx

Message: Sensor Sig Verify Fail has
deasserted.

Severity: Info

Description: An implementation has detected a
sensor has deasserted.

Action:

No action; information only.

Event ID: 80030012-2301xxxx

Message: Sensor OS RealTime Mod has
deasserted.

Severity: Info

Description: Sensor OS RealTime Mod has
deasserted.

Action:

No action; information only.

Event ID:
80050108-0a01xxxx
80050108-0a02xxxx

Message: Sensor has indicated limit
exceeded.

Severity: Info

Description: This message is for the use case
when an implementation has detected a Sensor limit was
exceeded.

Action:

No action; information only.

Event ID: 80070114-2201xxxx

Message: Sensor TPM Lock / TPM Phy Pres Set has
transitioned from normal to non-critical state.

Severity: Warning

Description: An implementation has detected a
sensor transitioned to non-critical from normal.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Event ID: 80070202-0701xxxx

Message: Sensor Planar Fault has transitioned
to critical from a less severe state.

Severity: Error

Description: A sensor has changed to Critical
state from a less severe state.

Action:

1. Check the system-event log.
2. Check for an error LED on the system board.
3. Replace any failing device.
4. Check for a server firmware update.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
5. (Trained technician only) Replace the system board.

Event ID: 8007020f-2201xxxx

Message: Sensor TXT ACM module has transitioned
to critical from a less severe state.

Severity: Error

Description: A sensor has transitioned to
critical from less severe.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Event ID: 8007020f-2582xxxx

Message: Sensor No PCI I/O has transitioned to
critical from a less severe state.

Severity: Error

Description: A sensor has transitioned to
critical from less severe.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Event ID: 80070614-2201xxxx

Message: Sensor TPM Phy Pres Set has
transitioned to non-recoverable.

Severity: Error

Description: A sensor has transitioned to
non-recoverable.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Event ID: 806f011b-0701xxxx

Message: The Front USB connector has
encountered a configuration error.

Severity: Error

Description: The system had detected an
internal connection error.

Action:

Reseat the front USB cable on the system board.

Event ID: 806f011b-0701xxxx

Message: The Front Video connector has
encountered a configuration error.

Severity: Error

Description: The system had detected an
internal connection error.

Action:

Reseat the front video cable on the system board.

Event ID: 806f0123-2101xxxx

Message: Reboot of system %1 initited by %2.
(%1 = ComputerSystem.ElementName) (%2 = Watchdog.ElementName)

Severity: Info

Description: This message is for the use case
when an implementation has detected a Reboot by a Watchdog
occurred.

Action:

No action; information only.

Event ID: 806f0125-0c01xxxx

Message: Front panel entity has been detected
Absent.

Severity: Info

Description: A front panel entity has been
detected absent.

Action:

No action; information only.

Event ID: 806f0013-1701xxxx

Message: A front panel NMI has occurred on
system %1. (%1 = CIM_ComputerSystem. ElementName)

Severity: Error

Description: An operator information panel
NMI/diagnostic interrupt has occurred.

Action:

1. Check the device driver.
2. Reinstall the device driver.
3. Update all device drivers to the latest level.
4. Update the firmware (UEFI and IMM).

Event ID: 806f0013-1701xxxx

Message: A software NMI has occurred on system
%1. (%1 = CIM_ComputerSystem. ElementName)

Severity: Error

Description: A software NMI has occurred.

Action:

1. Check the device driver.
2. Reinstall the device driver.
3. Update all device drivers to the latest level.
4. Update the firmware (UEFI and IMM).

Event ID: 806f0823-2101xxxx

Message: Watchdog Timer interrupt occurred for
%1. (%1 = Watchdog.ElementName)

Severity: Info

Description: This message is for the use case
when an implementation has detected a Watchdog Timer interrupt
occurred.

Action:

No action; information only.

Event ID: 806f0a13-0301xxxx

Message: A Fatal Bus Error has occurred on
system CPU 1 PECI.

Severity: Error

Description: A bus fatal error has been
detected.

Action:

1. Reseat the microprocessor, and then restart the server.
2. Replace microprocessor n.
   (n = microprocessor number)

Event ID: 806f0a13-0302xxxx

Message: A Fatal Bus Error has occurred on
system CPU 2 PECI.

Severity: Error

Description: A bus fatal error has been
detected.

Action:

1. Reseat the microprocessor, and then restart the server.
2. Replace microprocessor n.
   (n = microprocessor number)

Event ID: 81030012-2301xxxx

Message: OS RealTime Mod state has
deasserted.

Severity: Info

Description: OS RealTime Mod state has
deasserted.

Action:

No action; information only.

Event ID: 80070219-0701xxxx

Message: Sensor Sys Board Fault has
transitioned to critical.

Severity: Error

Description: A sensor has changed to Critical
state from a less severe state.

Action:

1. Check the system-event log.
2. Check for an error LED on the system board.
3. Replace any failing device.
4. Check for a server firmware update.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
5. (Trained technician only) Replace the system board.

Event ID: 806f0312-2201xxxx

Message: Entry to aux log has asserted.

Severity: Info

Description: Entry to aux log has been
detected.

Action:

No action; information only.

Event ID: 80080128-2101xxxx

Message: Low security jumper presence has
asserted.

Severity: Info

Description: Entry to aux log has been
detected.

Action:

No action; information only.

Event ID: 8008010f-2101xxxx

Message: Physical presence jumper presence has
asserted.

Severity: Info

Description: The physical presence jumper has
been detected.

Action:

No action; information only.

Event ID: 81030006-2101xxxx

Message: Sig verify fail has deasserted.

Severity: Info

Description: The sig verify fail has
deasserted.

Action:

No action; information only.

Event ID: 806f0028-2101xxxx

Message: TPM command fail has asserted.

Severity: Warning

Description: The TPM sensor access has been
degraded or unavailable.

Action:

1. Turn off the server and disconnect it from power.

Firmware and software messages

Event ID: 806f000f-220103xx

Message: The System %1 encountered firmware
error — unrecoverable boot device failure. (%1 =
ComputerSystem.ElementName)

Severity: Error

Description: This message is for the use case
when an implementation has detected that System Firmware Error
Unrecoverable boot device failure has occurred.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Event ID: 806f000f-220104xx

Message: The System %1 has encountered a
motherboard failure. (%1 = ComputerSystem.ElementName)

Severity: Error

Description: This message is for the use case
when an implementation has detected that a fatal motherboard
failure in the system.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Event ID: 806f000f-220107xx

Message: The System %1 encountered firmware
error — unrecoverable keyboard failure. (%1 =
ComputerSystem.ElementName)

Severity: Error

Description: This message is for the use case
when an implementation has detected that System Firmware Error
Unrecoverable Keyboard failure has occurred.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Event ID: 806f000f-22010axx

Message: The System %1 encountered firmware
error — no video device detected. (%1 =
ComputerSystem.ElementName)

Severity: Error

Description: This message is for the use case
when an implementation has detected that System Firmware Error No
video device detected has occurred.

Action:

1. This is a UEFI detected event. The UEFI diagnostic code for
   this event can be found in the logged IMM message text. Please
   refer to the UEFI diagnostic code in the «UEFI diagnostic code»
   section of the Info Center for the appropriate user response.

Event ID: 806f000f-22010bxx

Message: Firmware BIOS (ROM) corruption was
detected on system %1 during POST. (%1 =
ComputerSystem.ElementName)

Severity: Error

Description: Firmware BIOS (ROM) corruption was
detected during POST. (Sensor = ABR Status)

Action:

1. Make sure the server meets the minimum configuration to
   start.
2. Recover theserver firmware from the backup page:
   1. Restart the server.
   2. At the prompt, press F3 to recover the firmware.
3. Update the server firmware to the latest level
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
4. Remove components one at a time, restarting the server each
   time, to see if the problem goes away.
5. If the problem remains, (trained technician) replace the system
   board.

Event ID: 806f000f-2201ffff

Message: The System %1 encountered a POST
Error. (%1 = ComputerSystem.ElementName)

Severity: Error

Description: The System ABR Status / Firmware
Error encountered a POST Error.

Action:

1. Make sure the server meets the minimum configuration to
   start.
2. Recover the server firmware from the backup page:
   1. Restart the server.
   2. At the prompt, press F3 to recover the firmware.
3. Update the server firmware to the latest level.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
4. Remove components one at a time, restarting the server each
   time, to see if the problem goes away.
5. If the problem remains, (trained technician) replace the system
   board.

Event ID: 806f000f-2201xxxx

Message: The System %1 encountered a POST
Error.(%1 = CIM_ComputerSystem. ElementName)

Severity: Error

Description: The System encountered a firmware
error. (Sensor = Firmware Error)

Action:

1. Make sure the server meets the minimum configuration to
   start.
2. Update the server firmware on the primary page.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster olution
   before you update the code.
3. (Trained technician only) Replace the system board.

Event ID: 806f010f-2201xxxx

Message: The System %1 encountered a POST Hang.
(%1 = CIM_ComputerSystem. ElementName)

Severity: Error

Description: The System encountered a firmware
hang. (Sensor = Firmware Error)

Action:

1. Make sure the server meets the minimum configuration to
   start.
2. Update the server firmware on the primary page.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
3. (Trained technician only) Replace the system board.

Event ID: 806f052b-2201xxxx

Message: IMM2 FW Failover has been
detected.

Severity: Error

Description: Invalid or unsupported firmware or
software was detected.

Action:

1. Make sure the server meets the minimum configuration to
   start.
2. Recover the server firmware from the backup page:
   1. Restart the server.
   2. At the prompt, press F3 to recover the firmware.
3. Update the server firmware to the latest level.
   Important: Some cluster solutions require specific code levels or
   coordinated code updates. If the device is part of a cluster
   solution, verify that the latest level of code is supported for the
   cluster solution before you update the code.
4. Remove components one at a time, restarting the server each
   time, to see if the problem goes away.
5. If the problem remains, (trained technician) replace the system
   board.

Web interface messages

Event ID: 40000001-00000000

Message: IMM Network Initialization
Complete.

Severity: Info

Description: An IMM network has completed
initialization.

Action:

No action; information only.

Event ID: 40000002-00000000

Message: Certificate Authority [arg1] has
detected a [arg2] Certificate Error.

Severity: Error

Description: A problem has occurred with the
SSL Server, SSL Client, or SSL Trusted CA certificate that has been
imported into the IMM. The imported certificate must contain a
public key that corresponds to the key pair that was previously
generated by the Generate a New Key and Certificate Signing Request
link.

Action:

1. Make sure that the certificate that you are importing is
   correct and correctly generated.
2. Try importing the certificate again.

Event ID: 40000003-00000000

Message: Ethernet Data Rate modified from
[arg1] to [arg2] by user [arg3].

Severity: Info

Description: The specified user has changed the
Ethernet data rate of the Integrated Management Module external
network interface to the specified value.

Action:

No action; information only.

Event ID: 40000004-00000000

Message: Ethernet Duplex setting modified from
[arg1] to [arg2] by user [arg3].

Severity: Info

Description: The specified user has changed the
Ethernet duplex setting of the Integrated Management Module
external network interface to the specified value.

Action:

No action; information only.

Event ID: 40000005-00000000

Message: Ethernet MTU setting modified from
[arg1] to [arg2] by user [arg3].

Severity: Info

Description: The specified user has changed the
Ethernet maximum transmission unit (MTU) setting of the Integrated
Management Module external network interface to the specified
value.

Action:

No action; information only.

Event ID: 40000006-00000000

Message: Ethernet locally administered MAC
address modified from [arg1] to [arg2] by user [arg3].

Severity: Info

Description: The specified user has changed the
Ethernet locally administered MAC address of the Integrated
Management Module external network interface to the specified
value.

Action:

No action; information only.

Event ID: 40000007-00000000

Message: Ethernet interface [arg1] by user
[arg2].

Severity: Info

Description: A specified user has enabled or
disabled the Ethernet interface.

Action:

No action; information only.

Event ID: 40000008-00000000

Message: Hostname set to [arg1] by user
[arg2].

Severity: Info

Description: A specified user has modified the
host name of the IMM.

Action:

No action; information only.

Event ID: 40000009-00000000

Message: IP address of network interface
modified from [arg1] to [arg2] by user [arg3].

Severity: Info

Description: The specified user has changed the
IP address of the Integrated Management Module external network
interface to the specified value.

Action:

No action; information only.

Event ID: 4000000a-00000000

Message: IP subnet mask of network interface
modified from [arg1] to [arg2] by user [arg3].

Severity: Info

Description: The specified user has changed the
subnet mask of the Integrated Management Module external network
interface to the specified value.

Action:

No action; information only.

Event ID: 4000000b-00000000

Message: IP address of default gateway modified
from [arg1] to [arg2] by user [arg3].

Severity: Info

Description: The specified user has changed the
gateway address of the Integrated Management Module external
network interface to the specified value.

Action:

No action; information only.

Event ID: 4000000c-00000000

Message: OS Watchdog response [arg1] by
[arg2].

Severity: Info

Description: This message is for the use case
where an OS Watchdog has been enabled or disabled by a user.

Action:

No action; information only.

Event ID: 4000000d-00000000

Message: DHCP[%1] failure, no IP address
assigned.(%1 = IP address, xxx.xxx.xxx.xxx)

Severity: Info

Description: A DHCP server has failed to assign
an IP address to the IMM.

Action:

Complete the following steps until the problem is solved:

1. Make sure that the Chassis Management Module network cable is
   connected.
2. Make sure that there is a DHCP server on the network that can
   assign an IP address to the IMM.

Event ID: 4000000e-00000000

Message: Remote Login Successful. Login ID:
[arg1] from [arg2] at IP address [arg3].

Severity: Info

Description: The specified user has logged in
to the Integrated Management Module.

Action:

No action; information only.

Event ID: 4000000f-00000000

Message: Attempting to %1 server %2 by user
%3.(%1 = Power Up, Power Down, Power Cycle, or Reset; %2 =
IBM_ComputerSystem.ElementName; %3 = user ID)

Severity: Info

Description: A user has used the IMM to perform
a power function on the server.

Action:

No action; information only.

Event ID: 40000010-00000000

Message: Security: Userid: ‘%1’ had %2 login
failures from WEB client at IP address %3.(%1 = user ID; %2 =
MaximumSuccessiveLoginFailures (currently set to 5 in the
firmware); %3 = IP address, xxx.xxx.xxx.xxx)

Severity: Error

Description: A user has exceeded the maximum
number of unsuccessful login attempts from a web browser and has
been prevented from logging in for the lockout period.

Action:

Complete the following steps until the problem is solved:

1. Make sure that the correct login ID and password are being
   used.
2. Have the system administrator reset the login ID or
   password.

Event ID: 40000011-00000000

Message: Security: Login ID: ‘%1’ had %2 login
failures from CLI at %3.(%1 = user ID; %2 =
MaximumSuccessiveLoginFailures (currently set to 5 in the
firmware); %3 = IP address, xxx.xxx.xxx.xxx)

Severity: Error

Description: A user has exceeded the maximum
number of unsuccessful login attempts from the command-line
interface and has been prevented from logging in for the lockout
period.

Action:

Complete the following steps until the problem is solved:

1. Make sure that the correct login ID and password are being
   used.
2. Have the system administrator reset the login ID or
   password.

Event ID: 40000012-00000000

Message: Remote access attempt failed. Invalid
userid or password received. Userid is ‘%1’ from WEB browser at IP
address %2.(%1 = user ID; %2 = IP address, xxx.xxx.xxx.xxx)

Severity: Error

Description: A user has attempted to log in
from a web browser by using an invalid login ID or password.

Action:

1. Make sure that the correct login ID and password are being
   used.
2. Have the system administrator reset the login ID or
   password.

Event ID: 40000013-00000000

Message: Remote access attempt failed. Invalid
userid or password received. Userid is ‘%1’ from TELNET client at
IP address %2.(%1 = user ID; %2 = IP address, xxx.xxx.xxx.xxx)

Severity: Error

Description: A user has attempted to log in
from a Telnet session by using an invalid login ID or password.

Action:

1. Make sure that the correct login ID and password are being
   used.
2. Have the system administrator reset the login ID or
   password.

Event ID: 40000014-00000000

Message: The [arg1] on system [arg2] cleared by
user [arg3].

Severity: Info

Description: The specified user has deleted
system log events or audit log events.

Action:

No action; information only.

Event ID: 40000015-00000000

Message: IMM reset was initiated by user %1.(%1
= user ID)

Severity: Info

Description: The Integrated Management Module
has been reset. The logs provide additional details.

Action:

No action; information only

Event ID: 40000016-00000000

Message: ENET[0] DHCP-HSTN=%1, DN=%2, IP@=%3,
SN=%4, GW@=%5, DNS1@=%6.(%1 = CIM_DNSProtocolEndpoint.Hostname; %2
= CIM_DNSProtocolEndpoint.DomainName; %3 =
CIM_IPProtocolEndpoint.IPv4Address; %4 =
CIM_IPProtocolEndpoint.SubnetMask; %5 = IP address,
xxx.xxx.xxx.xxx; %6 = IP address, xxx.xxx.xxx.xxx)

Severity: Info

Description: The DHCP server has assigned an
IMM IP address and configuration.

Action:

No action; information only.

Event ID: 40000017-00000000

Message: ENET[0] IP-Cfg:HstName=%1, IP@%2,
NetMsk=%3, GW@=%4.(%1 = CIM_DNSProtocolEndpoint.Hostname; %2 =
CIM_StaticIPSettingData.IPv4Address; %3 =
CIM_StaticIPSettingData.SubnetMask; %4 =
CIM_StaticIPSettingData.DefaultGatewayAddress)

Severity: Info

Description: An IMM IP address and
configuration have been assigned using client data.

Action:

No action; information only.

Event ID: 40000018-00000000

Message: LAN: Ethernet[0] interface is no
longer active.

Severity: Info

Description: The IMM Ethernet interface has
been disabled.

Action:

No action; information only.

Event ID: 40000019-00000000

Message: LAN: Ethernet[0] interface is now
active.

Severity: Info

Description: LAN: Ethernet[0] interface is now
active.

Action:

No action; information only.

Event ID: 4000001a-00000000

Message: DHCP setting changed to [arg1] by user
[arg2].

Severity: Info

Description: The specified user has changed the
DHCP setting of the Integrated Management Module external network
interface.

Action:

No action; information only.

Event ID: 4000001b-00000000

Message: Management Controller [arg1]:
Configuration restored from a file by user [arg2].

Severity: Info

Description: The specified user has restored
the Integrated Management Module (IMM) configuration from a
previously saved configuration file. Some configuration settings
might require that the IMM be restarted before they take
effect.

Action:

No action; information only.

Event ID: 4000001c-00000000

Message: Watchdog %1 Screen Capture
Occurred.(%1 = OS Watchdog or Loader Watchdog)

Severity: Error

Description: An operating-system error has
occurred, and the screen capture was successful.

Action:

If there was no operating-system error, complete the following
steps until the problem is solved:

1. Reconfigure the watchdog timer to a higher value.
2. Make sure that the IMM Ethernet over USB interface is
   enabled.
3. Reinstall the RNDIS or cdc_ether device driver for the
   operating system.
4. Disable the watchdog.
5. Check the integrity of the installed operating system.
   If there was an operating-system error, check the integrity of the
   installed operating system.

Event ID: 4000001d-00000000

Message: Watchdog %1 Failed to Capture
Screen.(%1 = OS Watchdog or Loader Watchdog)

Severity: Error

Description: An operating-system error has
occurred, and the screen capture failed.

Action:

Complete the following steps until the problem is solved:

1. Reconfigure the watchdog timer to a higher value.
2. Make sure that the IMM Ethernet over USB interface is
   enabled.
3. Reinstall the RNDIS or cdc_ether device driver for the
   operating system.
4. Disable the watchdog.
5. Check the integrity of the installed operating system.
6. Update the IMM firmware.

Important: Some cluster solutions require
specific code levels or coordinated code updates. If the device is
part of a cluster solution, verify that the latest level of code is
supported for the cluster solution before you update the code.

Event ID: 4000001e-00000000

Message: Running the backup IMM main
application.

Severity: Error

Description: The IMM was unable to run the
primary IMM image and has resorted to running the backup image.

Action: Update the IMM firmware.

Important: Some cluster solutions require specific code levels
or coordinated code updates. If the device is part of a cluster
solution, verify that the latest level of code is supported for the
cluster solution before you update the code.

Event ID: 4000001f-00000000

Message: Please ensure that the IMM is flashed
with the correct firmware. The IMM is unable to match its firmware
to the server.

Severity: Error

Description: The server does not support the
installed IMM firmware version.

Action: Update the IMM firmware to a version
that the server supports.

Important: Some cluster solutions require
specific code levels or coordinated code updates. If the device is
part of a cluster solution, verify that the latest level of code is
supported for the cluster solution before you update the code.

Event ID: 4000002a-00000000

Message: [arg1] Firmware mismatch internal to
system [arg2]. Please attempt to flash the [arg3] firmware.

Severity: Error

Description: This message is for the use case
where a specific type of firmware mismatch has been detected.

Action: No action; information only.

Event ID: 4000002b-00000000

Message: Domain name set to [arg1].

Severity: Info

Description: Domain source changed by user.

Action: No action; information only.

Event ID: 4000002c-00000000

Message: Domain Source changed to [arg1] by
user [arg2].

Severity: Info

Description: Domain source changed by user.

Action: No action; information only.

Event ID: 4000002d-00000000

Message: DDNS setting changed to [arg1] by user
[arg2].

Severity: Info

Description: DDNS setting changed by user.

Action: No action; information only.

Event ID: 4000002e-00000000

Message: DDNS registration successful. The
domain name is [arg1].

Severity: Info

Description: DDNS registration and values.

Action: No action; information only.

Event ID: 4000002f-00000000

Message: IPv6 enabled by user [arg1].

Severity: Info

Description: IPv6 protocol is enabled by
user.

Action: No action; information only.

Event ID: 40000020-00000000

Message: IMM reset was caused by restoring
default values.

Severity: Info

Description: The IMM has been reset because a
user has restored the configuration to its default settings.

Action: No action; information only.

Event ID: 40000021-00000000

Message: IMM clock has been set from NTP server
%1.(%1 = IBM_NTPService.ElementName)

Severity: Info

Description: The IMM clock has been set to the
date and time that is provided by the Network Time Protocol
server.

Action: No action; information only.

Event ID: 40000022-00000000

Message: SSL data in the IMM configuration data
is invalid. Clearing configuration data region and disabling
SSL+H25.

Severity: Error

Description: There is a problem with the
certificate that has been imported into the IMM. The imported
certificate must contain a public key that corresponds to the key
pair that was previously generated through the Generate a New Key
and Certificate Signing Request link.

Action:

1. Make sure that the certificate that you are importing is
   correct.
2. Try to import the certificate again.

Event ID: 40000023-00000000

Message: Flash of %1 from %2 succeeded for user
%3.(%1 = CIM_ManagedElement.ElementName; %2 = Web or LegacyCLI; %3
= user ID)

Severity: Info

Description: A user has successfully updated
one of the following firmware components:

• IMM main application
• IMM boot ROM
• Server firmware (UEFI)
• Diagnostics
• System power backplane
• Remote expansion enclosure power backplane
• Integrated service processor
• Remote expansion enclosure processor

Action: No action; information only.

Event ID: 40000024-00000000

Message: Flash of %1 from %2 failed for user
%3.(%1 = CIM_ManagedElement.ElementName; %2 = Web or LegacyCLI; %3
= user ID)

Severity: Info

Description: An attempt to update a firmware
component from the interface and IP address has failed.

Action: Try to update the firmware again.

Event ID: 40000025-00000000

Message: The Chassis Event Log (CEL) on system
%1 is 75% full.(%1 = CIM_ComputerSystem.ElementName)

Severity: Info

Description: The IMM event log is 75% full.
When the log is full, older log entries are replaced by newer
ones.

Action: To avoid losing older log entries, save
the log as a text file and clear the log.

Event ID: 40000026-00000000

Message: The Chassis Event Log (CEL) on system
%1 is 100% full.(%1 = CIM_ComputerSystem.ElementName)

Severity: Info

Description: The IMM event log is full. When
the log is full, older log entries are replaced by newer ones.

Action: To avoid losing older log entries, save
the log as a text file and clear the log.

Event ID: 40000027-00000000

Message: %1 Platform Watchdog Timer expired for
%2.(%1 = OS Watchdog or Loader Watchdog; %2 = OS Watchdog or Loader
Watchdog)

Severity: Error

Description: A Platform Watchdog Timer Expired
event has occurred.

Action:

1. Reconfigure the watchdog timer to a higher value.
2. Make sure that the IMM Ethernet over USB interface is
   enabled.
3. Reinstall the RNDIS or cdc_ether device driver for the
   operating system.
4. Disable the watchdog.
5. Check the integrity of the installed operating system.

Event ID: 40000028-00000000

Message: IMM Test Alert Generated by %1.(%1 =
user ID)

Severity: Info

Description: A user has generated a test alert
from the IMM.

Action: No action; information only.

Event ID: 40000029-00000000

Message: Security: Userid: ‘%1’ had %2 login
failures from an SSH client at IP address %3.(%1 = user ID; %2 =
MaximumSuccessiveLoginFailures (currently set to 5 in the
firmware); %3 = IP address, xxx.xxx.xxx.xxx)

Severity: Error

Description: A user has exceeded the maximum
number of unsuccessful login attempts from SSH and has been
prevented from logging in for the lockout period.

Action:

1. Make sure that the correct login ID and password are being
   used.
2. Have the system administrator reset the login ID or
   password.

Event ID: 40000030-00000000

Message: IPv6 disabled by user [arg1].

Severity: Info

Description: IPv6 protocol is disabled by
user.

Action: No action; information only.

Event ID: 40000031-00000000

Message: IPv6 static IP configuration enabled
by user [arg1].

Severity: Info

Description: IPv6 static address assignment
method is enabled by user.

Action: No action; information only.

Event ID: 40000032-00000000

Message: 40000032-00000000 IPv6 DHCP enabled by
user [arg1].

Severity: Info

Description: IPv6 DHCP assignment method is
enabled by user.

Action: No action; information only.

Event ID: 40000033-00000000

Message: 40000033-00000000 IPv6 stateless
auto-configuration enabled by user [arg1].

Severity: Info

Description: IPv6 statless auto-assignment
method is enabled by user.

Action: No action; information only.

Event ID: 40000034-00000000

Message: IPv6 static IP configuration disabled
by user [arg1].

Severity: Info

Description: IPv6 static assignment method is
disabled by user.

Action: No action; information only.

Event ID: 40000035-00000000

Message: IPv6 DHCP disabled by user [arg1].

Severity: Info

Description: IPv6 DHCP assignment method is
disabled by user.

Action: No action; information only.

Event ID: 40000036-00000000

Message: IPv6 stateless auto-configuration
disabled by user [arg1].

Severity: Info

Description: IPv6 statless auto-assignment
method is disabled by user.

Action: No action; information only.

Event ID: 40000037-00000000

Message: ENET[[arg1]] IPv6-
LinkLocal:HstName=[arg2], IP@=[arg3] ,Pref=[arg4].

Severity: Info

Description: IPv6 Link Local address is
active.

Action: No action; information only.

Event ID: 40000038-00000000

Message: ENET[[arg1]] IPv6-
Static:HstName=[arg2], IP@=[arg3],Pref=[arg4], GW@=[arg5].

Severity: Info

Description: IPv6Static address is active.

Action: No action; information only.

Event ID: 40000039-00000000

Message: ENET[[arg1]] DHCPv6- HSTN=[arg2],
DN=[arg3], IP@=[arg4], Pref=[arg5].

Severity: Info

Description: IPv6 DHCP-assigned address is
active.

Action: No action; information only.

Event ID: 4000003a-00000000

Message: IPv6 static address of network
interface modified from [arg1] to [arg2] by user [arg3].

Severity: Info

Description: A user modifies the IPv6 static
address of a Management Controller.

Action: No action; information only.

Event ID: 4000003b-00000000

Message: DHCPv6 failure, no IP address
assigned.

Severity: Warning

Description: S DHCP6 server fails to assign an
IP address to a Management Controller.

Action: No action; information only.

Event ID: 4000003c-00000000

Message: Platform Watchdog Timer expired for
[arg1].

Severity: Error

Description: A user has modified the telnet
port number.

Action: No action; information only.

Event ID: 4000003e-00000000

Message: SSH port number changed from [arg1] to
[arg2] by user [arg3].

Severity: Info

Description: A user has modified the SSH port
number.

Action: No action; information only.

Event ID: 4000003f-00000000

Message: Web-HTTP port number changed from
[arg1] to [arg2] by user [arg3].

Severity: Info

Description: A user has modified the Web HTTP
port number.

Action: No action; information only.

Event ID: 40000040-00000000

Message: Web-HTTPS port number changed from
[arg1] to [arg2] by user [arg3].

Severity: Info

Description: A user has modified the Web HTTPS
port number.

Action: No action; information only.

Event ID: 40000041-00000000

Message: CIM/XML HTTP port number changed from
[arg1] to [arg2] by user [arg3].

Severity: Info

Description: A user has modified the CIM HTTP
port number.

Action: No action; information only.

Event ID: 40000042-00000000

Message: CIM/XML HTTPS port number changed from
[arg1] to [arg2] by user [arg3].

Severity: Info

Description: A user has modified the CIM HTTPS
port number.

Action: No action; information only.

Event ID: 40000043-00000000

Message: SNMP Agent port number changed from
[arg1] to [arg2] by user [arg3].

Severity: Info

Description: A user has modified the SNMP Agent
port number.

Action: No action; information only.

Event ID: 40000044-00000000

Message: SNMP Traps port number changed from
[arg1] to [arg2] by user [arg3].

Severity: Info

Description: A user has modified the SNMP Traps
port number.

Action: No action; information only.

Event ID: 40000045-00000000

Message: Syslog port number changed from [arg1]
to [arg2] by user [arg3].

Severity: Info

Description: A user has modified the Syslog
receiver port number.

Action: No action; information only.

Event ID: 40000046-00000000

Message: Remote Presence port number changed
from [arg1] to [arg2] by user [arg3].

Severity: Info

Description: A user has modified the Remote
Presence port number.

Action: No action; information only.

Event ID: 40000047-00000000

Message: LED [arg1] state changed to [arg2] by
[arg3].

Severity: Info

Description: A user has modified the state of
an LED.

Action: No action; information only.

Event ID: 40000048-00000000

Message: Inventory data changed for device
[arg1], new device data hash=[arg2], new master data
hash=[arg3].

Severity: Info

Description: Something has caused the physical
inventory to change.

Action: No action; information only.

Event ID: 40000049-00000000

Message: SNMP [arg1] enabled by user
[arg2].

Severity: Info

Description: A user enabled SNMPv1 or SNMPv3 or
Traps.

Action: No action; information only.

Event ID: 4000004a-00000000

Message: SNMP [arg1] disabled by user [arg2]
.

Severity: Info

Description: A user disabled SNMPv1 or SNMPv3
or Traps.

Action: No action; information only.

Event ID: 4000004b-00000000

Message: SNMPv1 [arg1] set by user [arg2]:
Name=[arg3], AccessType=[arg4], Address=[arg5].

Severity: Info

Description: A user changed the SNMP community
string.

Action: No action; information only.

Event ID: 4000004c-00000000

Message: LDAP Server configuration set by user
[arg1]: SelectionMethod=[arg2], DomainName=[arg3], Server1=[arg4],
Server2=[arg5], Server3=[arg6], Server4=[arg7].

Severity: Info

Description: A user changed the LDAP server
configuration.

Action: No action; information only.

Event ID: 4000004d-00000000

Message: LDAP set by user [arg1]:
RootDN=[arg2], UIDSearchAttribute=[arg3], BindingMethod=[arg4],
EnhancedRBS=[arg5], TargetName=[arg6], GroupFilter=[arg7],
GroupAttribute=[arg8], LoginAttribute=[arg9].

Severity: Info

Description: A user configured an LDAP
Miscellaneous setting.

Action: No action; information only.

Event ID: 4000004e-00000000

Message: Serial Redirection set by user [arg1]:
Mode=[arg2], BaudRate=[arg3], StopBits=[arg4], Parity=[arg5],
SessionTerminateSequence=[arg6].

Severity: Info

Description: A user configured the Serial Port
mode.

Action: No action; information only.

Event ID: 4000004f-00000000

Message: Date and Time set by user [arg1]:
Date=[arg2], Time-[arg3], DST Auto-adjust=[arg4],
Timezone=[arg5].

Severity: Info

Description: A user configured the Date and
Time settings.

Action: No action; information only.

Event ID: 40000050-00000000

Message: Server General Settings set by user
[arg1]: Name=[arg2], Contact=[arg3], Location=[arg4], Room=[arg5],
RackID=[arg6], Rack U-position=[arg7].

Severity: Info

Description: A user configured the Location
setting.

Action: No action; information only.

Event ID: 40000051-00000000

Message: Server Power Off Delay set to [arg1]
by user [arg2].

Severity: Info

Description: A user configured the Server Power
Off Delay.

Action: No action; information only.

Event ID: 40000052-00000000

Message: Server [arg1] scheduled for [arg2] at
[arg3] by user [arg4].

Severity: Info

Description: A user configured a Server Power
action at a specific time.

Action: No action; information only.

Event ID: 40000053-00000000

Message: Server [arg1] scheduled for every
[arg2] at [arg3] by user [arg4].

Severity: Info

Description: A user configured a recurring
Server Power Action.

Action: No action; information only.

Event ID: 40000054-00000000

Message: Server [arg1] [arg2] cleared by user
[arg3].

Severity: Info

Description: A user cleared a Server Power
Action.

Action: No action; information only.

Event ID: 40000055-00000000

Message: Synchronize time setting by user
[arg1]: Mode=[arg2],
NTPServerHost=[arg3]:[arg4],NTPUpdateFrequency=[arg5].

Severity: Info

Description: A user configured the Date and
Time synchronize settings.

Action: No action; information only

Event ID: 40000056-00000000

Message: SMTP Server set by user [arg1] to
[arg2]:[arg3].

Severity: Info

Description: A user configured the SMTP
server.

Action: No action; information only.

Event ID: 40000057-00000000

Message: Telnet [arg1] by user [arg2].

Severity: Info

Description: A user enables or disables Telnet
services.

Action: No action; information only.

Event ID: 40000058-00000000

Message: DNS servers set by user [arg1]:
UseAdditionalServers=[arg2], PreferredDNStype=[arg3],
IPv4Server1=[arg4], IPv4Server2=[arg5], IPv4Server3=[arg6],
IPv6Server1=[arg7], IPv6Server2=[arg8], IPv6Server3=[arg9].

Severity: Info

Description: A user configures the DNS
servers.

Action: No action; information only.

Event ID: 40000059-00000000

Message: LAN over USB [arg1] by user
[arg2].

Severity: Info

Description: A user configured USB-LAN.

Action: No action; information only.

Event ID: 4000005a-00000000

Message: LAN over USB Port Forwarding set by
user [arg1]: ExternalPort=[arg2], USB-LAN port=[arg3].

Severity: Info

Description: A user configured USB-LAN port
forwarding.

Action: No action; information only.

Event ID: 4000005b-00000000

Message: Secure Web services (HTTPS) [arg1] by
user [arg2].

Severity: Info

Description: A user enables or disables Secure
web services.

Action: No action; information only.

Event ID: 4000005c-00000000

Message: Secure CIM/XML(HTTPS) [arg1] by user
[arg2].

Severity: Info

Description: A user enables or disables Secure
CIM/XML services.

Action: No action; information only.

Event ID: 4000005d-00000000

Message: Secure LDAP [arg1] by user [arg2].

Severity: Info

Description: A user enables or disables Secure
LDAP services.

Action: No action; information only.

Event ID: 4000005e-00000000

Message: SSH [arg1] by user [arg2].

Severity: Info

Description: A user enables or disables SSH
services.

Action: No action; information only.

Event ID: 4000005f-00000000

Message: Server timeouts set by user [arg1]:
EnableOSWatchdog=[arg2], OSWatchdogTimout=[arg3],
EnableLoaderWatchdog=[arg4], LoaderTimeout=[arg5].

Severity: Info

Description: A user configures Server
Timeouts.

Action: No action; information only.

Event ID: 40000060-00000000

Message: License key for [arg1] added by user
[arg2].

Severity: Info

Description: A user installs License Key.

Action: No action; information only.

Event ID: 40000061-00000000

Message: License key for [arg1] removed by user
[arg2].

Severity: Info

Description: A user removes a License Key.

Action: No action; information only.

Event ID: 40000062-00000000

Message: Global Login General Settings set by
user [arg1]: AuthenticationMethod=[arg2], LockoutPeriod=[arg3],
SessionTimeout=[arg4].

Severity: Info

Description: A user changes the Global Login
General Settings.

Action: No action; information only.

Event ID: 40000063-00000000

Message: Global Login Account Security set by
user [arg1]: PasswordRequired=[arg2],
PasswordExpirationPeriod=[arg3], MinimumPasswordReuseCycle=[arg4],
MinimumPasswordLength=[arg5], MinimumPasswordChangeInterval=[arg6],
MaxmumLoginFailures=[arg7], LockoutAfterMaxFailures=[arg8],
MinimumDifferentCharacters=[arg9], DefaultIDExpired=[arg10],
ChangePasswordFirstAccess=[arg11].

Severity: Info

Description: A user changes the Global Login
Account Security Settings to Legacy.

Action: No action; information only.

Event ID: 40000064-00000000

Message: User [arg1] created.

Severity: Info

Description: A user account was created.

Action: No action; information only.

Event ID: 40000065-00000000

Message: User [arg1] removed.

Severity: Info

Description: A user account was deleted.

Action: No action; information only.

Event ID: 40000066-00000000

Message: User [arg1] modified.

Severity: Info

Description: A user account was changed.

Action: No action; information only.

Event ID: 40000067-00000000

Message: User [arg1] role set to [arg2].

Severity: Info

Description: A user account role assigned.

Action: No action; information only.

Event ID: 40000068-00000000

Message: User [arg1] custom privileges set:
[arg2].

Severity: Info

Description: User account priveleges
assigned.

Action: No action; information only.

Event ID: 40000069-00000000

Message: User [arg1] for SNMPv3 set:
AuthenticationProtocol=[arg2], PrivacyProtocol=[arg3],
AccessType=[arg4], HostforTraps=[arg5].

Severity: Info

Description: User account SNMPv3 settings
changed.

Action: No action; information only.

Event ID: 4000006a-00000000

Message: SSH Client key added for user
[arg1].

Severity: Info

Description: User locally defined an SSH Client
key.

Action: No action; information only.

Event ID: 4000006b-00000000

Message: SSH Client key imported for user
[arg1] from [arg2].

Severity: Info

Description: User imported an SSH Client
key.

Action: No action; information only.

Event ID: 4000006c-00000000

Message: SSH Client key removed from user
[arg1].

Severity: Info

Description: User removed an SSH Client
key.

Action: No action; information only.

Event ID: 4000006d-00000000

Message: Management Controller [arg1]:
Configuration saved to a file by user [arg2].

Severity: Info

Description: A user saves a Management
Controller configuration to a file.

Action: No action; information only.

Event ID: 4000006e-00000000

Message: Alert Configuration Global Event
Notification set by user [arg1]: RetryLimit=[arg2],
RetryInterval=[arg3], EntryInterval=[arg4].

Severity: Info

Description: A user changes the Global Event
Notification settings.

Action: No action; information only.

Event ID: 4000006f-00000000

Message: Alert Recipient Number [arg1] updated:
Name=[arg2], DeliveryMethod=[arg3], Address=[arg4],
IncludeLog=[arg5], Enabled=[arg6], EnabledAlerts=[arg7],
AllowedFilters=[arg8].

Severity: Info

Description: A user adds or updates an Alert
Recipient.

Action: No action; information only.

Event ID: 40000070-00000000

Message: SNMP Traps enabled by user [arg1]:
EnabledAlerts=[arg2], AllowedFilters=[arg3].

Severity: Info

Description: A user enabled the SNMP Traps
configuration.

Action: No action; information only.

Event ID: 40000071-00000000

Message: The power cap value changed from
[arg1] watts to [arg2] watts by user [arg3].

Severity: Info

Description: Power Cap values changed by
user.

Action: No action; information only.

Event ID: 40000072-00000000

Message: The minimum power cap value changed
from [arg1] watts to [arg2] watts.

Severity: Info

Description: Minimum Power Cap value
changed.

Action: No action; information only.

Event ID: 40000073-00000000

Message: The maximum power cap value changed
from [arg1] watts to [arg2] watts.

Severity: Info

Description: Maximum Power Cap value
changed.

Action: No action; information only.

Event ID: 40000074-00000000

Message: The soft minimum power cap value
changed from [arg1] watts to [arg2] watts.

Severity: Info

Description: Soft Minimum Power Cap value
changed.

Action: No action; information only.

Event ID: 40000075-00000000

Message: The measured power value exceeded the
power cap value.

Severity: Warning

Description: Power exceeded cap.

Action: No action; information only.

Event ID: 40000076-00000000

Message: The new minimum power cap value
exceeded the power cap value.

Severity: Warning

Description: Minimum Power Cap exceeds Power
Cap.

Action: No action; information only.

Event ID: 40000077-00000000

Message: Power capping was activated by user
[arg1].

Severity: Info

Description: Power capping activated by
user.

Action: No action; information only.

Event ID: 40000078-00000000

Message: Power capping was deactivated by user
[arg1].

Severity: Info

Description: Power capping deactivated by
user.

Action: No action; information only.

Event ID: 40000079-00000000

Message: Static Power Savings mode has been
turned on by user [arg1].

Severity: Info

Description: Static Power Savings mode turned
on by user.

Action: No action; information only.

Event ID: 4000007a-00000000

Message: Static Power Savings mode has been
turned off by user [arg1].

Severity: Info

Description: Static Power Savings mode turned
off by user.

Action: No action; information only.

Event ID: 4000007b-00000000

Message: Dynamic Power Savings mode has been
turned on by user [arg1].

Severity: Info

Description: Dynamic Power Savings mode turned
on by user.

Action: No action; information only.

Event ID: 4000007c-00000000

Message: Dynamic Power Savings mode has been
turned off by user [arg1].

Severity: Info

Description: Dynamic Power Savings mode turned
off by user.

Action: No action; information only.

Event ID: 4000007d-00000000

Message: Power cap and external throttling
occurred.

Severity: Info

Description: Power cap and external throttling
occurred.

Action: No action; information only.

Event ID: 4000007e-00000000

Message: External throttling occurred.

Severity: Info

Description: External throttling occurred.

Action: No action; information only.

Event ID: 4000007f-00000000

Message: Power cap throttling occurred.

Severity: Info

Description: Power cap throttling occurred.

Action: No action; information only.

Event ID: 40000080-00000000

Message: Remote Control session started by user
[arg1] in [arg2] mode.

Severity: Info

Description: Remote Control session started

Action: No action; information only.

Event ID: 40000081-00000000

Message: PXE boot requested by user [arg1].

Severity: Info

Description: PXE boot requested.

Action: No action; information only.

Event ID: 40000082-00000000

Message: The measured power value has returned
below the power cap value.

Severity: Info

Description: Power exceeded cap recovered.

Action: No action; information only.

Event ID: 40000083-00000000

Message: The new minimum power cap value has
returned below the power cap value.

Severity: Info

Description: Minimum Power Cap exceeds Power
Cap recovered

Action: No action; information only.

Event ID: 40000084-00000000

Message: IMM firmware mismatch between nodes
[arg1] and [arg2]. Please attempt to flash the IMM firmware to the
same level on all nodes.

Severity: Info

Description: A mismatch of IMM firmware has
been detected between nodes.

Action: No action; information only.

Event ID: 40000085-00000000

Message: FPGA firmware mismatch between nodes
[arg1] and [arg2]. Please attempt to flash the FPGA firmware to the
same level on all nodes.

Severity: Error

Description: A mismatch of FPGA firmware has
been detected between nodes.

Action: No action; information only.

Event ID: 40000086-00000000

Message: Test Call Home Generated by user
[arg1].

Severity: Info

Description: Test Call Home generated by
user.

Action: No action; information only.

Event ID: 40000087-00000000

Message: Manual Call Home by user [arg1]:
[arg2].

Severity: Info

Description: Manual Call Home by user.

Action: No action; information only.

Event ID: 40000088-00000000

Message: Management Controller [arg1]:
Configuration restoration from a file by user [arg2] completed.

Severity: Info

Description: This message is for the use case
where a user restores a Management Controller configuration from a
file and it completes.

Action: No action; information only.

Event ID: 40000089-00000000

Message: Management Controller [arg1]:
Configuration restoration from a file by user [arg2] failed to
complete.

Severity: Info

Description: This message is for the use case
where a user restores a Management Controller configuration from a
file and the restoration fails to complete.

Action: No action; information only.

Event ID: 4000008a-00000000

Message: Management Controller [arg1]:
Configuration restoration from a file by user [arg2] failed to
start.

Severity: Info

Description: This message is for the use case
where a user restores a Management Controller configuration from a
file and the restoration fails to start.

Action: No action; information only.

Event ID: 4000008b-00000000

Message: One or more of the Storage Management
IP addresses has changed.

Severity: Info

Description: This message is for the use case
where an IP address for the Storage Management has changed.

Action: No action; information only.

DSA messages

Message number: 089-801-xxx

Component: CPU

Test: CPU Stress Test

State: Aborted

Description: Internal program error.

Action:

1. Turn off and restart the system.
2. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
3. Run the test again.
4. Make sure that the system firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component.
5. Run the test again.
6. Turn off and restart the system if necessary to recover from a
   hung state.
7. Run the test again.
8. If the failure remains, go to the IBM Web site for more
   troubleshooting information at http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 089-802-xxx

Component: CPU

Test: CPU Stress Test

State: Aborted

Description: System resource availability
error.

Action:

1. Turn off and restart the system.
2. Make sure that the DSA code is at the latest level. For the
   latest level of DSAcode, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
3. Run the test again.
4. Make sure that the system firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For the latest level of
   firmware, go to http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4JTS2T
   and select your system to display a matrix of available firmware.
   For more information, see «Updating the firmware» section in the
   Installation and Service Guide — IBM System x3300 M4 (7382).
5. Run the test again.
6. Turn off and restart the system if necessary to recover from a
   hung state.
7. Run the test again.
8. Make sure that the system firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For the latest level of
   firmware, go to http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4JTS2T
   and select your system to display a matrix of available firmware.
   For more information, see «Updating the firmware» section in the
   Installation and Service Guide — IBM System x3300 M4 (7382).
9. Run the test again.
10. If the failure remains, go to the IBM Web site for more
    troubleshooting information at
    http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 089-901-xxx

Component: CPU

Test: CPU Stress Test

State: Failed

Description: Test failure.

Action:

1. Turn off and restart the system if necessary to recover from a
   hung state.
2. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
3. Run the test again.
4. Make sure that the system firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
5. Run the test again.
6. Turn off and restart the system if necessary to recover from a
   hung state.
7. Run the test again.
8. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-801-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C test aborted:
the IMM returned an incorrect response length.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this
   component. For more information, see «Updating the firmware»
   section in the Installation and Service Guide — IBM System x3300 M4
   (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-802-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted:
the test cannot be completed for an unknown reason.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-803-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted:
the node is busy; try later.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-804-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted:
invalid command.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-805-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted:
invalid command for the given LUN.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-806-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted:
timeout while processing the command.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-807-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
out of space.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-808-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
reservation canceled or invalid reservation ID.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-809-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
request data was truncated.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-810-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
request data length is invalid.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-811-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
request data field length limit is exceeded.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-812-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
a parameter is out of range.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-813-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
cannot return the number of requested data bytes.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-814-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
requested sensor, data, or record is not present.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-815-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
invalid data field in the request.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-816-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
the command is illegal for the specified sensor or record type.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-817-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
a command response could not be provided.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-818-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
cannot execute a duplicated request.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-819-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
a command response could not be provided; the SDR repository is in
update mode.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-820-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
a commandresponse could not be provided; the device is in firmware
update mode.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-821-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
a command response could not be provided; IMM initialization is in
progress.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-822-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
the destination is unavailable.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-823-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test aborted :
cannot execute the command; insufficient privilege level.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-824-xxx

Component: IMM

Test: IMM I²C Test

State: Aborted

Description: IMM I²C Test cancelled
: cannot execute the command.

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-901-xxx

Component: IMM

Test: IMM I²C Test

State: Failed

Description: IMM indicates failure in RTMM bus
(BUS 0).

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
4. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
5. Run the test again.
6. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-904-xxx

Component: IMM

Test: IMM I²C Test

State: Failed

Description: IMM indicates failure in PCA9545
(I2C I/O Expander) bus (BUS 3).

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
4. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
5. Run the test again.
6. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-905-xxx

Component: IMM

Test: IMM I²C Test

State: Failed

Description: IMM Indicates failure in the PIC
16F887 (Power Paddle Card) bus (BUS 4).

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
4. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
5. Run the test again.
6. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-907-xxx

Component: IMM

Test: IMM I²C Test

State: Failed

Description: IMM Indicates failure in the LM75
(Thermal Sensor) bus (BUS 6).

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
4. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
5. Run the test again.
6. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 166-908-xxx

Component: IMM

Test: IMM I²C Test

State: Failed

Description: IMM Indicates failure in the
PCA9539 (I2C I/O Expander) bus (BUS 7).

Action:

1. Turn off the system and disconnect it from the power source.
   You must disconnect the system from ac power to reset the
   IMM2.
2. After 45 seconds, reconnect the system to the power source and
   turn on the system.
3. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
4. Make sure that the IMM2 firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
5. Run the test again.
6. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-801-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test canceled: the system UEFI
programmed the memory controller with an invalid CBAR address

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
4. Run the test again.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-802-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test canceled: the end address in
the E820 function is less than 16 MB.

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
4. Run the test again.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-803-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test canceled: could not enable
the processor cache.

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
4. Run the test again.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-804-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test canceled: the memory
controller buffer request failed.

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
4. Run the test again.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-805-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test canceled: the memory
controller display/ alter write operation was not completed.

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
4. Run the test again.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-806-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test canceled: the memory
controller fast scrub operation was not completed.

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
4. Run the test again.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-807-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test canceled: the memory
controller buffer free request failed.

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
4. Run the test again.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-808-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test canceled: memory controller
display/ alter buffer execute error.

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
4. Run the test again.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-809-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test canceled program error:
operation running fast scrub.

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
4. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
5. Run the test again.
6. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-810-xxx

Component: Memory

Test: Memory Test

State: Aborted

Description: Test stopped: unknown error code
xxx received in COMMONEXIT procedure.

Action:

1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
4. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
5. Run the test again.
6. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 201-901-xxx

Component: Memory

Test: Memory Test

State: Failed

Description: Test failure: single-bit error,
failing DIMM z.

Action:

1. Turn off the system and disconnect it from the power
   source.
2. Reseat DIMM z.
3. Reconnect the system to power and turn on the system.
4. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
5. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
6. Run the test again.
7. Replace the failing DIMMs.
8. Re-enable all memory in the Setup utility. For more
   information, see «Using the Setup utility» section in the
   Installation and Service Guide — IBM System x3300 M4 (7382).
9. Run the test again.
10. Replace the failing DIMM.
11. Re-enable all memory in the Setup utility. For more
    information, see «Using the Setup utility» section in the
    Installation and Service Guide — IBM System x3300 M4 (7382).
12. Run the test again.
13. If the failure remains, go to the IBM Web site for more
    troubleshooting information at
    http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 202-801-xxx

Component: Memory

Test: Memory Stress Test

State: Aborted

Description: Internal program error.

Action:

1. Turn off and restart the system.
2. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/
   support/docview.wss?uid=psg1SERVDSA.
3. Make sure that the server firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
4. Run the test again.
5. Turn off and restart the system if necessary to recover from a
   hung state.
6. Run the memory diagnostics to identify the specific failing
   DIMM.
7. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 202-802-xxx

Component: Memory

Test: Memory Stress Test

State: Failed

Description: General error: memory size is
insufficient to run the test.

Action:

1. Make sure that all memory is enabled by checking the Available
   System Memory in the Resource Utilization section of the DSA event
   log. If necessary, enable all memory in the Setup utility. For more
   information, see «Updating the firmware» section in the
   Installation and Service Guide — IBM System x3300 M4 (7382).
2. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
3. Run the test again.
4. Run the standard memory test to validate all memory.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 202-901-xxx

Component: Memory

Test: Memory Stress Test

State: Failed

Description: Test failure.

Action:

1. Run the standard memory test to validate all memory.
2. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
3. Turn off the system and disconnect it from power.
4. Reseat the DIMMs.
5. Reconnect the system to power and turn on the system.
6. Run the test again.
7. Run the standard memory test to validate all memory.
8. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 215-801-xxx

Component: Optical Drive

Test:

• Verify Media Installed
• Read/ Write Test
• Self-Test

Messages and actions apply to all three tests.

State: Aborted

Description: Unable to communicate with the
device driver.

Action:

1. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to
   http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
2. Run the test again.
3. Check the drive cabling at both ends for loose or broken
   connections or damage to the cable. Replace the cable if it is
   damaged.
4. Run the test again.
5. For additional troubleshooting information, go to
   http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-41559.
6. Run the test again.
7. Make sure that the system firmware is at the latest level. The
   installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
8. Run the test again.
9. Replace the DVD drive.
10. If the failure remains, go to the IBM Web site for more
    troubleshooting information at
    http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 215-802-xxx

Component: Optical Drive

Test:

• Verify Media Installed
• Read/ Write Test
• Self-Test

Messages and actions apply to all three tests.

State: Aborted

Description: The media tray is open.

Action:

1. Close the media tray and wait 15 seconds.
2. Run the test again.
3. Insert a new CD/DVD into the drive and wait for 15 seconds for
   the media to be recognized.
4. Run the test again.
5. Check the drive cabling at both ends for loose or broken
   connections or damage to the cable. Replace the cable if it is
   damaged.
6. Run the test again.
7. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
8. Run the test again.
9. For additional troubleshooting information, go to
   http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-41559.
10. Run the test again.
11. Replace the CD/DVD drive.
12. If the failure remains, go to the IBM Web site for more
    troubleshooting information at
    http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 215-803-xxx

Component: Optical Drive

Test:

• Verify Media Installed
• Read/ Write Test
• Self-Test

Messages and actions apply to all three tests.

State: Failed

Description: The disc might be in use by the
system.

Action:

1. Wait for the system activity to stop.
2. Run the test again.
3. Turn off and restart the system.
4. Run the test again.
5. Replace the DVD drive.
6. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 215-901-xxx

Component: Optical Drive

Test:

• Verify Media Installed
• Read/ Write Test
• Self-Test

Messages and actions apply to all three tests.

State: Aborted

Description: Drive media is not detected.

Action:

1. Insert a CD/DVD into the DVD drive or try a new media, and wait
   for 15 seconds.
2. Run the test again.
3. Check the drive cabling at both ends for loose or broken
   connections or damage to the cable. Replace the cable if it is
   damaged.
4. Run the test again.
5. For additional troubleshooting information, go to
   http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-41559.
6. Run the test again.
7. Replace the DVD drive.
8. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 215-902-xxx

Component: Optical Drive

Test:

• Verify Media Installed
• Read/ Write Test
• Self-Test

Messages and actions apply to all three tests.

State: Failed

Description: Read miscompare.

Action:

1. Insert a CD/DVD into the drive or try a new media, and wait for
   15 seconds.
2. Run the test again.
3. Check the drive cabling at both ends for loose or broken
   connections or damage to the cable. Replace the cable if it is
   damaged.
4. Run the test again.
5. For additional troubleshooting information, go to
   http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-41559.
6. Run the test again.
7. Replace the DVD drive.
8. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 215-903-xxx

Component: Optical Drive

Test:

• Verify Media Installed
• Read/ Write Test
• Self-Test

Messages and actions apply to all three tests.

State: Aborted

Description: Could not access the drive.

Action:

1. Insert a CD/DVD into the drive or try a new media, and wait for
   15 seconds.
2. Run the test again.
3. Check the drive cabling at both ends for loose or broken
   connections or damage to the cable. Replace the cable if it is
   damaged.
4. Run the test again.
5. Make sure that the DSA code is at the latest level. For the
   latest level of DSA code, go to http://www.ibm.com/support/docview.wss?uid=psg1SERVDSA.
6. Run the test again.
7. For additional troubleshooting information, go to
   http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-41559.
8. Run the test again.
9. Replace the DVD drive.
10. If the failure remains, go to the IBM Web site for more
    troubleshooting information at
    http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 215-904-xxx

Component: Optical Drive

Test:

• Verify Media Installed
• Read/ Write Test
• Self-Test

Messages and actions apply to all three tests.

State: Failed

Description: A read error occurred.

Action:

1. Insert a CD/DVD into the drive or try a new media, and wait for
   15 seconds.
2. Run the test again.
3. Check the drive cabling at both ends for loose or broken
   connections or damage to the cable. Replace the cable if it is
   damaged.
4. Run the test again.
5. For additional troubleshooting information, go to
   http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-41559.
6. Run the test again.
7. Replace the DVD drive.
8. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 405-901-xxx

Component: Optical Drive

Test:

• Verify Media Installed
• Read/ Write Test
• Self-Test

Messages and actions apply to all three tests.

State: Failed

Description: A read error occurred.

Action:

1. Insert a CD/DVD into the drive or try a new media, and wait for
   15 seconds.
2. Run the test again.
3. Check the drive cabling at both ends for loose or broken
   connections or damage to the cable. Replace the cable if it is
   damaged.
4. Run the test again.
5. For additional troubleshooting information, go to
   http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-41559.
6. Run the test again.
7. Replace the DVD drive.
8. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 405-901-xxx

Component: Ethernet Device

Test: Test Control Registers

State: Failed

Description:

Action:

1. Make sure that the component firmware is at the latest level.
   The installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
2. Run the test again.
3. Replace the component that is causing the error. If the error
   is caused by an adapter, replace the adapter. Check the PCI
   Information and Network Settings information in the DSA event log
   to determine the physical location of the failing component.
4. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 405-902-xxx

Component: Ethernet Device

Test: Test EEPROM

State: Failed

Description:

Action:

1. Make sure that the component firmware is at the latest level.
   The installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
2. Run the test again.
3. Replace the component that is causing the error. If the error
   is caused by an adapter, replace the adapter. Check the PCI
   Information and Network Settings information in the DSA event log
   to determine the physical location of the failing component.
4. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 405-903-xxx

Component: Ethernet Device

Test: Test Internal Memory

State: Failed

Description:

Action:

1. Make sure that the component firmware is at the latest level.
   The installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
2. Run the test again.
3. Check the interrupt assignments in the PCI Hardware section of
   the DSA event log. If the Ethernet device is sharing interrupts, if
   possible, use the Setup utility see «Using the Setup utility»
   section in the Installation and Service Guide — IBM System x3300 M4
   (7382), to assign a unique interrupt to the device.
4. Replace the component that is causing the error. If the error
   is caused by an adapter, replace the adapter. Check the PCI
   Information and Network Settings information in the DSA event log
   to determine the physical location of the failing component.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 405-904-xxx

Component: Ethernet Device

Test: Test Interrupt

State: Failed

Description:

Action:

1. Make sure that the component firmware is at the latest level.
   The installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
2. Run the test again.
3. Check the interrupt assignments in the PCI Hardware section of
   the DSA event log. If the Ethernet device is sharing interrupts, if
   possible, use the Setup utility see «Using the Setup utility»
   section in the Installation and Service Guide — IBM System x3300 M4
   (7382), to assign a unique interrupt to the device.
4. Replace the component that is causing the error. If the error
   is caused by an adapter, replace the adapter. Check the PCI
   Information and Network Settings information in the DSA event log
   to determine the physical location of the failing component.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 405-905-xxx

Component: Ethernet Device

Test: Test Loop back at MAC Layer

State: Failed

Description:

Action:

1. Make sure that the component firmware is at the latest level.
   The installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
2. Run the test again.
3. Replace the component that is causing the error. If the error
   is caused by an adapter, replace the adapter. Check the PCI
   Information and Network Settings information in the DSA event log
   to determine the physical location of the failing component.
4. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 405-906-xxx

Component: Ethernet Device

Test: Test Loop back at Physical Layer

State: Failed

Description:

Action:

1. Check the Ethernet cable for damage and make sure that the
   cable type and connection are correct.
2. Make sure that the component firmware is at the latest level.
   The installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
3. Run the test again.
4. Replace the component that is causing the error. If the error
   is caused by an adapter, replace the adapter. Check the PCI
   Information and Network Settings information in the DSA event log
   to determine the physical location of the failing component.
5. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Message number: 405-907-xxx

Component: Ethernet Device

Test: Test LEDs

State: Failed

Description:

Action:

1. Make sure that the component firmware is at the latest level.
   The installed firmware level is shown in the DSA event log in the
   Firmware/VPD section for this component. For more information, see
   «Updating the firmware» section in the Installation and Service
   Guide — IBM System x3300 M4 (7382).
2. Run the test again.
3. Replace the component that is causing the error. If the error
   is caused by an adapter, replace the adapter. Check the PCI
   Information and Network Settings information in the DSA event log
   to determine the physical location of the failing component.
4. If the failure remains, go to the IBM Web site for more
   troubleshooting information at
   http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-CALL.

Материнские платы ошибки:

Код — Описание
Код ошибки 101 — Системная плата прерывать недостаточности (неожиданных прерываний)
Код ошибки 102 — BIOS ROM ошибка контрольной суммы (PC, XT); таймер ошибки (AT, MCA)
Код ошибки 103 — ROM BASIC ошибка контрольной суммы (PC, XT); прерыванием таймера ошибки (AT, MCA)
Код ошибки 104 — контроллер прерываний ошибки (PC, XT); защищенном режиме ошибки (AT, MCA)
Код ошибки 105 — Таймер недостаточности (PC, XT); 8042 контроллер клавиатуры недостаточности (MCA)
Код ошибки 106 — Системная плата преобразования логики провал испытаний
Код ошибки 107 — системной платы без прерывания maskable (НМИ) тест недостаточность; Горячие НМИ провал испытаний (MCA)
Код ошибки 108 — системной платы таймера тест шины провал
Код ошибки 109 — тест памяти DMA выберите провал
Код ошибки 110 — PS / 2 системной плате ошибка четности (MCA); PS / 2 системной плате ошибок памяти (ISA)
Код ошибки 111 — PS / 2 адаптер памяти задачи (ISA); PS / 2 I / O каналов ошибка четности (MCA)
Код ошибки 112 — PS / 2 тайм-аут таймера ошибки (НМИ)
Код ошибки 113 — PS / 2 DMA арбитражного ошибки тайм-аут (НМИ)
Код ошибки 114 — PS / 2 внешних ошибка контрольной суммы ROM
Код ошибки 115 — BIOS ROM ошибка контрольной суммы, ошибка четности кэш, либо ошибка DMA
Код ошибки 116 — системной платы для чтения / записи ошибке
Код ошибки 118 — системной платы четности или L2 кэш ошибке
Код ошибки 119 — 2.88MB дискеты установлен, но не поддерживает контроллер гибких дисков
Код ошибки 120 — CPU самостоятельной ошибка тест
Код ошибки 121 — Неожиданный аппаратное прерывание произошло; 256KB ошибка контрольной суммы ROM (128 Кб второго банка)
Код ошибки 129 — Отсутствие системной платы
Код ошибки 131 — Кассетный упаковка теста; регистров DMA совместимость ошибке
Код ошибки 132 — DMA расширенных регистров ошибке
Код ошибки 133 — DMA проверить логическую ошибку
Код ошибки 134 — ошибка арбитражного DMA
Код ошибки 151 — батарейки, часы реального времени, или CMOS RAM провал
Код ошибки 152 — Часы реального времени, или CMOS RAM провал
Код ошибки 160 — PS / 2 ID системной платы не признаются
Код ошибки 161 — CMOS конфигурации потерял (аккумулятор умер)
Код ошибки 162 — ошибка контрольной суммы CMOS, КПР ошибку, или адаптер ID несоответствие
Код ошибки 163 — CMOS ошибка; часы не обновляется
Код ошибки 164 — CMOS ошибка; CMOS настройки не соответствует памяти на системной плате
Код ошибки 165 — PS / 2 адаптер ID несоответствие
Код ошибки 166 — PS / 2 адаптер тайм-аут, карточные занят
Код ошибки 167 — PS / 2 с системными часами не обновлялось
Код ошибки 168 — математический сопроцессор ошибки в конфигурации CMOS
Код ошибки 169 — системной платы и процессора карты конфигурации несоответствие
Код ошибки 170 — ASCII установки конфликта ошибке
Код ошибки 171 — прокатный бит испытаний аварии на байт выключения CMOS
Код ошибки 172 — прокатный бит испытаний аварии на NVRAM диагностических байт
Код ошибки 173 — Bad CMOS / NVRAM контрольной
Код ошибки 174 — Неправильная конфигурация системы
Код ошибки 175 — Bad EEPROM Конвенции о правах ребенка
Код ошибки 177 — Bad пароль Конвенции о правах ребенка
Код ошибки 178 — Bad EEPROM
Код ошибки 179 — NVRAM полный журнал ошибок
Код ошибки 180x — Sub адрес дата ошибку в слот х
Код ошибки 181 — Неподдерживаемый конфигурации
Код ошибки 182 — Пароль переключатель не в письменной форме позиции
Код ошибки 183 — Система остановились, пароль не требуется
Код ошибки 184 — Bad власть на пароль
Код ошибки 185 — Bad последовательность запуска
Код ошибки 186 — Защита паролем Аппаратная ошибка
Код ошибки 187 — серийный номер ошибки
Код ошибки 188 — Неправильная контрольная сумма EEPROM
Код ошибки 189 — Слишком много неудачных попыток ввести пароль
Код ошибки 191 — Cache тест контроллера не удалось
Код ошибки 194 — Система встроенной памяти ошибке
Код ошибки 195 — Конфигурация читать от зимней спячки области HDD не соответствует фактической конфигурации
Код ошибки 196 — Произошла ошибка чтения в спящем области HDD
Код ошибки 199 — пользователь указал списке устройств не правильно

Память ошибок на IBM
Ошибки памяти

Код — Описание

Код ошибки 20x — Memory ошибке
Код ошибки 201 — Тест памяти недостаточность; место ошибка может отображаться
Код ошибки 202 — Memory адрес ошибки; линии 00-15
Код ошибки 203 — Memory адрес ошибки; линии 16-23 (ISA) и 16-31 (MCA)
Код ошибки 204 — Memory переназначен из-за ошибки (запустить диагностику еще раз)
Код ошибки 205 — 128 КБ памяти базы ошибка, память переназначен
Код ошибки 207 — ROM провал
Код ошибки 210 — системной платы памяти, ошибка четности
Код ошибки 211 — Ошибка в первых 64 Кб оперативной памяти
Код ошибки 212 — Watchdog таймер ошибке
Код ошибки 213 — DMA арбитража шины тайм-аут
Код ошибки 215 — Memory адрес ошибки; 64 Кб на дочери / SIP 2 не удалось
Код ошибки 216 — Memory адрес ошибки; 64 Кб на дочери / SIP 1 не удалось
Код ошибки 221 — ROM в RAM копию не удалось
Код ошибки 225 — Неправильно скорости памяти на системной плате
Код ошибки 229 — Memory Error
Код ошибки 230 — адаптер Перекрытие и плоских памяти
Код ошибки 231 — Номера непрерывной памяти адаптера, установленного
Код ошибки 235 — Stuck линия передачи данных на модуль памяти
Код ошибки 241 — 2 модуля памяти не удалось
Код ошибки 251 — для модулей памяти 3 не удалось
27-09-2008
IBM, клавиатуру, дисплей, адаптер и адаптер Ошибки Графика
Клавиатура ошибки:

Код — Описание

Код ошибки 301 — клавиатура не ответил правильно
Код ошибки 302 — клавиатура заблокирована
Код ошибки 303 — клавиатура и / или системной платы интерфейса ошибки; контроллер клавиатуры вине
Код ошибки 304 — клавиатура и системный блок ошибке
Код ошибки 305 — клавиатура предохранитель рухнул на системной плате
Код ошибки 306 — Неподдерживаемый клавиатуре прилагается
Код ошибки 341 — клавиатура ошибке
Код ошибки 342 — клавиатура кабель ошибке
Код ошибки 343 — карточка Повышение или кабельного ошибке
Код ошибки 365 — клавиатура провал
Код ошибки 366 — Интерфейсный кабель провал
Код ошибки 367 — карточка Повышение или кабельного провал

Монохромный адаптер Ошибки Дисплей:

Код — Описание

Код ошибки 401 — памяти, частота горизонтальной или вертикальной синхронизации отказ синхронизировать
Код ошибки 408 — Пользователь с ошибкой отображения атрибута
Код ошибки 416 — пользователь указал набор символов провал
Код ошибки 424 — пользователь указал 80 х 25 отказов
Код ошибки 432 — MDA карты провале испытаний порт

Цвет адаптер Ошибки графика:

Код — Описание

Код ошибки 501 — CRT ошибки; CGA памяти, частота горизонтальной синхронизации или видео-тест провал
Код ошибки 503 — контроллер CGA адаптер не удалось
Код ошибки 508 — Пользователь отображения атрибута провал
Код ошибки 516 — пользователь указал набор символов провал
Код ошибки 524 — пользователь указал 80 х 25 отказов
Код ошибки 532 — пользователь указал 40 х 25 отказов
Код ошибки 540 — пользователь указал 320 х 200 графический режим отказа
Код ошибки 548 — пользователь указал 640 х 200 графический режим отказа
Код ошибки 556 — пользователь указал легкий тест пера не удалось
Код ошибки 564 — Пользователь с ошибкой пейджинговая тест

Дисковод IBM, / Ошибки контроллер
Дисковод / Ошибки контроллер:

Код — Описание

Код ошибки 601 — Общие дискеты или адаптер провал
Код ошибки 602 — дискеты загрузочный сектор не действует
Код ошибки 603 — дискеты размером ошибке
Код ошибки 604 — Медиа смысле ошибке
Код ошибки 605 — дисковод закрывается
Код ошибки 606 — дискеты проверить тест не удалось
Код ошибки 607 — Напишите защитить ошибке
Код ошибки 608 — Привод команды ошибка
Код ошибки 610 — дискеты инициализации провал
Код ошибки 611 — Драйв тайм-аут ошибке
Код ошибки 612 — NEC контроллера диска IC ошибке
Код ошибки 613 — Floppy системы DMA ошибке
Код ошибки 614 — Floppy системы DMA границы ошибка переполнения
Код ошибки 615 — Привод индекс ошибка синхронизации
Код ошибки 616 — Управляйте скоростью ошибке
Код ошибки 621 — Привод искать ошибку
Код ошибки 622 — Привод циклическую проверку избыточности (КПР), ошибка
Код ошибки 625 — контроллер чипа (NEC) искать ошибку
Код ошибки 626 — дискеты данные сравнить ошибку
Код ошибки 627 — дискеты данные сравнить ошибку
Код ошибки 628 — дискеты удалены
Код ошибки 630 — Индекс застрял высоким, привод:
Код ошибки 631 — Индекс застрял низким, привод:
Код ошибки 632 — Track 0 застрял с, привод:
Код ошибки 632 — Track 0 застрял на, привод:
Код ошибки 640 — Индекс застрял высоким, привод B:
Код ошибки 641 — Индекс застрял низким, диск B:
Код ошибки 642 — Track 0 застрял с, привод B:
Код ошибки 643 — Track 0 застрял на; диск B:
Код ошибки 645 — не показатель импульса
Код ошибки 646 — Привод трек 0 ошибка определения
Код ошибки 647 — нет переходов на чтение данных в режиме реального
Код ошибки 648 — Формат тест не удалось
Код ошибки 649 — Неправильный тип носителя в приводе
Код ошибки 650 — Управляйте скоростью ошибке
Код ошибки 651 — Формат провал
Код ошибки 652 — Убедитесь, провал
Код ошибки 653 — Читать провал
Код ошибки 654 — Напишите провал
Код ошибки 655 — ошибка контроллера
Код ошибки 656 — Привод провал
Код ошибки 657 — Напишите защиты охраняемых застрял
Код ошибки 658 — Changeline застрял незащищенные
Код ошибки 659 — Создать охраняемые застрял незащищенные
Код ошибки 660 — Changeline застрял неизменной

Мать в IBM сопроцессора, параллельный и альтернативный адаптер ошибки принтера
Сопроцессор Ошибки Математика:

Код — Описание

Код ошибки 701 — мат наличие сопроцессора / инициализация ошибке
Код ошибки 702 — Исключение ошибки провал испытаний
Код ошибки 703 — Округление провал испытаний
Код ошибки 704 — Арифметический тест 1 провал
Код ошибки 705 — Арифметический тест 2 неудачи
Код ошибки 706 — Арифметический тест 3 недостаточность; испытание проводится на 80387 только
Код ошибки 707 — провал испытаний комбинации
Код ошибки 708 — Integer загрузки / сохранения провал испытаний
Код ошибки 709 — эквивалент выражения ошибки
Код ошибки 710 — Прерывание ошибки
Код ошибки 711 — ошибки Сохранить состояние
Код ошибки 712 — охраняемые провал тестовом режиме
Код ошибки 713 — Напряжение испытания провал

Параллельные Ошибки адаптер принтера:

Код — Описание

Код ошибки 901 — Данные регистра защелки ошибке
Код ошибки 902 — Управление регистр защелку ошибке
Код ошибки 903 — Регистрация декодирования адреса ошибке
Код ошибки 904 — Address ошибки декодирования
Код ошибки 910 — Статус перевод строки разъем ошибке
Код ошибки 911 — Статус битовом режиме 8 обертывание ошибке
Код ошибки 912 — Статус битовом режиме 7 обертывание ошибке
Код ошибки 913 — Статус битовом режиме 6 обертывание ошибке
Код ошибки 914 — Статус битовом режиме 5 упаковка ошибке
Код ошибки 915 — Статус битовом режиме 4 упаковка ошибке
Код ошибки 916 — принтер адаптера прерывания ошибки переполнения
Код ошибки 917 — Неожиданный адаптер принтера прерывания
Код ошибки 92x — Художественные регистр ошибок

Альтернативный адаптер ошибки принтера:

Код — Описание

Код ошибки 1001 — адаптер принтера данных регистра защелки ошибке
Код ошибки 1002 — адаптер для принтера управляющий регистр защелку ошибке
Код ошибки 1003 — принтер адаптер зарегистрировать адрес ошибки декодирования
Код ошибки 1004 — принтер адрес адаптера ошибки декодирования
Код ошибки 1010 — Статус перевод строки разъем ошибке
Код ошибки 1011 — Статус битовом режиме 8 обертывание ошибке
Код ошибки 1012 — Статус битовом режиме 7 обертывание ошибке
Код ошибки 1013 — Статус битовом режиме 6 обертывание ошибке
Код ошибки 1014 — Статус битовом режиме 5 упаковка ошибке
Код ошибки 1015 — Статус битовом режиме 4 упаковка ошибке
Код ошибки 1016 — принтер адаптера прерывания ошибки переполнения
Код ошибки 1017 — Неожиданный адаптер принтера прерывания
Код ошибки 102x — Художественные регистр ошибок

IBM’s Game контроля адаптер, матричный принтер и ДГМА Ошибки
Адаптер игры Ошибки управления:

Код — Описание

Код ошибки 1301 — Игра контроля адаптер провал испытаний
Код ошибки 1302 — джойстик провал испытаний

Принтер Ошибки Матрица:

Код — Описание

Код ошибки 1401 — принтер провал испытаний
Код ошибки 1402 — принтер не готов, а не на линии, или из бумаги
Код ошибки 1403 — принтер бумаги не ошибка
Код ошибки 1404 — матричный принтер тест недостаточность; системной плате тайм-аут
Код ошибки 1405 — Параллельные неудачи адаптер
Код ошибки 1406 — принтер проверка на присутствие не удалось

Дисплей Станция эмуляция адаптера (ДГМА) ошибки:

Код — Описание

Код ошибки 1604 — ДГМА или twinaxial ошибка сети
Код ошибки 1608 — ДГМА или twinaxial ошибка сети
Код ошибки 1624 — ДГМА ошибке
Код ошибки 1634 — ДГМА ошибке
Код ошибки 1644 — ДГМА ошибке
Код ошибки 1652 — ДГМА ошибке
Код ошибки 1654 — ДГМА ошибке
Код ошибки 1658 — ДГМА ошибке
Код ошибки 1662 — ДГМА прерывать уровень ошибок
Код ошибки 1664 — ДГМА ошибке
Код ошибки 1668 — ДГМА прерывать уровень ошибок
Код ошибки 1669 — ДГМА диагностики ошибок; использовать 3,0 или выше
Код ошибки 1674 — ДГМА диагностики ошибок; использовать 3,0 или выше; ДГМА адрес станции ошибке
Код ошибки 1684 — ДГМА адрес устройства ошибке
Код ошибки 1688 — ДГМА адрес устройства ошибке

Жесткий диск IBM и контроллер Ошибки
Жесткий диск и контроллер ошибки:

Код — Описание

Код ошибки 1701 — Исправлена ошибка диска или адаптера общая ошибка
Код ошибки 1702 — привод и контроллер тайм-аут ошибке
Код ошибки 1703 — Драйв искать ошибку
Код ошибки 1704 — контроллера диска не удалось
Код ошибки 1705 — Драйв сектора не найдена ошибка
Код ошибки 1706 — Ошибка записи вине
Код ошибки 1707 — Драйв трек 00 ошибки
Код ошибки 1708 — начальник выберите ошибке
Код ошибки 1709 — Bad ECC вернулся
Код ошибки 1710 — Сектор буфера
Код ошибки 1711 — Плохо знаком адрес
Код ошибки 1712 — диагностика внутреннего контроллера провал
Код ошибки 1713 — Данные сравнить ошибку
Код ошибки 1714 — Дисковод не готов
Код ошибки 1715 — Track 00 индикатор ошибки
Код ошибки 1716 — Диагностика цилиндра ошибки
Код ошибки 1717 — Поверхность ошибки чтения
Код ошибки 1718 — Жесткий диск ошибке
Код ошибки 1720 — Bad диагностики цилиндра
Код ошибки 1726 — Данные сравнить ошибку
Код ошибки 1730 — Драйв ошибка контроллера
Код ошибки 1731 — Драйв ошибка контроллера
Код ошибки 1732 — Драйв ошибка контроллера
Код ошибки 1733 — BIOS неопределенная ошибка возвращения
Код ошибки 1735 — Плохо ошибку команды
Код ошибки 1736 — исправлена ошибка данных
Код ошибки 1737 — Плохо ошибку трек диска
Код ошибки 1738 — Плохо ошибку сектора
Код ошибки 1739 — Bad ошибка инициализации
Код ошибки 1740 — Bad смысле ошибке
Код ошибки 1750 — Драйв проверить ошибки
Код ошибки 1751 — Драйв ошибка чтения
Код ошибки 1752 — Драйв ошибка записи
Код ошибки 1753 — Драйв случайного чтения тест провал
Код ошибки 1754 — Драйв искать провал испытаний
Код ошибки 1755 — отказ контроллера диска
Код ошибки 1756 — контроллер ECC провал испытаний
Код ошибки 1757 — Контроллер голову выбрать провал
Код ошибки 1780 — Драйв искать неисправность (диск 0)
Код ошибки 1781 — Драйв искать неисправность (диск 1)
Код ошибки 1782 — Жесткий диск контроллера провал
Код ошибки 1790 — Диагностические цилиндре ошибка чтения (диск 0)
Код ошибки 1791 — Диагностические цилиндре ошибка чтения (диск 1)

I / O группы Ошибки Слоты расширения:

Код — Описание

Код ошибки 1801 — Расширение блок POST ошибке
Код ошибки 1810 — Включить / Выключить провал
Код ошибки 1811 — Extender карты упаковка тест ошибка при инвалидов
Код ошибки 1812 — высокого порядка адресных линий ошибка при инвалидов
Код ошибки 1813 — Подождите, государство в то время как неспособность инвалидов
Код ошибки 1814 — Включить / выключить не может быть установлен на
Код ошибки 1815 — Подождите, государство в то время как неспособность включен
Код ошибки 1816 — Extender карты упаковка тест ошибка при включен
Код ошибки 1817 — высокого порядка адресных линий ошибка при включен
Код ошибки 1818 — отключить не работает
Код ошибки 1819 — Подождите, пока запрос переключатель установлен неправильно
Код ошибки 1820 — приемник карты упаковка тест не удалось
Код ошибки 1821 — Приемник высоковольтных линий адрес для отказа

For their PS/2 systems, IBM
used a system of diagnostic codes to diagnose trouble spots in a given
computer.  The problem was, these diagnostic codes were never really
documented all that well.  The codes that I am presenting here
are from documents I have read through, found on the web, found in old
books, documents and technical papers.  As a computer technician,
I rely on documentation to guide me through these types of messages. 
Therefore, I hope to provide this to all those other technicians out
there who get the opportunity to work on one of these.  And, yes,
people still use them and some refuse to give them up.

The method for reading these codes is
pretty straight forward.  The first part of the error code indicates
the device that is causing the trouble.  The second part gives
the meaning of the error.  You can think of the first part as the
test code and the second part as the fault code.  A fault code
of 00 indicates that no problem was found.  Thus 200 means the
system memory was tested.   The 00 means that no fault was found. 
201 would mean a memory error.   202 would mean memory address
error; lines 00-15. 

This page is rather extensive and will
be updated on a regular basis.  Like all the other codes out there. 
If you know of any error codes that I am displaying incorrectly or that
aren’t here.  Let me know and I’ll get it corrected
as soon as I can.

Thanks to Mike Rose for erors 129 and
229!

System Board
Errors:

Code	Description
101	System board interrupt failure (unexpected interrupt)
102	BIOS ROM checksum error (PC, XT); timer error (AT, MCA)
103	BASIC ROM checksum error (PC, XT); timer interrupt error (AT, MCA)
104	Interrupt controller error (PC, XT); protected mode error (AT, MCA)
105	Timer failure (PC, XT); 8042 keyboard controller failure (MCA)
106	System board converting logic test failure
107	System board non-maskable interrupt (NMI) test failure; Hot NMI test failure (MCA)
108	System board timer bus test failure
109	DMA test memory select failure
110	PS/2 system board parity check error (MCA); PS/2 system board memory error (ISA)
111	PS/2 adapter memory problem (ISA); PS/2 I/O channel parity check error (MCA)
112	PS/2 watchdog timeout error (NMI)
113	PS/2 DMA arbitration time out error (NMI)
114	PS/2 external ROM checksum error
115	BIOS ROM checksum error, cache parity error, or DMA error
116	System board read/write error
118	System Board parity or L2 cache error
119	2.88MB floppy installed but not supported by the floppy controller
120	CPU self test error
121	Unexpected hardware interrupt occurred; 256KB ROM checksum error (second 128KB bank)
129	System Board Failure
131	Cassette wrap test; DMA compatibility registers error
132	DMA extended registers error
133	DMA verify logic error
134	DMA arbitration error
151	Battery, real time clock, or CMOS RAM failure
152	Real time clock, or CMOS RAM failure
160	PS/2 system board ID not recognized
161	CMOS configuration lost (battery has died)
162	CMOS checksum error, CRC error, or adapter ID mismatch
163	CMOS error; Clock is not updating
164	CMOS error; CMOS setting does not match memory on system board
165	PS/2 adapter ID mismatch
166	PS/2 adapter time out; card busy
167	PS/2 system clock not updating
168	Math coprocessor error in the CMOS configuration
169	System board and processor card configuration mismatch
170	ASCII setup conflict error
171	Rolling bit test failure on CMOS shutdown byte
172	Rolling bit test failure on NVRAM diagnostic byte
173	Bad CMOS/NVRAM checksum
174	Bad system configuration
175	Bad EEPROM CRC
177	Bad password CRC
178	Bad EEPROM
179	NVRAM error log full
180x	Sub address date error in slot x
181	Unsupported configuration
182	Password switch is not in the writing position
183	System halted; password is required
184	Bad power on password
185	Bad startup sequence
186	Password protection hardware error
187	Serial number error
188	Bad EEPROM checksum
189	Too many incorrect password attempts
191	Cache controller test failed
194	System board memory error
195	Configuration read from hibernation area of HDD doesn’t match actual configuration
196	Read error occurred in hibernation area of HDD
199	User indicated device list not correct

Return to Top

Memory Errors:

Code	Description
20x	Memory error
201	Memory test failure; error location might be displayed
202	Memory address error; lines 00-15
203	Memory address error; lines 16-23 (ISA) or 16-31 (MCA)
204	Memory remapped due to error (run diagnostics again)
205	Base 128KB memory error; memory remapped
207	ROM failure
210	System board memory parity error
211	Error in first 64KB of RAM
212	Watchdog timer error
213	DMA bus arbitration time out
215	Memory address error; 64KB on daughter/SIP 2 failed
216	Memory address error; 64KB on daughter/SIP 1 failed
221	ROM to RAM copy failed
225	Wrong speed memory on system board
229	Memory Error
230	Overlapping adapter and planar memory
231	Non continuous adapter memory installed
235	Stuck data line on memory module
241	Memory module 2 failed
251	Memory module 3 failed

Return to Top

Keyboard Errors:

Code	Description
301	Keyboard did not respond correctly
302	Keyboard locked
303	Keyboard and/or system board interface error; keyboard controller fault
304	Keyboard or system unit error
305	Keyboard fuse failed on system board
306	Unsupported keyboard attached
341	Keyboard error
342	Keyboard cable error
343	Enhancement card or cable error
365	Keyboard failure
366	Interface cable failure
367	Enhancement card or cable failure

Return to Top

Monochrome Display
Adapter Errors:

Code	Description
401	Memory, horizontal sync frequency or vertical sync failure
408	User indicated display attribute failure
416	User indicated character set failure
424	User indicated 80 x 25 mode failure
432	MDA card parallel port test failure

Return to Top

Color Graphics
Adapter Errors:

Code	Description
501	CRT error; CGA memory, horizontal sync frequency or video test failure
503	CGA adapter controller failed
508	User display attribute failure
516	User indicated character set failure
524	User indicated 80 x 25 mode failure
532	User indicated 40 x 25 mode failure
540	User indicated 320 x 200 graphics mode failure
548	User indicated 640 x 200 graphics mode failure
556	User indicated light pen test failed
564	User indicated paging test failure

Return to Top

Floppy Drive/Controller
Errors:

Code	Description
601	General diskette or adapter failure
602	Diskette boot sector is not valid
603	Diskette size error
604	Media sense error
605	Diskette drive locked
606	Diskette verify test failed
607	Write protect error
608	Drive command error
610	Diskette initialization failure
611	Drive time out error
612	NEC drive controller IC error
613	Floppy system DMA error
614	Floppy system DMA boundary overrun error
615	Drive index timing error
616	Drive speed error
621	Drive seek error
622	Drive cyclic redundancy check (CRC) error
625	Controller chip (NEC) seek error
626	Diskette data compare error
627	Diskette data compare error
628	Diskette removed
630	Index stuck high; drive A:
631	Index stuck low; drive A:
632	Track 0 stuck off; drive A:
632	Track 0 stuck on; drive A:
640	Index stuck high; drive B:
641	Index stuck low; drive B:
642	Track 0 stuck off; drive B:
643	Track 0 stuck on; drive B:
645	No index pulse
646	Drive track 0 detection failed
647	No transitions on read data line
648	Format test failed
649	Incorrect media type in drive
650	Drive speed error
651	Format failure
652	Verify failure
653	Read failure
654	Write failure
655	Controller error
656	Drive failure
657	Write protect stuck protected
658	Changeline stuck unprotected
659	Write protected stuck unprotected
660	Changeline stuck unchanged

Return to Top

Math Coprocessor
Errors:

Code	Description
701	Math coprocessor presence/initialization error
702	Exception errors test failure
703	Rounding test failure
704	Arithmetic test 1 failure
705	Arithmetic test 2 failure
706	Arithmetic test 3 failure; Test is performed on 80387 only
707	Combination test failure
708	Integer load/store test failure
709	Equivalent expressions errors
710	Interrupt errors
711	Save state errors
712	Protected mode test failure
713	Voltage test failure

Return to Top

Parallel Printer
Adapter Errors:

Code	Description
901	Data register latch error
902	Control register latch error
903	Register address decode error
904	Address decode error
910	Status line wrap connector error
911	Status line bit 8 wrap error
912	Status line bit 7 wrap error
913	Status line bit 6 wrap error
914	Status line bit 5 wrap error
915	Status line bit 4 wrap error
916	Printer adapter interrupt wrap error
917	Unexpected printer adapter interrupt
92x	Feature register error

Return to Top

Alternate Printer
Adapter Errors:

Code	Description
1001	Printer adapter data register latch error
1002	Printer adapter control register latch error
1003	Printer adapter register address decode error
1004	Printer adapter address decode error
1010	Status line wrap connector error
1011	Status line bit 8 wrap error
1012	Status line bit 7 wrap error
1013	Status line bit 6 wrap error
1014	Status line bit 5 wrap error
1015	Status line bit 4 wrap error
1016	Printer adapter interrupt wrap error
1017	Unexpected printer adapter interrupt
102x	Feature register error

Return to Top

Primary Async
Communications Errors:

Code	Description
1101	16450/16550 chip error; serial port A error
1102	Card selected feedback error; PC convertible internal modem test failed
1103	Port 102h register test failure; PC convertible internal modem dial tone test 1 failed
1104	PC convertible internal modem dial tine test 2 failed
1106	Serial option cannot be put to sleep
1107	Cable error
1108	Interrupt request (IRQ) 3 error
1109	Interrupt request (IRQ) 4 error
1110	16450/16550 chip register failure
1111	Internal wrap test of 16450/16550 chip modem control line failure
1112	External wrap test of 16450/16550 chip modem control line failure
1113	16450/16550 chip transmit error
1114	16450/16550 chip receive error
1115	16450/16550 chip receive error; data not equal to transmit data
1116	16450/16550 chip interrupt function error
1117	16450/16550 chip baud rate test failure
1118	16450/16550 chip receive external data wrap test failure
1119	16550 chip first-in/first-out (FIFO) buffer failure
1120	Interrupt enable register error; all bits cannot be set
1121	Interrupt enable register error; all bits cannot be reset
1122	Interrupt pending; stuck on
1123	Interrupt ID register; stuck on
1124	Modem cannot register error; all bits cannot be set
1125	Modem cannot register error; all bits cannot be reset
1126	Modem status register error; all bits cannot be set
1127	Modem status register error; all bits cannot be reset
1128	Interrupt ID error
1129	Cannot force overrun error
1130	No modem status interrupt
1131	Invalid interrupt pending
1132	No data ready
1133	No data available interrupt
1134	No transmit holding interrupt
1135	No interrupts
1136	No received line status interrupt
1137	No receive data available
1138	Transmit holding register not empty
1139	No modem status interrupt
1140	Transmit holding register not empty
1141	No interrupts
1142	No interrupt 4
1143	No interrupt 3
1144	No data transferred
1145	Maximum baud rate error
1146	Minimum baud rate error
1148	Time out error
1149	Invalid data returned
1150	Modem status register error
1151	No data set ready and delta data set ready
1152	No data set ready
1153	No delta data set ready
1154	Modem status register not clear
1155	No clear to send and delta clear to send
1156	No clear to send
1157	No delta clear to send

Return to Top

Alternate Async
Communications Errors:

Code	Description
1201	16450/16550 chip error
1202	Card selected feedback error
1203	Port 02h register test failure
1206	Serial option cannot be put to sleep
1207	Cable error
1208	Interrupt request (IRQ) 3 error
1209	Interrupt request (IRQ) 4 error
1210	16450/16550 chip register failure
1211	Internal wrap test of 16450/16550 chip modem control line failure
1212	External wrap test of 16450/16550 chip modem control line failure
1213	16450/16550 chip transmit error
1214	16450/16550 chip receive error
1215	16450/16550 chip receive error; data not equal to transmit data
1216	16450/16550 chip interrupt function error
1217	16450/16550 chip baud rate test failure
1218	16450/16550 chip receive external data wrap test failure
1219	16550 chip first-in/first-out (FIFO) buffer failure
1220	Interrupt enable register error; all bits cannot be set
1221	Interrupt enable register error; all bits cannot be reset
1222	Interrupt pending; stuck on
1223	Interrupt ID register; stuck on
1224	Modem cannot register error; all bits cannot be set
1225	Modem cannot register error; all bits cannot be reset
1226	Modem status register error; all bits cannot be set
1227	Modem status register error; all bits cannot be reset
1228	Interrupt ID error
1229	Cannot force overrun error
1230	No modem status interrupt
1231	Invalid interrupt pending
1232	No data ready
1233	No data available interrupt
1234	No transmit holding interrupt
1235	No interrupts
1236	No received line status interrupt
1237	No receive data available
1238	Transmit holding register not empty
1239	No modem status interrupt
1240	Transmit holding register not empty
1241	No interrupts
1242	No interrupt 4
1243	No interrupt 3
1244	No data transferred
1245	Maximum baud rate error
1246	Minimum baud rate error
1248	Time out error
1249	Invalid data returned
1250	Modem status register error
1251	No data set ready and delta data set ready
1252	No data set ready
1253	No delta data set ready
1254	Modem status register not clear
1255	No clear to send and delta clear to send
1256	No clear to send
1257	No delta clear to send

Return to Top

Game Control Adapter
Errors:

Code	Description
1301	Game control adapter test failure
1302	Joystick test failure

Return to Top

Matrix Printer
Errors:

Code	Description
1401	Printer test failure
1402	Printer not ready, not on line, or out of paper
1403	Printer no paper error
1404	Matrix printer test failure; system board time out
1405	Parallel adapter failure
1406	Printer presence test failed

Return to Top

Synchronous Data
Link Control Communications (SDLC) Adapter Errors:

Code	Description
1501	SDLC adapter test failure
1510	8255 port B failure
1511	8255 port A failure
1512	8255 port C failure
1513	8253 timer #1 did not reach terminal count
1514	8253 timer #1 stuck on
1515	8253 timer #0 did not reach terminal count
1516	8253 timer #0 stuck on
1517	8253 timer #2 did not reach terminal count
1518	8253 timer #2 stuck on
1519	8273 port B error
1520	8273 port A error
1521	8273 command/read time out
1522	Interrupt level 4 failure
1523	Ring indicate stuck on
1524	Receive clock stuck on
1525	Transmit clock stuck on
1526	Test indicate stuck on
1527	Ring indicate stuck on
1528	Receive clock stuck on
1529	Transmit clock stuck on
1530	Test indicate not on
1531	Data set ready not on
1532	Carrier detect not on
1533	Clear to send not on
1534	Data set ready stuck on
1535	Carrier detect stuck on
1536	Clear to send stuck on
1537	Interrupt level 3 failure
1538	Receive interrupt results error
1539	Wrap data compare error
1540	Direct memory access channel 1 error
1541	Direct memory access channel 1 error
1542	8273 error checking or status reporting error
1547	Stray interrupt level 4
1548	Stray interrupt level 3
1549	Interrupt presentation sequence time out

Return to Top

Display Station
Emulation Adapter (DSEA) Errors:

Code	Description
1604	DSEA or twinaxial network error
1608	DSEA or twinaxial network error
1624	DSEA error
1634	DSEA error
1644	DSEA error
1652	DSEA error
1654	DSEA error
1658	DSEA error
1662	DSEA interrupt level error
1664	DSEA error
1668	DSEA interrupt level error
1669	DSEA diagnostics error; use 3.0 or higher
1674	DSEA diagnostics error; use 3.0 or higher; DSEA station address error
1684	DSEA device address error
1688	DSEA device address error

Return to Top

Hard Drive and
Controller Errors:

Code	Description
1701	Fixed disk or adapter general error
1702	Drive and controller time out error
1703	Drive seek error
1704	Drive controller failed
1705	Drive sector not found error
1706	Write fault error
1707	Drive track 00 error
1708	Head select error
1709	Bad ECC returned
1710	Sector buffer overrun
1711	Bad address mark
1712	Internal controller diagnostics failure
1713	Data compare error
1714	Drive not ready
1715	Track 00 indicator error
1716	Diagnostics cylinder errors
1717	Surface read errors
1718	Hard drive error
1720	Bad diagnostics cylinder
1726	Data compare error
1730	Drive controller error
1731	Drive controller error
1732	Drive controller error
1733	BIOS undefined error return
1735	Bad command error
1736	Data corrected error
1737	Bad drive track error
1738	Bad sector error
1739	Bad initialization error
1740	Bad sense error
1750	Drive verify error
1751	Drive read error
1752	Drive write error
1753	Drive random read test failure
1754	Drive seek test failure
1755	Drive controller failure
1756	Controller ECC test failure
1757	Controller head select failure
1780	Drive seek failure (drive 0)
1781	Drive seek failure (drive 1)
1782	Hard disk controller failure
1790	Diagnostic cylinder read error (drive 0)
1791	Diagnostic cylinder read error (drive 1)

Return to Top

I/O Expansion
Unit Errors:

Code	Description
1801	Expansion unit POST error
1810	Enable/Disable failure
1811	Extender card wrap test failure while disabled
1812	High order address lines failure while disabled
1813	Wait state failure while disabled
1814	Enable/disable could not be set on
1815	Wait state failure while enabled
1816	Extender card wrap test failure while enabled
1817	High order address lines failure while enabled
1818	Disable not functioning
1819	Wait request switch not set correctly
1820	Receiver card wrap test failed
1821	Receiver high order address lines failure

Return to Top

Binary Synchronous
Communications (BSC) Adapter Errors:

Code	Description
2001	BSC adapter test failure
2010	8255 port A failure
2011	8255 port B failure
2012	8255 port C failure
2013	8253 timer #1 did not reach terminal count
2014	8253 timer #1 stuck on
2015	8253 timer #2 did not reach terminal count
2016	8253 timer #2 stuck on
2017	8251 data set ready failed to come on
2018	8251 clear to send not sensed
2019	8251 data set ready stuck on
2020	8151 clear to send stuck on
2021	8151 hardware reset failure
2022	8251 software reset failure
2023	8251 software «error reset» failure
2024	8251 transmit ready did not come on
2025	8251 receive ready did not come on
2026	8251 could not force «overrun» error status
2027	Interrupt failure; no timer interrupt
2028	Interrupt failure; transmit; replace card or planar
2029	Interrupt failure; transmit; replace card
2030	Interrupt failure; receive; replace card or planar
2031	Interrupt failure; receive; replace card
2033	Ring indicate stuck on
2034	Receive clock stuck on
2035	transmit clock stuck on
2036	Test indicate stuck on
2037	Ring indicate stuck on
2038	Receive clock not on
2039	Transmit clock not on
2040	Test indicate not on
2041	Data set ready not on
2042	Carrier detect not on
2043	Clear to send not on
2044	Data set ready stuck on
2045	Carrier detect stuck on
2046	Clear to send stuck on
2047	Unexpected transmit interrupt
2048	Unexpected receive interrupt
2050	8251 detected overrun error
2051	Lost data set ready during data wrap
2052	Receive time out during data wrap

Return
to Top

Alternate Binary
Synchronous Communications (BSC) Adapter Errors:

Code	Description
2101	BSC adapter test failure
2110	8255 port A failure
2111	8255 port B failure
2112	8255 port C failure
2113	8253 timer #1 did not reach terminal count
2114	8253 timer #1 stuck on
2115	8253 timer #2 did not reach terminal count
2116	8253 timer #2 stuck on
2117	8251 data set ready failed to come on
2118	8251 clear to send not sensed
2119	8251 data set ready stuck on
2120	8151 clear to send stuck on
2121	8151 hardware reset failure
2122	8251 software reset failure
2123	8251 software «error reset» failure
2124	8251 transmit ready did not come on
2125	8251 receive ready did not come on
2126	8251 could not force «overrun» error status
2127	Interrupt failure; no timer interrupt
2128	Interrupt failure; transmit; replace card or planar
2129	Interrupt failure; transmit; replace card
2130	Interrupt failure; receive; replace card or planar
2131	Interrupt failure; receive; replace card
2133	Ring indicate stuck on
2134	Receive clock stuck on
2135	transmit clock stuck on
2136	Test indicate stuck on
2137	Ring indicate stuck on
2138	Receive clock not on
2139	Transmit clock not on
2140	Test indicate not on
2141	Data set ready not on
2142	Carrier detect not on
2143	Clear to send not on
2144	Data set ready stuck on
2145	Carrier detect stuck on
2146	Clear to send stuck on
2147	Unexpected transmit interrupt
2148	Unexpected receive interrupt
2150	8251 detected overrun error
2151	Lost data set ready during data wrap
2152	Receive time out during data wrap

Return
to Top

Cluster Adapter
Errors:

Code	Description
22xx	A cluster adapter error has occurred — replace the cluster adapter

Return
to Top

Plasma Monitor
Adapter Errors:

Code	Description
23xx	A plasma adapter display error has occurred — replace the plasma display monitor assembly

Return
to Top

Enhanced Graphics
Adapter or Video Graphics Adapter Errors:

Code	Description
2401	Video adapter test failure
2402	Video display error
2408	User indicated display attribute test failed
2409	Video display error
2410	Video adapter error; video port error
2416	User indicated character set test failed
2424	User indicated 80 x 25 mode failure
2432	User indicated 40 x 25 mode failure
2440	User indicated mode 320 x 200 mode failure
2448	User indicated 640 x 200 mode failure
2456	User indicated light pen test failure
2464	User indicated paging test failure

Return
to Top

Alternate Enhanced
Graphics Adapter Errors:

Code	Description
2501	Video adapter test failure
2502	Video display error
2508	User indicated display attribute test failed
2509	Video display error
2510	Video adapter error; video port error
2516	User indicated character set test failed
2524	User indicated 80 x 25 mode failure
2532	User indicated 40 x 25 mode failure
2540	User indicated mode 320 x 200 mode failure
2548	User indicated 640 x 200 mode failure
2556	User indicated light pen test failure
2564	User indicated paging test failure

Return
to Top

XT or AT/370 370-M
(Memory) and 370-P (Processor) Adapter Errors:

Code	Description
2601	370-M adapter error
2655	370-M adapter error
2657	370-M adapter error
2668	370-M adapter error
2672	370-M adapter error
2673	370-P adapter error
2674	370-P adapter error
2677	370-P adapter error
2680	370-P adapter error
2681	370-M adapter error
2682	370-P adapter error
2694	370-P adapter error
2697	370-P adapter error
2698	XT or AT/370 diagnostic diskette error

Return
to Top

XT or AT/370 3277-EM
(Emulation) Adapter Error:

Code	Description
2701	3277-EM adapter error
2702	3277-EM adapter error
2703	3277-EM adapter error

Return
to Top

3728/3729 Emulation
Adapter or 3270 Connection Adapter Errors:

Code	Description
28xx	An emulation adapter fault has occurred — replace the adapter

Return
to Top

Color/Graphics
Printer Errors:

Code	Description
29xx	A general fault has been detected with the printer or it’s printer port — replace the adapter

Return
to Top

Primary PC Network
Adapter Errors:

Code	Description
3001	Network adapter test failure
3002	ROM checksum test failure
3003	Unit ID PROM test failure
3004	RAM test failure
3005	Host interface controller 9HIC) test failure
3006	+/- 12Vdc test failure
3007	Digital loopback test failure
3008	Host detected HIC failure
3009	Sync signal failure and no go bit
3010	HIC test OK and no go bit
3011	Go bit OK, but no command 41
3012	Card not present
3013	Digital failure fall through
3015	Analog failure
3041	Hot carrier on other card
3042	Hot carrier on this card

Return
to Top

Secondary PC Network
Adapter Errors:

Code	Description
3101	Network adapter test failure
3102	ROM checksum test failure
3103	Unit ID PROM test failure
3104	RAM test failure
3105	Host interface controller 9HIC) test failure
3106	+/- 12Vdc test failure
3107	Digital loopback test failure
3108	Host detected HIC failure
3109	Sync signal failure and no go bit
3110	HIC test OK and no go bit
3111	Go bit OK, but no command 41
3112	Card not present
3113	Digital failure fall through
3115	Analog failure
3141	Hot carrier on other card
3142	Hot carrier on this card

Return
to Top

3270 PC/AT Display
Errors:

Code	Description
32xx	A fault has been detected in the display system — replace the display system

Return
to Top

Compact Printer
Errors:

Code	Description
33xx	A fault has been detected in the printer or printer adapter — replace the printer or printer adapter

Return
to Top

Enhanced Display
Station Emulation Adapter (EDSEA) Errors:

Code	Description
3504	Adapter connected to twinaxial cable during offline test
3508	Workstation address error
3509	Diagnostic program failure
3540	Workstation address invalid
3588	Adapter address switch error
3599	Diagnostic program failure

Return
to Top

General Purpose
Interface Bus (GPIB) Adapter Errors:

Code	Description
3601	Adapter test failure
3602	Serial poll mode register write error
3603	Adapter address error
3610	Adapter listen error
3611	Adapter talk error
3612	Adapter control error
3613	Adapter standby error
3614	Adapter asynchronous control error
3615	Adapter asynchronous control error
3616	Adapter error; cannot pass control
3617	Adapter error; cannot address to listen
3618	Adapter error; cannot unaddress to listen
3619	Adapter error; cannot address to talk
3620	Adapter error; cannot unaddress to talk
3621	Adapter error; cannot address to listen with extended addressing
3622	Adapter error; cannot unaddress to listen with extended addressing
3623	Adapter error; cannot address to talk with extended addressing
3624	Adapter error; cannot unaddress to talk with extended addressing
3625	Write to self error
3626	Generate handshake error
3627	Cannot detect Device Clear message error
3628	Cannot detect Selected Device Clear message error
3629	Cannot detect end with end of identify
3630	Cannot detect end of transmission with end of identify
3631	Cannot detect end with 0 bot end of string
3632	Cannot detect end with 7 bit end of string
3633	Cannot detect group execute trigger
3634	Mode 3 addressing error
3635	Cannot recognize undefined command
3636	Cannot detect remote, remote changed, lockout, or lockout changed
3639	Cannot conduct serial poll
3640	Cannot conduct parallel poll
3650	Adapter error; direct memory access (DMA) to 7210
3651	Data error; error on direct memory access (DMA) to 7210
3652	Adapter error; direct memory access (DMA) from 7210
3653	Data error on direct memory access (DMA) from 7210
3658	Uninvoked interrupt received
3659	Cannot interrupt on address status changed
3660	Cannot interrupt on address status changed
3661	Cannot interrupt on command output
3662	Cannot interrupt on data out
3663	Cannot interrupt on data in
3664	Cannot interrupt on error
3665	Cannot interrupt on device clear
3666	Cannot interrupt on end
3667	Cannot interrupt on device execute trigger
3668	Cannot interrupt on address pass through
3669	Cannot interrupt on command pass through
3670	Cannot interrupt on remote changed
3671	Cannot interrupt on lockout changed
3672	Cannot interrupt on service request in
3673	Cannot interrupt on terminal count on direct memory access to 7210
3674	Cannot interrupt on terminal count on direct memory access from 7210
3675	Spurious direct memory access terminal count interrupt
3697	Illegal direct memory access configuration setting detected
3698	Illegal interrupt level setting detected

Return
to Top

System Board SCSI
Controller Errors:

Code	Description
37xx	the system board SCSI controller has failed — replace the motherboard

Return
to Top

Data Acquisition
Adapter Errors:

Code	Description
3801	Adapter test failure
3810	Timer read test failure
3811	Timer interrupt test failure
3812	Binary input 13 test failure
3813	Binary input 13 test failure
3814	Binary output 14 interrupt request test failure
3815	Binary output 0 count in test failure
3816	Binary input strobe (STB) count out test failure
3817	Binary output 0 clear to send (CTS) test failure
3818	Binary output 1, binary input 0 test failure
3819	Binary output 2, binary input 1 test failure
3820	Binary output 3, binary input 2 test failure
3821	Binary output 4, binary input 3 test failure
3822	Binary output 5, binary input 4 test failure
3823	Binary output 6, binary input 5 test failure
3824	Binary output 7, binary input 6 test failure
3825	Binary output 8, binary input 7 test failure
3826	Binary output 9, binary input 8 test failure
3827	Binary output 10, binary input 9 test failure
3828	Binary output 11, binary input 10 test failure
3829	Binary output 12, binary input 11 test failure
3830	Binary output 13, binary input 12 test failure
3831	Binary output 15, analog input CE test failure
3832	Binary output strobe, binary output GATE test failure
3833	Binary input clear to send, binary output HOLD test failure
3834	Analog input command output (CO), binary input 15 test failure
3835	Counter interrupt test failure
3836	Counter read test failure
3837	Analog output 0 ranges test failure
3838	Analog output 1 ranges test failure
3839	Analog input 0 values test failure
3840	Analog input 1 values test failure
3841	Analog input 2 values test failure
3842	Analog input 3 values test failure
3843	Analog input interrupt test failure
3844	Analog input 23 address or value test failure

Return
to Top

Professional Graphics
Adapter (PGA) Errors:

Code	Description
3901	PGA test failed
3902	ROM 1 self test failed
3903	ROM 2 self test failed
3904	RAM self test failed
3905	Cold start cycle power error
3906	Data error in communications RAM
3907	Address error in communications RAM
3908	Bad data reading/writing 6845 like register
3909	Bad data in lower E0h bytes reading/writing 6845 like registers
3910	Graphics controller display bank output latches error
3911	Basic clock error
3912	Command control error
3913	Vertical sync scanner error
3914	Horizontal sync scanner error
3915	Intech error
3916	Look up table address error
3917	Look up table red RAM chip error
3918	Look up table green RAM chip error
3919	Look up table blue RAM chip error
3920	Look up table data latch error
3921	Horizontal display error
3922	Vertical display error
3923	Light pen error
3924	Unexpected error
3925	Emulator addressing error
3926	Emulator data latch error
3927	Base for error codes 3928-3930
3928	Emulator RAM error
3929	Emulator RAM error
3930	Emulator RAM error
3931	Emulator horizontal/vertical display problem
3932	Emulator cursor position error
3933	Emulator attribute display problem
3934	Emulator cursor display error
3935	Fundamental emulation RAM problem
3936	Emulation character set problem
3937	Emulation graphics display error
3938	Emulation character display problem
3939	Emulation bank select error
3940	Adapter RAM U2 error
3941	Adapter RAM U4 error
3942	Adapter RAM U6 error
3943	Adapter RAM U8 error
3944	Adapter RAM U10 error
3945	Adapter RAM U1 error
3946	Adapter RAM U3 error
3947	Adapter RAM U5 error
3948	Adapter RAM U7 error
3949	Adapter RAM U9 error
3950	Adapter RAM U12 error
3951	Adapter RAM U14 error
3952	Adapter RAM U16 error
3953	Adapter RAM U18 error
3954	Adapter RAM U20 error
3955	Adapter RAM U11 error
3956	Adapter RAM U13 error
3957	Adapter RAM U15 error
3958	Adapter RAM U17 error
3959	Adapter RAM U19 error
3960	Adapter RAM U22 error
3961	Adapter RAM U24 error
3962	Adapter RAM U26 error
3963	Adapter RAM U28 error
3964	Adapter RAM U30 error
3965	Adapter RAM U21 error
3966	Adapter RAM U23 error
3967	Adapter RAM U25 error
3968	Adapter RAM U27 error
3969	Adapter RAM U29 error
3970	Adapter RAM U32 error
3971	Adapter RAM U34 error
3972	Adapter RAM U36 error
3973	Adapter RAM U38 error
3974	Adapter RAM U40 error
3975	Adapter RAM U31 error
3976	Adapter RAM U33 error
3977	Adapter RAM U35 error
3978	Adapter RAM U37 error
3979	Adapter RAM U39 error
3980	Graphics controller RAM timing error
3981	Graphics controller read/write latch error
3982	Shift register bus output latches error
3983	Addressing error (vertical column of memory; U2 at top)
3984	Addressing error (vertical column of memory; U4 at top)
3985	Addressing error (vertical column of memory; U6 at top)
3986	Addressing error (vertical column of memory; U6 at top)
3987	Addressing error (vertical column of memory; U8 at top)
3988	Addressing error (vertical column of memory; U10 at top)
3989	Horizontal bank latch errors
3990	Horizontal bank latch errors
3991	Horizontal bank latch errors
3992	RAG/CAG graphics controller error
3993	Multiple write modes; nibble mask errors
3994	Row nibble (display RAM) error
3995	Graphics controller addressing error

Return
to Top

Display Attachment
Unit and 5279 Display Errors:

Code	Description
44xx	A fault has occurred with the display system — replace the display system

Return
to Top

IEEE 488 (GPIB)
Interface Adapter Errors:

Code	Description
45xx	A fault has occurred with the GPIB — replace the adapter

Return
to Top

ARTIC Multiport/2
Interface Adapter Errors:

Code	Description
4611	ARTIC adapter error
4612/4613	Memory module error
4630	ARTIC adapter error
4640/4641	Memory module error
4650	ARTIC interface cable error

Return
to Top

Internal Modem
Errors:

Code	Description
48xx	The internal modem has failed — replace the modem

Return
to Top

Alternate Internal
Modem Errors:

Code	Description
49xx	The alternate internal modem has failed — replace the alternate internal modem

Return
to Top

PC Convertible
LCD Errors:

Code	Description
5001	LCD buffer failure
5002	LCD font buffer failure
5003	LCD controller failure
5004	User indicated PEL/drive test failure
5008	User indicated display attribute test failed
5016	User indicated character set test failed
5020	User indicated alternate character set test failure
5024	User indicated 80 x 25 mode test failure
5032	User indicated 40 x 25 mode test failure
5040	User indicated 320 x 200 graphics test failure
5048	User indicated 640 x 200 graphics test failure
5064	User indicated paging test failure

Return
to Top

PC Convertible
Portable Printer Errors:

Code	Description
5101	Portable printer interface failure
5102	Portable printer busy error
5103	Portable printer paper or ribbon error
5104	Portable printer time out
5105	User indicated print pattern test error

Return
to Top

Financial Communication
System Errors:

Code	Description
56xx	A fault has been detected in the financial communication system — replace the financial communication system

Return
to Top

Phoenix BIOS/Chipset
Specific Errors:

Code	Description
7000	Chipset CMOS failure
7001	Shadow RAM failure (ROM not shadowed to RAM)
7002	Chipset CMOS configuration data error

Return
to Top

Voice Communications
Adapter (VCA) Errors:

Code	Description
7101	Adapter test failure
7102	Instruction or external data memory error
7103	PC to VCA interrupt error
7104	Internal data memory error
7105	DMA error
7106	Internal registers error
7107	Interactive shared memory error
7108	VCA to PC interrupt error
7109	DC wrap error
7111	External analog wrap and tone output error
7114	Telephone attachment test failure

Return to Top

3 1/2″ Floppy
Disk Drive Errors:

Code	Description
7301	Diskette drive/adapter test failure
7306	Diskette change line error
7307	Write protected diskette
7308	drive command error
7310	Diskette initialization failure track 00 error
7311	Drive time out error
7312	NEC drive controller IC error
7313	DMA error
7314	DMA boundary overrun error
7315	Drive index timing error
7316	Drive speed error
7321	Drive seek error
7322	Drive CRC check error
7323	Sector not found error
7324	Address mark error
7325	NEC controller IC seek error

Return
to Top

8514/A Display
Adapter Errors:

Code	Description
7426	8514 display error
7440	8514/A memory module 31 error
7441	8514/A memory module 30 error
7442	8514/A memory module 29 error
7443	8514/A memory module 28 error
7444	8514/A memory module 22 error
7445	8514/A memory module 21 error
7446	8514/A memory module 18 error
7447	8514/A memory module 17 error
7448	8514/A memory module 32 error
7449	8514/A memory module 14 error
7450	8514/A memory module 13 error
7451	8514/A memory module 12 error
7452	8514/A memory module 06 error
7453	8514/A memory module 05 error
7454	8514/A memory module 02 error
7455	8514/A memory module 01 error
7460	8514/A memory module 16 error
7461	8514/A memory module 27 error
7462	8514/A memory module 26 error
7463	8514/A memory module 25 error
7464	8514/A memory module 24 error
7465	8514/A memory module 23 error
7466	8514/A memory module 20 error
7467	8514/A memory module 19 error
7468	8514/A memory module 15 error
7469	8514/A memory module 11 error
7470	8514/A memory module 10 error
7471	8514/A memory module 09 error
7472	8514/A memory module 08 error
7473	8514/A memory module 07 error
7474	8514/A memory module 04 error
7475	8514/A memory module 03 error

Return
to Top

4216 Page Printer
Adapter Errors:

Code	Description
7601	Adapter test failure
7602	Adapter card error
7603	Printer error
7604	Printer cable error

Return to Top

PCMCIA Adapter
Errors:

Code	Description
8081	Presence test failure (PCMCIA revision number also checksum)
8082	PCMCIA register test failure

Return
to Top

PS/2 Speech Adapter
Errors:

Code	Description
84xx	A fault has occurred with the speech adapter — replace the speech adapter

Return
to Top

2MB XMA Memory
Adapter Errors:

Code	Description
85xx	A fault has occurred with the memory module — replace the memory module

Return
to Top

PS/2 Pointing
Device Errors:

Code	Description
8601	Pointing device: mouse time out error
8602	Pointing device: mouse interface error
8603	System board: mouse interrupt error
8604	Pointing device or system board error
8611	System bus error
8612	TrackPoint II error
8613	System bus or TrackPoint II error

Return
to Top

MIDI Interface
Errors:

Code	Description
89xx	A fault has occurred with the MIDI adapter — replace the MIDI adapter

Return
to Top

3363 Worm Optical
Drive/Adapter Errors:

Code	Description
91xx	A fault has occurred in the drive or adapter — replace the adapter or the drive

Return
to Top

SCSI Adapter (W/32
bit Cache):

Code	Description
96xx	A fault has occurred with the SCSI adapter — replace the SCSI adapter

Return
to Top

Multiprotocol
Adapter Errors:

Code	Description
10001	Presence test failure
10002	Card selected feedback error
10003	Port 102h register test failure
10004	Port 103h register test failure
10006	Serial option cannot be disabled
10007	Cable error
10008	IRQ 3 error
10009	IRQ 4 error
10010	UART register failure
10011	Internal wrap test of UART control line failed
10012	External wrap test of UART control line failed
10013	UART transmit error
10014	UART receive error
10015	UART receive error — data not equal to transmit data
10016	UART interrupt error
10017	UART baud rate test failure
10018	UART receive external wrap test failure
10019	UART FIFO buffer failure
10026	8255 port A error
10027	8255 port B error
10028	8255 port C error
10029	8254 timer 0 error
10030	8254 timer 1 error
10031	8254 timer 2 error
10032	Bi-sync data set ready (DSR) response error
10033	Bi-sync clear to send(CTS) error
10034	8251 hardware reset test failed
10035	8251 function generator
10036	8251 status error
10037	Bi-sync timer interrupt error
10038	Bi-sync transmit interrupt error
10039	Bi-sync receive interrupt error
10040	Stray IRQ 3 error
10041	Stray IRQ 4 error
10042	Bi-sync external wrap error
10044	Bi-sync data wrap error
10045	Bi-sync line status error
10046	Bi-sync time out error during wrap test
10050	8273 command acceptance or time out error
10051	8273 port A error
10052	8273 port B error
10053	SDLC modem status logic error
10054	SDLC timer IRQ 4 error
10055	SDLC IRQ 4 error
10056	SDLC external wrap error
10057	SDLC interrupt results error
10058	SDLC data wrap error
10059	SDLC transmit interrupt error
10060	SDLC receive interrupt error
10061	DMA channel 1 transmit error
10062	DMA channel 1 receive error
10063	8273 status detect failure
10064	8273 error detect failure

Return
to Top

Internal 300/1200Bps
Modem Errors:

Code	Description
10101	Presence detect failure
10102	Card selected feedback error
10103	Port 102h register test error
10106	Serial option cannot be disabled
10108	IRQ 3 error
10109	IRQ 4 error
10110	UART chip register failure
10111	UART control line internal wrap test failure
10113	UART transmit error
10114	UART receive error
10115	UART error — transmit and receive data not equal
10116	UART interrupt function error
10117	UART baud rate test failure
10118	UART interrupt driven receive external data wrap test failure
10125	Modem reset result code error
10126	Modem general result code error
10127	Modem S registers read/write error
10128	Modem echo on/off error
10129	Modem enable/disable result codes error
10130	Modem enable number/word result codes error
10133	Connect results for 300 baud not received
10134	Connect results for 1200 baud not received
10135	Modem fails local analog loopback 300 baud test
10136	Modem fails local analog loopback 1200 baud test
10137	Modem does not respond to escape/reset sequence
10138	S register 13 shows incorrect parity or number of data bits
10139	S register 15 shows incorrect bit rate

Return
to Top

ESDI or MCA IDE
Fixed Disk or Adapter Errors:

Code	Description
10450	Read/write test failed
10451	read verify test failed
10452	Seek test failed
10453	Wrong drive type indicated
10454	Controller sector buffer test failure
10455	Controller invalid failure
10456	Controller diagnostic command failure
10461	Drive format error
10462	Controller head select error
10463	Drive read/write sector error
10464	Drive primary detect map unreadable
10465	Controller: error-correction code (ECC) 8 bit error
10466	Controller: error correction code (ECC) 9 bit error
10467	Drive soft seek error
10468	Drive head seek error
10469	Drive soft error count exceeded
10470	Controller attachment diagnostic error
10471	Controller wrap mode interface error
10472	Controller wrap mode drive select error
10473	Read verify test errors
10480	Seek failure: drive 0
10481	Seek failure: drive 1
10482	Controller transfer acknowledge error
10483	Controller reset failure
10484	Controller: head select 3 error
10485	Controller: head select 2 error
10486	Controller: head select 1 error
10487	Controller: head select 0 error
10488	Controller: read gate — command complete 2 error
10489	Controller: write gate — command complete 1 error
10490	Diagnostic area read error: drive 0
10491	Diagnostic area read error: drive 1
10492	Controller error, drive 1
10493	Reset error, drive 1
10499	Controller failure

Return
to Top

5 1/4 External
Disk Drive or Adapter Errors:

Code	Description
107xx	A fault has occurred with the external disk drive or adapter — replace the disk drive or adapter

Return
to Top

SCSI
Adapter (16 bit without Cache) Errors:

Code	Description
112xx	A fault has occurred with the SCSI adapter — replace the SCSI adapter

Return
to Top

System Board SCSI
Adapter Errors:

Code	Description
113xx	A fault has occurred with the system board SCSI adapter — replace the motherboard

Return
to Top

Processor Complex
Errors:

Code	Description
129005	DMA error
12901	Processor board: processor test failure
12902	Processor board: cache test failure
12904	Second level cache failure
12905	Cache enable/disable errors
12907	Cache fatal error
12908	Cache POST program error
12912x	Hardware failure
12913x	Micro channel bus time out
12914x	Software failure
12915x	Processor complex error
12916x	Processor complex error
12917x	Processor complex error
12918x	Processor complex error
12919x	Processor complex error
12940x	Processor complex failure
12950x	Processor complex failure
129900	Processor complex serial number mismatch

Return
to Top

P70/P75 Plasma
Display and Adapter Errors:

Code	Description
14901	Plasma display adapter failure
14902	Plasma display adapter failure
14922	Plasma display failure
14932	External display device failure

Return
to Top

XGA Display Adapter
Errors:

Code	Description
152xx	A fault has occurred with the XGA display adapter — replace the display adapter

Return
to Top

120MB Internal
Tape Drive Errors:

Code	Description
164xx	A fault has occurred with the internal tape drive — replace the tape drive

Return
to Top

6157 Streaming
Tape Drive Errors:

Code	Description
16520	Streaming tape drive failure
16540	Tape attachment adapter failure

Return
to Top

Primary Token
Ring Network Adapter Errors:

Code	Description
166xx	A fault has occurred with the network adapter — replace the network adapter

Return
to Top

Alternate Token
Ring Network Adapter Errors:

Code	Description
167xx	A fault has occurred with the network adapter — replace the network adapter

Return
to Top

PS/2 Wizard Adapter
Errors:

Code	Description
18001	Interrupt controller failure
18002	Incorrect timer count
18003	Timer interrupt failure
18004	Sync check interrupt failure
18005	Parity check interrupt failure
18006	Access error interrupt failure
18012	Bad checksum error
18013	Micro Channel interface error
18021	Wizard memory compare or parity error
18022	Wizard memory address line error
18023	Dynamic RAM controller error
18029	Wizard memory byte enable error
18031	Wizard memory expansion module memory compare or parity error
18032	Wizard memory expansion module byte enable error
19039	Wizard memory expansion module byte enable error

Return
to Top

DBCS Japanese
Display Adapter Errors:

Code	Description
185xx	A fault has occurred with the display adapter — replace the display adapter

Return
to Top

80286 Memory Expansion
Option Module Errors:

Code	Description
194xx	A fault has occurred with the memory module — replace the memory module

Return
to Top

Image Adapter
Errors:

Code	Description
200xx	A fault has occurred with the image adapter — replace the image adapter

Return
to Top

Unknown SCSI Device
Errors:

Code	Description
208xx	A fault has occurred in an unknown SCSI adapter — replace the unknown SCSI adapter

Return
to Top

SCSI Removable
Media Errors:

Code	Description
209xx	A fault has occurred in the SCSI removable disk — replace the removable disk

Return
to Top

SCSI Fixed Disk
Errors:

Code	Description
210PLSC	«PLSC» codes indicate errors
	P = SCSI ID number (Physical Unit Number or PUN)
	L = Logical unit number (LUN, usually 0)
	S = Host adapter slot number
	C = SCSI drive capacity
	A = 60MB
	B = 80MB
	C = 120MB
	D = 160MB
	E = 320MB
	F = 400MB
	H = 1.02MB (1GB)
	I = 104MB
	J = 212MB
	U = Undetermined or non IBM OEM drive

Return
to Top

SCSI Tape Drive
Errors:

Code	Description
211xx	A fault has occurred with the SCSI tape drive — replace the SCSI tape drive

Return
to Top

SCSI Printer Errors:

Code	Description
212xx	A fault has occurred with the SCSI printer — replace the SCSI printer

Return
to Top

SCSI Processor
Errors:

Code	Description
213xx	A fault has occurred with the SCSI adapter processor — replace the SCSI adapter

Return
to Top

SCSI Write Once
Read Multiple (WORM) Drive Errors:

Code	Description
214xx	A fault has occurred with the SCSI WORM drive — replace the SCSI WORM drive

Return
to Top

SCSI CD-ROM Drive
Errors:

Code	Description
215xx	A fault has occurred with the SCSI CD-ROM drive — replace the SCSI CD-ROM drive

Return
to Top

SCSI Scanner Errors:

Code	Description
216xx	A fault has occurred with the SCSI Scanner — replace the SCSI Scanner

Return
to Top

SCSI Magneto Optical
Drive Errors:

Code	Description
217xx	A fault has occurred with the SCSI Magneto Optical Drive — replace the drive

Return
to Top

SCSI Jukebox Changer
Errors:

Code	Description
218xx	A fault has occurred with the SCSI Jukebox Changer — replace the device

Return
to Top

SCSI Communications
Errors:

Code	Description
219xx	A fault has occurred with the SCSI Communications device — replace the device

Return
to Top

XGA-2 Adapter
Errors:

Code	Description
243xxxx	A fault has occurred with the XGA-2 adapter — replace the adapter

Return
to Top

Dynamic Configuration
Select (DCS) Information Codes:

Code	Description
I998001x	Bad integrity of DCS master boot record
I988002x	Read failure of DCS master boot record
I988003x	DCS master boot record is not compatible with the planar ID
I988004x	DCS master boot record is not compatible with the model/submodel byte
I988005x	Bad integrity of CMOS/NVRAM or internal process error
I988006x	Read failure of header/mask/configuration record
I988007x	Bad integrity of header/mask/configuration record
I988008x	Hard disk does not support the command to set the maximum RBA
I988009x	DCS master boot record is older than system ROM
I9880402	Copyright notice in E000 segment does not match the one in DCS MBR
I9880403	DCS MBR is not compatible with the system board ID or model/submodel byte

Return
to Top

Initial
Microcode Load (IML) Errors:

Code	Description
I999001x	Invalid disk IML error
I999002x	Disk IML record load error
I999003x	Disk IML record incompatible with system board
I999004x	Disk IML record incompatible with processor/processor card
I999005x	Disk IML not attempted
I999006x	Disk stage II system image load error
I999007x	Disk stage II image checksum error
I999008x	IML not supported on primary disk drive
I999009x	Disk IML record is older than ROM
I99900x1	Invalid diskette IML record
I99900x2	Diskette IML record load error
I99900x3	Diskette IML record incompatible with system board
I99900x4	Diskette IML record incompatible with processor board
I99900x5	Diskette IML recovery prevented (valid password and CE override not set)
I99900x6	Diskette stage II image load error
I99900x7	Diskette stage II image checksum error
I99900x9	Diskette IML record older then ROM

Return
to Top

No Bootable Device,
Initial Program Load (IPL) Errors:

Code	Description
I9990301	Hard disk error
I9990302	Invalid disk boot record, unable to read IPL boot record from disk
I9990303	IML system partition boot failure
I9990304	No bootable device with ASCII console
I9990305	No bootable device
I9990306	Invalid SCSI Device boot record
I9990401	Unauthorized access (manufacturing boot request with valid password)
I9990402	Missing ROM IBM copyright notice
I9990403	IML Boot record incompatible with system board/processor card

Return to Top