IBM Netfinity 7100, Руководство пользователя

Страница: 129 / 200

Chapter 7. Solving problems
115
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.
289 An error occurred during POST memory tests and a failing DIMM was disabled.
Note: You can use the server with decreased memory.
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. Start the
Configuration/Setup Utility program and select Memory Settings from the
Advanced Setup menu to enable the DIMM.
2. If the problem remains, replace the failing DIMM.
If the problem persists, call for service.
301
303 An error occurred during the keyboard and keyboard controller test. These error messages also
might be accompanied by continuous beeping.
Action: Ensure that:
1. Nothing is resting on the keyboard and pressing a key.
2. No key is stuck.
3. The keyboard cable is connected correctly to the keyboard and to the correct
connector on the server.
Running the diagnostic tests can isolate the server component that failed, but you must have your
system serviced. If the error message remains, call for service.
Note: If you just connected a new mouse or other pointing device, turn off the server and
disconnect that device. Wait at least 5 seconds; then, turn on the server. If the error
message goes away, replace the device.
602 Invalid diskette boot record
Action: 1. Replace the diskette.
2. If the problem persists, make sure that the diskette drive cables are correctly and
securely connected.
3. If the problem remains, replace the diskette drive.
If the problem persists, call for service.
POST message Description
Table 16. POST error messages