Hypervisor problems
Table 17. Hypervisor's symptoms and actions
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 technician only)”, that step must be performed only by a trained
technician.
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
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 the USB embedded hypervisor flash
device” on page 227 and “Replacing the USB embedded hypervisor flash
device” on page 230).
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.
Intermittent problems
Use this information to solve intermittent problems.
Table 18. Intermittent problems and actions
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 technician only),” that step must be performed only by a trained
technician.
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
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 fan is not working. This can cause the server to overheat and
shut down.
2. Check the system-error log or IMM event logs (see “Event logs” on page 133).
The server resets (restarts)
occasionally.
1. If the reset occurs during POST and the POST watchdog timer is enabled (click
System Settings > Recovery > System Recovery > 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 Appendix B, “UEFI/POST
diagnostic codes,” on page 501 and Appendix C, “DSA diagnostic test results,”
on page 515.
2. If neither condition applies, check the system-error log or IMM system-event
log (see “Event logs” on page 133).
Chapter 4. Troubleshooting 145
To Next Page
Loading...
Need help?
General