Table of Contents
Advertisement
Chapter 6. Solving problems
Use the diagnostic tools that are available to help you solve some common
problems that might occur while you are setting up the blade server.
If you install the blade server in the BladeCenter unit and the blade server does
not start, perform the following actions:
v Make sure that the BladeCenter unit is correctly connected to a power source.
v Reseat the blade server in the BladeCenter unit, as described in "Installing the
v If the power-on LED is flashing slowly, turn on the blade server, as described in
v If you have just added a new optional device or component, make sure that it is
If the blade server does not start after you have performed the preceding actions,
see the online information or the Problem Determination and Service Guide on the
IBM BladeCenter Documentation CD.
If you cannot see the AIX console after you install AIX locally by using the
keyboard/video select button and local media, run the change console command
and restart the blade server to switch the AIX console to a SOL connection:
chcons /dev/vty0
shutdown -Fr
The commands do not affect the console that is used by partition firmware.
The following tools are available to help you diagnose and solve hardware-related
problems:
v Power-on self-test (POST) firmware checkpoints and error codes
v Firmware error codes and location codes
v Troubleshooting tables
© Copyright IBM Corp. 2008
blade server in a BladeCenter unit" on page 36.
"Turning on the blade server" on page 16.
correctly installed and compatible with the blade server and its components. If
the device or component is not compatible, remove it from the blade server,
reinstall the blade server in the BladeCenter unit, and then restart the blade
server.
The firmware checkpoints are progress codes that your blade server writes to the
management-module event log during POST.
See the online information or the Problem Determination and Service Guide for
more information.
For detailed descriptions of the firmware error codes, see the online information
or the Problem Determination and Service Guide.
Some firmware error codes also include location codes. The location code
information is required to identify the failing component. Check the event log in
the management module to determine the location code information that
corresponds to the firmware error code.
For additional information about location codes, see the online information or
the Problem Determination and Service Guide.
Use the troubleshooting tables to find solutions to problems that have
identifiable symptoms.
53
Advertisement
Table of Contents
