Checkpoint Description Action/Possible Failing FRUE174 Description: Establishing host connectionAction/Possible Failing FRU: If the system is not connected to an active network, or ifthe target server is inaccessible (which can result from incorrect IP parameters beingspecified), the system still attempts to boot and because time-out durations arenecessarily 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 checkpointE174.E176 TFTP file transfer Follow the repair actions for checkpointE174.E177 Transfer failure due to TFTP error condition See “Boot Problems/Concerns” onpage 204.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 1541: JTAG ProblemIsolation” on page 126.E18D A system reset request has been sent tothe service processor. 1. Check for system firmware updates.2. Call service support.E191 Create ISA reserved node Go to “MAP 1540: Problem IsolationProcedures” on page 124.E199 Evaluating the RIO interface speed set bythe user in the service processor menu 1. Check for system firmware updates.Apply if available.2. Call service support.E19A NVRAM auto-boot? variable not found -assume FALSEGo to “MAP 1540: Problem IsolationProcedures” on page 124.E19B NVRAM menu? variable not found -assume FALSEGo to “MAP 1540: Problem IsolationProcedures” on page 124.E19D Create NVRAM node Go to “MAP 1540: Problem IsolationProcedures” on page 124.E19E Real-time clock (RTC) initialization Refer to error code 28030xxx in“Checkpoint and Error Code Index” onpage 213.E1A0 User requested boot to SMS menus viakeyboard entryGo to “MAP 1540: Problem IsolationProcedures” on page 124.E1A1 User requested boot to open firmwareprompt via keyboard entryGo to “MAP 1540: Problem IsolationProcedures” on page 124.E1A2 User requested boot using default servicemode boot list via keyboard entryGo to “MAP 1540: Problem IsolationProcedures” on page 124.E1A3 User requested boot using customizedservice mode boot list via keyboard entryGo to “MAP 1540: Problem IsolationProcedures” on page 124.170 Eserver pSeries 630 Model 6C4 and Model 6E4 Service Guide
