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: the system board, Ethernet controller, video controller, RAM, keyboard, mouse (pointing device), diskette drive, serial port, and parallel port.
You can also use them to test some external devices.
See 'Diagnostic programs'.
Also, if you cannot determine whether a problem is caused by the hardware or by the software, you can run the diagnostic programs to confirm that the hardware is working properly.
When you run the diagnostic programs, a single problem might cause several error messages.
When this occurs, work to correct the cause of the first error message.
After the cause of the first error message is corrected, the other error messages might not occur the next time you run the test.
A failed system might be part of a shared DASD cluster (two or more systems sharing the same external storage device(s)).
Prior to running diagnostics, verify that the failing system is not part of a shared DASD cluster.
A system might be part of a cluster if:
IS THE SYSTEM PART OF A CLUSTER?
Yes No-+002| Go to Step 004.
Schedule maintenance with the customer.
Shut down all systems related to the cluster. Run storage test.
- Power-off the computer and all external devices.
- Check all cables and power cords.
- Set all display controls to the middle position.
- Power-on all external devices.
- Power-on the computer.
- Record any POST error messages displayed on the screen.
If an error is displayed, look up the first error in
the 'Symptom-to-FRU index'.
- Check the information LED panel System Error LED; if on,
see 'Light path diagnostics'.
- Check the System Error Log. If an error was recorded by the system,
see 'Symptom-to-FRU index'.
- Start the Diagnostic Programs.
See 'Running diagnostic programs'.
- Check for the following responses:
1. One beep.
2. Readable instructions or the Main Menu.
DID YOU RECEIVE BOTH OF THE CORRECT RESPONSES?
Yes No-+005| Find the failure symptom in 'Symptom-to-FRU index'.
| +---+ Or, use remote video mode to monitor and access
+-+-+ or look at the System Error Log.
- Run the Diagnostic Programs.
If necessary, refer to 'Running diagnostic programs'.
If you receive an error, go to 'Symptom-to-FRU index'.
If the diagnostics completed successfully and you still suspect a problem,
see 'Undetermined problems'.
Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.