Chapter 7. Solving Problems; Diagnostic Tools Overview; Troubleshooting Tables - IBM 8852 - BladeCenter H Rack-mountable Installation And User Manual

Chapter 7. Solving problems

This section provides basic troubleshooting information to help you solve some
common problems that might occur while you are setting up your BladeCenter unit.
If you cannot locate and correct the problem using the information in this section,
see the Problem Determination and Service Guide for more information.

Diagnostic tools overview

The following tools are available to help you diagnose and solve hardware-related
problems:
v Troubleshooting tables
v Diagnostic programs and error messages
v Light path diagnostic LEDs

Troubleshooting tables

Use the troubleshooting tables to find solutions to problems that have identifiable
symptoms.
Note: The symptoms for monitor, keyboard, and mouse apply only to the devices
See the Problem Determination and Service Guide for more detailed information
about testing the BladeCenter unit. If you have run the diagnostic test programs or
if running the tests does not reveal the cause of problem, call for service.
Attention:
Determination and Service Guide, make sure that the latest level of firmware code
is installed in your BladeCenter unit.
If you have just added a new optional device and your system is not working,
complete the following procedure before using the troubleshooting tables:
1. Remove the device that you just added.
2. Run the diagnostic tests to determine whether the system is running correctly.
3. Reinstall the new device.
© Copyright IBM Corp. 2010
These tables list problem symptoms and steps to correct the problems. See
"Troubleshooting tables" for more information.
The built-in self-test (BIST) program checks the BladeCenter unit during startup
and generates error messages if problems are found.
Use the light path diagnostic LEDs on the BladeCenter unit and the BladeCenter
components to identify system errors quickly. See "Light path diagnostic LEDs"
on page 44.
that are connected to the management module; they do not apply to the
remote console.
If diagnostic error messages appear that are not listed in the Problem
41