Table 2. Firmware Checkpoints (continued)
Checkpoint Description Action/
Possible Failing FRU
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 155.
E177 Transfer failure due to TFTP
error condition
See “Boot Problems and
Concerns” on page 155.
E17B Processor clock speed check
measurement
Primary I/O backplane.
See “Note” on page 137.
E180 Service processor command
setup
See “Note” on page 137.
E183 Service processor post See “Note” on page 137.
E186 Request PS1 VPD See “Note” on page 137.
E187 Add PS1 VPD to NVRAM and
device tree
See “Note” on page 137.
E188 Request PS2 VPD See “Note” on page 137.
Chapter 4. Checkpoints 147
To Next Page
Loading...
Need help?
General