CheckpointsCheckpoints are intended to let users and service personal know what the server isdoing, with some detail, as it initializes. These checkpoints are not intended to beerror indicators, but in some cases a server could hang at one of the checkpointswithout displaying an 8-character error code. It is for these hang conditions, only, thatany action should be taken with respect to checkpoints. The most appropriate actionis included with each checkpoint.Before taking actions listed with a checkpoint, it is a good idea to look for bettersymptoms in the Service Processor error log. See Service Processor SystemInformation Menu.SP CheckpointsService Processor checkpoints are in the range E010 to E0FF. The message OKindicates successful service processor testing and initialization. Firmware checkpointsare listed in “Firmware Checkpoints” on page 3-32.Note: Go to MAP 1540 for any of the following conditions: A four-digit code in the range of E001 through EFFF displays on the operatorpanal but is not listed in the checkpoint table. A four-digit code displays in the checkpoint table, but does not contain a repairaction or FRU listing. All of the FRUs listed in the repair action have been replaced and the problemhas not been corrected.Table 3-4 (Page 1 of 3). SP Checkpoints.Checkpoint Description Action/Possible Failing FRUE000 System Support Controller beginsoperation. This is an informationalcheckpoint.See the note on 3-29.E010 Starting SP. self-tests 1. Service Processor.2. I/O board. (See notes on 3-1.)E011 SP self-tests completed successfully NAE012 Begin to set up Service ProcessorheapsService Processor.E020 Configuring CMOS 1. I/O board. (See notes on 3-1.)2. Service Processor.Chapter 3. Error Code to FRU Index 3-29