Table 3. Firmware Checkpoints (continued)
Checkpoint Description Action/ Possible Failing FRU
E174 Establishing host connection If the system is not connected to an
active network or if the target server
is inaccessible (which 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 the note on page136.
E177 Transfer failure due to TFTP error
condition
See the note on page136.
E178 Create PCI token ring node See the note on page136.
E17B Processor bus speed check
1. I/O planar
2. See the note on page136.
E180 Service processor command setup See the note on page136.
E181 Send drawer data to I/O planar See the note on page136.
E182 Request 10 EIA-unit I/O drawer I/O
planar VPD
See the note on page136.
E183 Service processor Post See the note on page136.
E184 Request 10 EIA-unit I/O drawer
drawer interface panel VPD
See the note on page136.
E185 Add 10 EIA-unit I/O drawer drawer
interface panel VPD to NVRAM and
device tree
See the note on page136.
E186 Request PS1 VPD See the note on page136.
E187 Add PS1 VPD to NVRAM and
device tree
See the note on page136.
E188 Request PS2 VPD See the note on page136.
148 Service Guide