Table 2. 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 (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 159.
E177 Transfer failure due to TFTP error
condition
See “Boot Problems and Concerns”
on page 159.
E17B Processor clock speed check
measurement
Primary I/O backplane.
See the note on page 139.
E180 Service processor command setup See the note on page 139.
E183 Service processor post See the note on page 139.
E186 Request PS1 VPD See the note on page 139.
E187 Add PS1 VPD to NVRAM and
device tree
See the note on page 139.
E188 Request PS2 VPD See the note on page 139.
E189 Add PS2 VPD to NVRAM and
device tree
See the note on page 139.
E18C VPD and data communications with
I/O planar complete
See the note on page 139.
E190 Create ISA node See the note on page 139.
E191 Create ISA reserved node See the note on page 139.
150 Service Guide
To Next Page
Loading...