General Checkout - (NF 8500R

General Checkout - (NF 8500R - Type 8681)

General Checkout

The server diagnostic programs are stored in flash RAM on the I/O function card.
These programs are the primary method of testing the major components of the server.
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.

Note: Some error conditions will generate error messages that are displayed in the front panel video fluorescent display (VFD).
Some of these messages will automatically be cleared once the problem is corrected. Others will need to be cleared manually.
To ensure you have correctly identified the failing FRU during your diagnosis, manually clear any messages from the front panel display using the scroll and enter buttons on the right side of the front panel after you have replaced any FRU(s).
This can be done with the system in the Standby mode before power up. Then, once you reboot the system, if a problem still exists which normally generates a message on the front panel, the new message generated will alert you to the continued or new error condition.

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.

Notes:

If you hear beep codes, see 'Beep symptoms'.
If you hear beep code 1-3-1, see "1st 1MB RAM test failed" (Beep code 1-3-1) in 'Beep symptoms'.
If you hear beep code 3-3-2, see "SM Bus error" (Beep code 3-3-2) in 'Beep symptoms'.
If you do not hear beep codes, and have no other error indications but the system will not boot
or will not power off, see 'No beep symptoms'.
If you have SCSI errors posted on the monitor, see 'SCSI errors'.
If you have symptoms relating to fans, CD-ROM, diskette drive, SCSI devices, or monitor,
see 'Other error symptoms'.
If you do not have two LED's lit on each power supply, see 'Power supply LED errors'.
If you have a power fault message in the system error log, see 'Power control card LED'.
If you have server component fault indicator LEDs lit, see 'Server component fault indicators'.
If you have a flashing attention light and error messages posted in the front panel, see 'System management codes'.
If you have run diagnostics which generated diagnostic error codes, see 'Diagnostic error codes'.
If you have a SMI error posted in the front panel, see 'System Management Interrupt (SMI) Handler'.
If your system is hung, will not boot, or exhibits symptoms other than those above, see 'Undetermined problems'.
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 there are multiple errors logged in the system error log, diagnose the errors in the order they were posted according to the date/time stamp.
If you have intermittent problems, check the system error log; see, 'System error log'
If you need safety information, see 'Safety information'.

+---+ |001| +---+ IS THE SYSTEM PART OF A CLUSTER? +---+ Yes No-|002| Go to Step 004. +---+ +---+ |003| +---+ Schedule maintenance with the customer. Shut down all failing 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 front panel system error LED; if blinking, check the error message on the front panel and see 'System management codes'. - Attempt to boot to the Configuration/Setup utility and check the system error log. If an error was recorded by the system, see 'Symptom-to-FRU index'. If this is not possible, connect to the System Management Adapter and access the system error log remotely. - Attempt to boot the system and start the Diagnostic programs. See 'Running the diagnostic programs'. If the diagnostics will not load, record the symptoms you observe and go to 'Symptom-to-FRU index'.

If the diagnostics completed successfully and you still suspect a problem, go to
'Undetermined problems'.

Back to

Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.