IBM eserver 630 6C4, Service Manual

Page: 156 / 573

Table 2. Firmware Checkpoints (continued)
Checkpoint Description Action/
Possible Failing FRU
E158 System firmware waiting for a
virtual terminal to be opened on an
HMC for SMS menus to be
displayed. Open a virtual terminal window on
the HMC.
E15B Transferring control to operating
system (service mode boot) See “Boot Problems/Concerns” on
page 150.
E15F Adapter VPD probe Follow the repair action listed for
checkpoint E151.
E170 Start of PCI Bus Probe Follow the repair action listed for
checkpoint E151.
E172 First pass of 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 (which can
result from incorrect IP parameters
being specified), the system still
attempts to boot and because
time-out durations are necessarily
long to accommodate retries, the
system may appear to hang.
Restart the system and get to the
SMS utilities menu. Under Select
Boot Options, verify:
v
Is the intended boot device
correctly specified in the boot
list?
v
Are the IP parameters correct?
v
Look at the server configuration
for this client.
v
Attempt to ping the target server
using the ping utility in SMS.
E175 BootP request Follow the repair actions for
checkpoint E174.
E176 TFTP file transfer Follow the repair actions for
checkpoint E174.
E177 Transfer failure due to TFTP error
condition See “Boot Problems/Concerns” on
page 150.
E17B Processor clock speed
measurement Call service support.
E183 Service processor POST
1. Replace the CEC backplane,
location: U0.1-P1.
2. Go to “MAP 1540: Minimum
Configuration” on page 101.
136 Eserver
pSeries 630 Models 6C4 and 6E4 Service Guide