IBM eServer xSeries 135, User Reference Manual

Page: 83 / 144

Chapter 6. Solving Problems
71
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:
• 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.
Action: Verify that all external devices are turned on. You must turn on external devices
before turning on the server.
If you did not add, remove, or change the location of a device, a device is probably failing.
Running a 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
163 error message reappears, call for service.
You can use the server until the system is serviced, but any application programs that use the date
and time will be affected.
164 A change in the memory configuration occurred. This message might appear after you add or
remove memory.
Note: The server can be used with decreased memory capacity.
Action: 1. If POST error message 289 also occurred, follow the instructions for that error
message first.
2. If you just installed or removed memory, run the Configuration/Setup Utility
program (see “Using the Configuration/Setup Utility program” on page 12 for
more information); then, exit, saving the new configuration settings.
If the message appears again, shut down the server, reseat the memory
modules, and restart the server.
If the problem persists, call for service.
175 A vital product data (VPD) error occurred.
Action: Call for service.
176 177 178 A security hardware error occurred.
Action: Check for indications that someone has tampered with the server. If no one has
tampered with the server, call for service.
Table 12. POST error messages
POST message Description