Chapter 2. Diagnostics; Diagnostic Tools; Post; Post Beep Codes - IBM BladeCenter HS20 7981 Problem Determination And Service Manual

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 server.
If you cannot locate and correct the problem using the information in this chapter,
see Appendix A, "Getting help and technical assistance," on page 83 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 10 and "POST error codes" on
page 18 for more information.

POST beep codes

A beep code is a combination of short or long beeps or a series of short beeps that
are separated by pauses. For example, a "1-2-3" beep code is one short beep, a
pause, two short beeps, a pause, and three short beeps. A beep code other than
one beep indicates that POST has detected a problem. To determine the meaning
of a beep code, see "Beep code descriptions" on page 10. If no beep code sounds,
see "No-beep symptoms" on page 16.
© 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 25 for more information.
Use the light path diagnostics to diagnose system errors quickly. See "Light path
diagnostics" on page 38 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 41 for more information.
9

Advertisement

Table of Contents
loading

Table of Contents