IBM System x3650 M4 BD Type 5466, Инструкция по установке и обслуживанию

Страница: 145 / 786

If you are able to restart the server or if you need comprehensive diagnostics,
use DSA Preboot.
The IBM System x3650 M4 BD server comes with DSA Preboot diagnostics code
on the integrated USB flash memory. Utilities are available to reset and update
the diagnostics code on the integrated USB flash device, if the diagnostic
partition becomes damaged and does not start the DSA Preboot diagnostic
programs. For more information and to download the utilities, go to
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=SERV-DSA.
Running the DSA Preboot diagnostic programs
Use this information to run the DSA Preboot diagnostic programs.
About this task
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 DSA Preboot diagnostic programs that is stored in integrated flash
memory on the server, complete the following steps:
Procedure
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> Diagnostics 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.
Results
If the server stops during testing and you cannot continue, restart the server and
try running the DSA Preboot diagnostic programs again. If the problem remains,
replace the component that was being tested when the server stopped.
Chapter 4. Troubleshooting
129