v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained service technician.
v Go to the IBM support Web site at http://www.ibm.com/systems/support/ to check for technical information, hints, tips, and new device drivers or to submit a request for information.
Symptom Action
If an optional embedded hypervisor flash device is not listed in the expected boot order, does not appear in the list of boot devices, or a similar problem has occurred.
1. Make sure that the optional embedded hypervisor flash device is selected on the boot manager <F12> Select Boot Device) at startup.
2. Make sure that the embedded hypervisor flash device is seated in the connector correctly (see “Removing a USB hypervisor memory key” on page 216 and “Installing a USB hypervisor memory key” on page 217).
3. See the documentation that comes with the optional embedded hypervisor flash device for setup and configuration information.
4. Make sure that other software works on the server.
information, hints, tips, and new device drivers or to submit a request for information.
Symptom Action
A problem occurs only occasionally and is difficult to diagnose.
1. Make sure that:
v All cables and cords are connected securely to the rear of the server and attached devices.
v When the server is turned on, air is flowing from the fan grille. If there is no airflow, the fans are not working. This can cause the server to overheat and shut down.
2. Check the system event log or IMM2 event log (see “Event logs” on page 26).
3. Make sure that the server and IMM2 firmware has been updated to the most recent code levels.
4. Review the operating system logs.
5. Contact your operating-system vendor to set up any available tools that are capable of monitoring the server.
6. If an error occurs, run the DSA program and forward the results to IBM service and support for analysis.
7. See “Solving undetermined problems” on page 177.
The server resets (restarts)
occasionally. 1. If the reset occurs during POST and the POST watchdog timer is enabled (click System Settings --> Integrated Management Module --> POST Watchdog Timer in the Setup utility to see the POST watchdog setting), make sure that sufficient time is allowed in the watchdog timeout value (POST Watchdog Timer). If the server continues to reset during POST, see “POST/UEFI diagnostic codes” on page 28 and “Running the diagnostic programs” on page 137.
2. If the reset occurs after the operating system starts, disable any automatic server restart (ASR) utilities, such as the IBM Automatic Server Restart IPMI Application for Windows, or any ASR devices that are be installed.
Note: ASR utilities operate as operating-system utilities and are related to the IPMI device driver. If the reset continues to occur after the operating system starts, the operating system might have a problem; see “Software problems” on page 123.
3. If neither condition applies, check the system-error log or IMM2 system-event log (see “Event logs” on page 26).
BladeCenter and System x" document at http://www-947.ibm.com/support/entry/portal/
docdisplay?brand=5000020&lndocid=MIGR-5081319.
v Go to the IBM support website at http://www.ibm.com/supportportal/ to check for technical information, hints, tips, and new device drivers or to submit a request for information.
Symptom Action
The amount of system memory that is displayed is less than the amount of installed physical memory.
Note: Each time you install or remove a DIMM, you must disconnect the server from the power source; then, wait 10 seconds before restarting the server.
1. Make sure that:
v No error LEDs are lit on the operator information panel.
v No DIMM error LEDs are lit on the system board.
v Memory mirroring does not account for the discrepancy.
v The memory modules are seated correctly.
v You have installed the correct type of memory.
v If you changed the memory, you updated the memory configuration in the Setup utility.
v All banks of memory are enabled. The server might have automatically disabled a memory bank when it detected a problem, or a memory bank might have been manually disabled.
v There is no memory mismatch when the server is at the minimum memory configuration.
2. Reseat the DIMMs, and then restart the server.
3. Check the POST error log:
v If a DIMM was disabled by a systems-management interrupt (SMI), replace the DIMM.
v If a DIMM was disabled by the user or by POST, reseat the DIMM; then, run the Setup utility and enable the DIMM.
4. Check that all DIMMs are initialized in the Setup utility; then, run memory diagnostics (see “Running the diagnostic programs” on page 137).
5. Reverse the DIMMs between the channels (of the same microprocessor), and then restart the server. If the problem is related to a DIMM, replace the failing DIMM.
6. Re-enable all DIMMs using the Setup utility, and then restart the server.
7. (Trained technician only) Install the failing DIMM into a DIMM connector for microprocessor 2 (if installed) to verify that the problem is not the
microprocessor or the DIMM connector.
8. (Trained technician only) Replace the system board.
hints, tips, and new device drivers or to submit a request for information.
Symptom Action
Multiple DIMMs in a channel are identified as failing.
Note: Each time you install or remove a DIMM, you must disconnect the server from the power source; then, wait 10 seconds before restarting the server.
1. Reseat the DIMMs; then, restart the server.
2. Remove the highest-numbered DIMM of those that are identified and replace it with an identical known good DIMM; then, restart the server. Repeat as necessary. If the failures continue after all identified DIMMs are replaced, go to step 4.
3. Return the removed DIMMs, one at a time, to their original connectors, restarting the server after each DIMM, until a DIMM fails. Replace each failing DIMM with an identical known good DIMM, restarting the server after each DIMM replacement. Repeat step 3 until you have tested all removed DIMMs.
4. Replace the highest-numbered DIMM of those identified; then, restart the server. Repeat as necessary.
5. Reverse the DIMMs between the channels (of the same microprocessor), and then restart the server. If the problem is related to a DIMM, replace the failing DIMM.
6. (Trained technician only) Install the failing DIMM into a DIMM connector for microprocessor 2 (if installed) to verify that the problem is not the
microprocessor or the DIMM connector.
7. (Trained technician only) Replace the system board.
information, hints, tips, and new device drivers or to submit a request for information.
Symptom Action
The server goes directly to the POST Event Viewer when it is turned on.
1. Correct any errors that are indicated by the light path diagnostics LEDs (see
“Light path diagnostics LEDs” on page 129).
2. Make sure that the server supports all the microprocessors and that the microprocessors match in speed and cache size. To view the microprocessor information, run the Setup utility and select System Information → System Summary → Processor Details.
3. (Trained technician only) Make sure that microprocessor 1 is seated correctly.
4. (Trained technician only) Remove microprocessor 2 and restart the server.
5. Replace the following components one at a time, in the order shown, restarting the server each time:
a. (Trained technician only) Microprocessor b. (Trained technician only) System board