IBM eServer 250 xSeries, Руководство пользователя

Страница: 117 / 186

Chapter 6. Solving problems
103
189 An attempt has been made to access the server with invalid passwords. After three incorrect
attempts, the server locks up; that is, the logon data fields are no longer available to the user.
201 An error occurred during the memory controller test. This error can be caused by:
• Incorrectly installed memory
• A failing memory module
• A processor-board problem
• A memory-board problem
Action: 1. If you just installed memory, verify that the new memory is correct for your server.
Also verify that the memory is installed and seated correctly.
2. If the problem persists, check to see if the system has isolated the problem to a
memory module:
• If the System Error light on the operator information panel is on, check to see if
the MEM LED on the diagnostic LED panel is on. If it is on, check the DIMM
Error LEDs next to the memory sockets. 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, call for service.
• If the memory tests do not fail, call for service.
3. 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, call for service.
229 An error was detected in the L2 cache of one of the microprocessors.
Action: 1. 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 to see if
the CPU LED on the diagnostic LED panel is on. If it is on, check the
Microprocessor Error LEDs next to the microprocessor sockets.
— If a Microprocessor LED is on, run the diagnostic program for the
microprocessor indicated by the LED. (If the Secondary Microprocessor
Error LED is on, run the "Alt CPU" diagnostic program.) If the tests fail,
replace the 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 on the microprocessor error.
If the problem persists, call for service.
262 A memory parity configuration error occurred.
Action: Call for service.
POST message Description
Table 16. POST error messages.