IBM F80 Service Manual page 111

Table 2. Firmware Checkpoints (continued)
Checkpoint Description
E15B Transferring control to operating
system (service mode boot)
E15C Probe primary 64-bit PCI bus
E15D Create host PCI controller node
E15F Adapter VPD probe
E162 SP node VPD creation
E163 Create CPU VPD
E165 Create planar-clock VPD
E166 Create CEC VPD
E167 Collect power cards VPD.
E170 Start of PCI Bus Probe
E172 First pass PCI device probe
E174 Establishing host connection
E175 BootP request
E176 TFTP file transfer
E177 Transfer failure due to TFTP error
condition
Action/ Possible Failing FRU
See "Boot Problems and Concerns"
on page 102.
See the note on page 91.
See the note on page 91.
Follow the repair action listed for
checkpoint E151.
See the note on page 91.
See the note on page 91.
See the note on page 91.
See the note on page 91.
See the note on page 91.
Follow the repair action listed for
checkpoint E151.
Follow the repair action listed for
checkpoint E151.
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 102.
See "Boot Problems and Concerns"
on page 102.
Chapter 4. Checkpoints
93