Specifications

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