Table 2. Firmware Checkpoints. (continued)
Checkpoint Description Action/ Possible Failing FRU
E140 Loading boot image See “Unresolved Checkpoint Problems”
on page 85.
E149 Create boot manager node See “Unresolved Checkpoint Problems”
on page 85.
E14C Create terminal-emulator node See “Unresolved Checkpoint Problems”
on page 85.
E14D Initiate boot image loading See “Boot Problems/Concerns” on
page 110.
E14E Create client interface node/directory See “Unresolved Checkpoint Problems”
on page 85.
E14F NVRAM validation, configure variable
token generation
See “Unresolved Checkpoint Problems”
on page 85.
E150 Create host (primary) PCI controller
node
See “Unresolved Checkpoint Problems”
on page 85.
E151 Probing PCI bus
1. If a location code is associated with
the checkpoint:
v Replace the FRU identified by the
location code
v Replace, one at a time, the other
PCI adapter cards on the same
PCI bus. See “Bus SRN to FRU
Reference Table” on page 178.
v Go to MAP 1540: Minimum
Configuration, “Step 1540-24” on
page 81.
2. If no location code is associated
with the checkpoint, go to MAP
1540: Minimum Configuration, “Step
1540-24” on page 81.
E152 Probing for the adapter FCODE;
evaluate if present.
1. If a location code is associated with
the checkpoint:
v Replace the FRU identified by the
location code
v Replace, one at a time, the other
PCI adapter cards on the same
PCI bus. See “Bus SRN to FRU
Reference Table” on page 178.
v Go to MAP 1540: Minimum
Configuration, “Step 1540-24” on
page 81.
2. If no location code is associated
with the checkpoint, go to MAP
1540: Minimum Configuration, “Step
1540-24” on page 81.
Chapter 4. Checkpoints
95
To Next Page
Loading...
