Viewing The Test Log; Diagnostic Error Codes - IBM LS20 - BladeCenter - 8850 Service Manual

Viewing the test log

To view the test log when the tests are completed, select Utility from the top of the
screen and then select View Test Log. The test-log data is maintained only while
you are running the diagnostic programs. When you exit from the diagnostic
programs, the test log is cleared.
To save the test log to a file on a diskette or to the hard disk, select Save Log on
the diagnostic programs screen and specify a location and name for the saved log
file.
Note: To save the test log to a diskette, you must use a diskette that you have
formatted yourself; this function does not work with preformatted diskettes. If the
diskette has sufficient space for the test log, the diskette can contain other data.

Diagnostic error codes

The following table describes the error codes that the diagnostic programs might
generate and suggested actions to correct the detected problems.
If the diagnostic programs generate error codes that are not listed in the table,
make sure that the latest level of the BIOS code is installed.
In the error codes, x can be any numeral or letter. However, if the three-digit
number in the central position of the code is 000, 195, or 197, do not replace a
CRU or FRU. These numbers appearing in the central position of the code have the
following meanings:
000
195
197
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, "Parts listing, Type 8850," on page 53 to determine which components are customer
replaceable units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by "(Trained service technician only)," that step must be performed only by a
trained service technician.
Error code Description
001-197-000 Test aborted.
001-198-000
The blade server passed the test. Do not replace a CRU or FRU.
The Esc key was pressed to end the test. Do not replace a CRU or FRU.
This is a warning error, but it does not indicate a hardware failure; do not
replace a CRU or FRU. Take the action that is indicated in the Action
column, but do not replace a CRU or a FRU. See the description for
Warning in the section "Diagnostic text messages" on page 44 for more
information.
Action
1. Check the test log for messages indicating the
cause of the error, and take the indicated action.
2. From the diagnostic programs, run Quick Memory
Test All Banks; then, if an error is detected, take
the indicated action.
3. Reinstall and, if necessary, update the BIOS code
on the server; then, rerun the test (see "Updating
the firmware" on page 85).
45
Chapter 2. Diagnostics