Running the diagnostic programs

Use this information to run the diagnostic programs.

Note: The DSA memory test might take up to 30 minutes to run. If the problem is not a memory problem, skip the memory test.

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 <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.
  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. Type gui to display the graphical user interface, or type 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 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.
Exception: 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 Microprocessor problems 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.