Table of Contents
Advertisement
To run the diagnostic programs, complete the following steps:
Step 1.
If the server is running, turn off the server and all attached devices.
Step 2.
Turn on all attached devices; then, turn on the server.
Step 3.
When the prompt <F2> Dynamic System Analysis 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. The
loading process may take up to 10 minutes.
Step 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.
Step 5.
Type gui to display the graphical user interface, or type cmd to display the DSA interactive menu.
Step 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
operation, 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.
If multiple error codes or light path diagnostics LEDs indicate a microprocessor error, the error might be in a
microprocessor or in a microprocessor socket. See
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.
Aborted: The test could not proceed because of the server configuration.
Additional information concerning test failures is available in the extended diagnostic results for each test.
Viewing the test log
Use this information to view the test log results.
To view the test log when the tests are completed, type the view command in the DSA interactive menu, or
select Diagnostic Event Log in the graphical user interface. To transfer DSA Preboot collections to an
external USB device, type the
Diagnostic messages
The following table describes the messages that the diagnostic programs might generate and suggested
actions to correct the detected problems.
"Microprocessor problems" on page 369
command in the DSA interactive menu.
copy
for information
.
Chapter 3
Diagnostics
319
Advertisement
Table of Contents
