IBM eserver xSeries 350 User Reference Manual page 97

Table 16. POST error messages.
POST message
129 An error was detected in the L1 cache of one of the microprocessors.
Action: 1.
If the problem persists, call for service.
151 A real-time clock (RTC) error occurred.
Action: Call for service.
161 The real-time clock battery has failed.
Action: Replace the battery yourself or call for service.
You can use the server until you replace the battery. However, you must run the
Configuration/Setup Utility program and set the time and date and other custom settings each
time you turn on the server.
162 A change in device configuration occurred. This error occurs under one or more of the following
conditions:
•
•
•
•
•
•
Action: Verify that all external devices are turned on. You must turn on external devices before
If you did not add, remove, or change the location of a device, a device is probably failing.
Running the diagnostic test might isolate the failing device.
If you cannot isolate and correct the problem, call for service.
163 The time of day has not been set.
Action: Set the correct date and time. If the date and time are set correctly and saved, but the
You can use the server until the system is serviced, but any application programs that use the
date and time will be affected.
If you just installed a microprocessor, verify that the microprocessor is installed and
seated correctly.
2. If the problem persists, check to see if the system has isolated the problem to a
microprocessor:
• If the system error light on the operator information panel is on, check the
diagnostic panel to see if the CPU LED is on. See "System board LED locations
and diagnostic LED panel" on page 36 to identify the diagnostic panel and the
LED. If it is on, check the microprocessor-error lights next to the
microprocessor sockets.
— If a microprocessor-error light is on, run the diagnostic program for the
microprocessor that is indicated by the LED. If the tests fail, replace the
indicated microprocessor.
— If the microprocessor tests do not fail, call for service.
• If no error LED is on, the error logs in the Configuration/Setup Utility
program might provide additional information about the microprocessor error.
A new device has been installed.
A device has been moved to a different location or cable connection.
A device has been removed or disconnected from a cable.
A device is failing and is no longer recognized by the server as being installed.
An external device is not turned on.
An invalid checksum is detected in the battery-backed memory.
turning on the server.
163 error message reappears, call for service.
Description
Chapter 6. Solving problems
85