Table of Contents
Advertisement
Chapter 2. Diagnostics
This chapter describes the diagnostic tools that are available to help you solve
problems that might occur in the blade server.
Note: The blade server uses shared resources that are installed in the BladeCenter
unit. Problems with these shared resources might appear to be in the blade server
(see "Solving shared BladeCenter resource problems" on page 66 for information
about isolating problems with these resources). See the Problem Determination and
Service Guide or the Hardware Maintenance Manual and Troubleshooting Guide for
your BladeCenter unit and other BladeCenter component documentation for
diagnostic procedures for shared BladeCenter components.
If you cannot locate and correct the problem using the information in this chapter,
see Appendix A, "Getting help and technical assistance," on page 111 for more
information.
Diagnostic tools
The following tools are available to help you diagnose and solve hardware-related
problems:
v POST beep codes, error messages, and error logs
v Troubleshooting tables
v Light path diagnostics
v Diagnostic programs, messages, and error codes
POST
When you turn on the blade server, it performs a series of tests to check the
operation of the blade server components and some optional devices in the blade
server. This series of tests is called the power-on self-test, or POST.
If a power-on password is set, you must type the password and press Enter, when
prompted, for POST to run.
If POST is completed without detecting any problems, a single beep sounds, and
the blade server startup is completed.
If POST detects a problem, more than one beep might sound, or an error message
is displayed. See "Beep code descriptions" on page 12 and "POST error codes" on
page 22 for more information.
© Copyright IBM Corp. 2006
The power-on self-test (POST) generates beep codes and messages to indicate
successful test completion or the detection of a problem. See "POST" for more
information.
These tables list problem symptoms and actions to correct the problems. See
"Troubleshooting tables" on page 39 for more information.
Use the light path diagnostics to diagnose system errors quickly. See "Light path
diagnostics" on page 51 for more information.
The diagnostic programs are the primary method of testing the major
components of the blade server. These programs are stored in read-only memory
(ROM) on the blade server. See "Diagnostic programs, messages, and error
codes" on page 55 for more information.
11
Advertisement
Table of Contents
