Table of Contents
Advertisement
Table 2. Firmware Checkpoints (continued)
Checkpoint
E174
E175
E176
E177
E17B
E180
E183
E186
E187
E188
E189
E18C
E190
E191
150
Service Guide
Description
Establishing host connection
BootP request
TFTP file transfer
Transfer failure due to TFTP error
condition
Processor clock speed check
measurement
Service processor command setup
Service processor post
Request PS1 VPD
Add PS1 VPD to NVRAM and
device tree
Request PS2 VPD
Add PS2 VPD to NVRAM and
device tree
VPD and data communications with
I/O planar complete
Create ISA node
Create ISA reserved node
Action/
Possible Failing FRU
If the system is not connected to
an active network or if the target
server is inaccessible (this can also
result from incorrect IP parameters
being supplied), the system will still
attempt to boot. Because time-out
durations are necessarily long to
accommodate retries, the system
may appear to be hung.
Restart the system and access the
firmware SMS utilities. In the
utilities check:
v Is the intended boot device
correctly specified in the boot
list?
v Are the IP parameters correct?
v Verify the network connection
(network could be down).
v Have network administrator
verify the server configuration for
this client.
v Attempt to "ping" the target
server using the SMS "Ping"
utility.
Refer to checkpoint E174.
See "Boot Problems and Concerns"
on page 159.
See "Boot Problems and Concerns"
on page 159.
Primary I/O backplane.
See the note on page 139.
See the note on page 139.
See the note on page 139.
See the note on page 139.
See the note on page 139.
See the note on page 139.
See the note on page 139.
See the note on page 139.
See the note on page 139.
See the note on page 139.
Advertisement
Table of Contents
