If this default boot list is used during system startup, the server attempts to boot from
the diskette drive, then from the CD-ROM drive, then from the first disk drive
encountered, and finally the first network connection encountered.
Custom Boot List
The contents of the

custom boot list

can be defined by using the graphical System
Management Services or the text-based System Management Services. When the
custom boot list is used during system startup, the server attempts to boot in turn
from each specific device in the custom boot list.
Note: Only the specific devices contained in the custom boot list are checked for a
bootable image. Other devices of the same type are
not
searched for a
bootable image unless they are also specified in the custom boot list. Refer
to Chapter 3, “Using System Management Services” for more information on
custom boot lists.
If no bootable image is found in the custom boot list, then the server restarts and
attempts to boot again.
If the custom boot list is discovered to be corrupted, the server rebuilds the custom
boot list according to the default boot list.
Loading Diagnostics in Service Mode Boot
The server can be booted in service mode (instead of normal mode) from either the
default boot list or custom boot list. After a successful service mode boot, the
diagnostic programs are started automatically.
Booting in Service Mode from the Default Boot List
To boot in service mode from the default boot list, do the following:
1. Before stopping the programs and operating system, notify your system
administrator and users that the server is going to be shut down.
2. Insert the diagnostics CD-ROM into the CD-ROM drive, if you intend to run
standalone diagnostics.
3. Turn off the server.
4. Wait 30 seconds, then turn on the server.
5. When the keyboard indicator appears during startup, press the F5 key if the
system console is a directly attached keyboard, or the 5 key if the system
console is an ASCII terminal.
Chapter 2. Using the Server 2-7