POST Messages
POST Message
Description
161
The real-time clock battery has failed.
Action: Have the system serviced or replace the battery yourself. For additional
information, see “Replacing the Battery” on page 159 and “Lithium Battery Notice”
on page ix before you attempt to change the battery.
You can use the server until you replace the battery. However, you must run the
Configuration/Setup utility programs 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 the diagnostic test programs might isolate the failing device, but
you must have the system serviced.
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, have the system serviced.
The server can be used 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 have installed or removed memory, run the Configuration/Setup Utility
program; then, exit, saving the new configuration settings. For information
about using the Configuration/Setup utility programs, see “Using the
Configuration/Setup Utility” on page 22.
If the message appears again, shut down the Netfinity 5000 server, reseat the
memory modules, and restart the Netfinity 5000 server.
3. If the problem persists, check to see if the system has isolated the problem to a
memory module:
If the System Error LED on the information LED panel is on, check the
DIMM Error LEDS next to the memory sockets on the system board (see
“System Board LEDs” on page 168). If a DIMM Error LED is on, run the
diagnostic program for the memory.
– If the tests fail, replace the DIMM. If the problem persists after you
replace the DIMM, have the system serviced.
– If the memory tests do not fail, have the system serviced.
If no error LED is on, the error logs in the Configuration/Setup Utility
program might provide additional information on the memory error.
If the problem persists, have the system serviced.
175
A vital product data (VPD) error occurred.
Action: Have the system serviced.
Chapter 6. Solving Problems
115
