Firmware/Post Error Codes - IBM 265 Service Manual

assembly should be replaced, swap the VPD from the old operator panel to the new
one. If the existing VPD module must be replaced, call technical support for
recovery instructions. If recovery is not possible, notify the system owner that new
keys for licensed programs may be required.
3. If a network adapter or the system board is replaced, the network administrator
must be notified so that the client IP addresses used by the server can be changed.
In addition, the operating system configuration of the network controller might need
to be changed in order to enable system startup. Also check to ensure that any
client or server that addresses this system is updated.
4. For service processor menus, see Chapter 7, "Using the Service Processor" on
page 177.

Firmware/POST Error Codes

If you replace FRUs or perform an action and the problem is still unresolved, go to
"MAP 1540: Minimum Configuration" on page 59 unless otherwise indicated in the
tables.
If you replace FRUs or perform an action, and the problem has been resolved, go to
"MAP 0410: Repair Checkout" in the RS/6000 Eserver pSeries Diagnostic Information
for Multiple Bus Systems , unless otherwise indicated in the tables.
The error codes listed in Table 3 identify the failing device/FRU, in most cases. A
physical location code may be displayed with the error code. If so, use the physical
location code to identify the suspected FRU.
Table 3. Firmware Error Codes.
Error Code Description
20A80000 Insufficient information to boot.
20A80001 Client IP address is already in use by
20A80002 Cannot get gateway IP address.
20A80003 Cannot get server hardware address.
20A80004 Bootp failed.
20A80005 File transmission (TFTP) failed.
20A80006 Image too large. Ran out of available
110
Service Guide
other network device.
firmware memory resources loading boot
image.
Action / Possible Failing FRU
Verify the IP address.
Change IP address.
Refer to "Firmware Checkpoints" on
page 88 table using code E174.
Refer to "Firmware Checkpoints" on
page 88 table using code E174.
Refer to "Firmware Checkpoints" on
page 88 table using code E175.
Check network connection, try again.
1. Verify boot server configuration.
2. Contact your service support
representative for assistance.