Table of Contents
Advertisement
Chapter 6. Loading the System Diagnostics
The system diagnostics can be booted using either the default boot list or the
customized service mode boot list. (The service mode boot list can be modified using
the system diagnostics "Display or Change Bootlist" service aid. The service mode boot
list cannot be modified under the System Management Services.)
Performing Slow Boot
To fully analyze all of the available information, perform the following steps before doing
a hardware repair or replacement, especially if the error is related to the CPU or
memory:
1. Record the 8-character error code (and location code if present) displayed in the
operator panel, or that was reported by the customer.
2. Do a slow-mode boot in service mode. This can be specified using the System
Power Control Menu on the service processor main menu. (A fast-mode boot skips
much of the built-in diagnostic testing.) A slow-mode boot may yield a new
8-character error code on the operator panel and new errors in the service
processor error log. If a new error code is reported, use it in subsequent steps to
continue problem analysis.
Loading Standalone Diagnostics
To load Standalone Diagnostics using the default boot list, perform the following
procedure:
1. Verify with the system administrator and users that all programs may be stopped,
then do so.
2. Turn off the system.
3. Wait 30 seconds, and turn on the system.
4. Immediately insert the diagnostic CD-ROM into the CD-ROM drive.
5. After the keyboard indicator appears during startup, and before the tone sounds,
press the F5 key on a directly attached keyboard (or the number 5 key on an ASCII
terminal).
6. Enter any requested passwords.
Loading Online Diagnostics
Online Diagnostics can be loaded by booting using the customized service mode boot
list by pressing the F6 key (on a directly attached keyboard) or the number 6 key on an
ASCII terminal.
The procedure for booting from the devices listed in the service mode boot list (Online
Diagnostics) is the following:
1. Verify with the system administrator and users that all programs may be stopped,
then do so.
175
Advertisement
Table of Contents
