Resolving The Problem

The server diagnostic programs are stored in upgradable read-only memory (ROM) on the system board. These programs are the primary method of testing the major components of the server. Sometimes the first error to occur causes additional errors. In this case, the server displays more than one error message. Always follow the suggested action instructions for the first error message that appears. The following sections contain the error codes that might appear in the detailed test log and summary log when running the diagnostic programs.

The error code format is as follows:

fff-ttt-iii-date-cc-text message

where:

The diagnostic text message format is as follows:

Function Name: Result (test specific string)

where:

WARNING: This result occurs when a possible problem is reported during the diagnostic test, such as when a device that is to be tested is not installed.

Note: Test Specific String This is additional information that you can use to analyze the problem.

Press F1 while running the diagnostic programs to obtain Help information. You also can press F1 from within a help screen to obtain online documentation from which you can select different categories. Press Esc to exit Help and return to where you started.

Starting the diagnostic programs

1. Turn on the server and watch the screen.
2. Press F2 when the message F2 for Diagnostics appears.
3. Enter the appropriate password and press Enter.
4. Select either Extended or Basic from the top of the screen.
5. Select the test you want to run when the Diagnostic Programs screen appears.
6. Follow the instructions on the screen.

Notes:

1. If the server stops during testing and you cannot continue, restart the server and try running the diagnostic programs again.
2. The keyboard and mouse (pointing device) tests assume that a keyboard and mouse are attached to the server.
3. If you run the diagnostic programs with no mouse attached to the server, you will not be able to navigate between test categories using the Next Cat and Prev Cat buttons. All other functions provided by mouse-selectable buttons are also available using the function keys.
4. You can test the USB keyboard by using the regular keyboard test. The regular mouse test can test a USB mouse. Also, you can run the USB hub test only if there are no USB devices attached.
5. You can view server configuration information (such as system configuration, memory contents, interrupt request (IRQ) use, direct memory access (DMA) use, device drivers, and so on) by selecting Hardware Info from the top of the screen.

If the hardware checks out OK but the problem persists during normal server operations, a software error might be the cause. If you suspect a software problem, refer to the information that comes with the software package.

The test log will not contain any information until after the diagnostic program has run.

Note: If you already are running the diagnostic programs, begin with (below) step 3.

1. Turn on the server and watch the screen.
2. Press F2 when the message F2 or Diagnostics appears.
3. Enter the appropriate power-on password if prompted and press Enter.
4. Select Utility when the Diagnostic Programs screen appears.
5. Select View Test Log from the list that appears
6. Follow the instructions on the screen. The system maintains the test-log data while the server is powered on. When you turn off the power to the server, the test log is cleared

Support forums

Submit a technical question

Before you call IBM Service