Filter
Top Products
Diagnostic programs, messages, and error codes
The diagnostic programs are the primary method of testing the major components
of the server. As you run the diagnostic programs, text messages and error codes
are displayed on the screen and are saved in the test log. A diagnostic text
message or error code indicates that a problem has been detected; to determine
what action you should take as a result of a message or error code, see the table in
“Diagnostic messages” on page 91.
Running the diagnostic programs
To run the diagnostic programs, complete the following steps:
1. If the server is running, turn off the server and all attached devices.
2. Turn on all attached devices; then, turn on the server.
3. When the prompt Press F2 for Dynamic System Analysis (DSA) is displayed,
press F2.
Note: The DSA Preboot diagnostic program might appear to be unresponsive
for an unusual length of time when you start the program. This is normal
operation while the program loads.
4. Optionally, select Quit to DSA to exit from the stand-alone memory diagnostic
program.
Note: After you exit from the stand-alone memory diagnostic environment, you
must restart the server to access the stand-alone memory diagnostic
environment again.
5. Select gui to display the graphical user interface, or select cmd to display the
DSA interactive menu.
6. Follow the instructions on the screen to select the diagnostic test to run.
If the diagnostic programs do not detect any hardware errors but the problem
remains during normal server operations, a software error might be the cause. If
you suspect a software problem, see the information that comes with your software.
A single problem might cause more than one error message. When this happens,
correct the cause of the first error message. The other error messages usually will
not occur the next time you run the diagnostic programs.
Exception: If multiple error codes or EasyLED diagnostics LEDs indicate a
microprocessor error, the error might be in a microprocessor or in a microprocessor
socket. See “Microprocessor problems” on page 69 for information about diagnosing
microprocessor problems.
If the server stops during testing and you cannot continue, restart the server and try
running the diagnostic programs again. If the problem remains, replace the
component that was being tested when the server stopped.
Diagnostic text messages
Diagnostic text messages are displayed while the tests are running. A diagnostic
text message contains one of the following results:
Passed: The test was completed without any errors.
Failed: The test detected an error.
90 ThinkServer TD200x Types 3719, 3821, 3822, and 3823: Hardware Maintenance Manual