 |
IBM-AUSTRIA - PC-HW-Support 30 Aug 1999 |
General Checkout
General Checkout
The server diagnostic programs are stored in nonvolatile
random-access memory (NVRAM) 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.
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:
- The customer identifies the system as part of a cluster.
- One or more external storage units are attached to the system and at least
one of the attached storage units is additionally attached to another system or
unidentifiable source.
- One or more systems are located near the failing system.
If the failing system is suspect to be part of a shared DASD cluster,
all diagnostic tests can be run except diagnostic tests which tests the storage unit
(DASD residing in the storage unit) or the storage adapter attached to the storage unit.
NOTE:
- For systems that are part of a shared DASD
cluster, run one test at a time in looped mode.
Do not run all tests in looped mode, as this could
enable the DASD diagnostic tests.
- If multiple error codes are displayed, diagnose
the first error code displayed.
- If the computer hangs with a POST error, go to
the 'Symptom-to-FRU Index'.
- If the computer hangs and no error is displayed,
go to 'Undetermined Problems'.
- Power Supply problems, see 'No Beep Symptoms'.
- Safety information, see 'Safety Information'
- For intermittent problems, check the error log, see, 'Error Log'.
+---+
|001|
+---+
IS THE SYSTEM PART OF A CLUSTER?
+---+
Yes No-+002| Go to Step 004.
| +---+
+-+-+
|003|
+---+
Schedule maintenance with the customer. Shut down all systems
related to the cluster. Run storage test.
---------------------------------------------------------------
+---+
|004|
+---+
- 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.
- Check the error log, see 'Error Log'. If an
error was recorded by the system, see 'Symptom-to-FRU Index'.
- Start the Diagnostic Programs. See 'Running Diagnostic Test Programs'.
- Check for the following responses:
1. No beep.
2. Readable instructions or the Main Menu.
DID YOU RECEIVE THE CORRECT RESPONSES?
+---+
Yes No-+005| Find the failure symptom in 'Symptom-to-FRU Index'
| +---+
+-+-+
|006|
+---+
- Run the Diagnostic Programs. If necessary, refer to
'Running Diagnostic Test 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'.
---------------------------------------------------------------
Back to 
More INFORMATION / HELP is available at the IBM-HelpCenter
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.