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:
- Make
sure that the BladeCenter unit
is correctly connected to a power source.
- Reseat the blade
server in the BladeCenter unit,
as described in Installing the blade server in a BladeCenter unit.
- If the power-on LED is flashing slowly, turn on the blade server,
as described in Turning on the blade server.
- If you have just added a new optional device or component, make
sure that it is 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.
If the blade server
does not start after you have performed the preceding actions, see Troubleshooting tables.
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:
- Power-on
self-test (POST) firmware checkpoints and error codes
The
firmware checkpoints are progress codes that your blade server writes
to the management-module event log during POST.
See POST progress codes (checkpoints).
- Firmware error codes
and location codes
For
detailed descriptions of
the firmware error codes, see System reference codes (SRCs).
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.
- Troubleshooting
tables
Use the troubleshooting tables
to find solutions to problems that have identifiable symptoms.
See Troubleshooting tables.
- Diagnostic utilities for the Linux operating
system
Diagnostic utilities for the Linux operating system are available from IBM®. To obtain these utilities and
information about them, complete the following steps:
- Go
to http://www.ibm.com/systems/bladecenter/.
- Under Product support, click BladeCenter.
- From the Product
family menu, click BladeCenter PS703 or PS704.
- From the Operating system menu, select the Linux operating system, and then click Go to
display the available downloads.
- Diagnostic
utilities for the AIX operating
system
An AIX operating-system
diagnostic CD, also known as the stand-alone Diagnostics CD,
is available from IBM. You can
start the CD from a CD drive or from NIM. To download the CD image,
go to http://www14.software.ibm.com/webapp/set2/sas/f/diags/home.html.
- Diagnostic utilities for other operating systems
Other
supported operating systems might have diagnostic tools that are available
through the operating system. See your operating-system documentation
for more information.
- Light path diagnostics
Use
light path diagnostics
LEDs on the system board to identify system errors. If the system-error
LED on the system LED panel on the front or rear of the BladeCenter unit is lit, one or more
error LEDs on the BladeCenter unit
components also might be lit. These LEDs help identify the cause of
the problem.
Notes: - View the system
event log in the BladeCenter management
module.
- Before you have the blade server serviced,
verify that you provide
a Serial over LAN (SOL) connection to the blade server. To do this,
you must configure the SOL feature on the blade server and start an
SOL session as described in the IBM BladeCenter Serial over
LAN Setup Guide.
- You can also configure the service processor
IP address by using
the management module, and set up a SOL connection to the service
processor.