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
52
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
101
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
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.
v
Troubleshooting
tables
These
tables
list
problem
symptoms
and
actions
to
correct
the
problems.
See
“Troubleshooting
tables”
on
page
25
for
more
information.
v
Light
path
diagnostics
Use
the
light
path
diagnostics
to
diagnose
system
errors
quickly.
See
“Light
path
diagnostics”
on
page
38
for
more
information.
v
Diagnostic
programs,
messages,
and
error
codes
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
42
for
more
information.
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
15
for
more
information.
©
Copyright
IBM
Corp.
2006
11
Summary of Contents for LS21 - BladeCenter - 7971
Page 1: ...BladeCenter LS21 Type 7971 and LS41 Type 7972 Problem Determination and Service Guide...
Page 2: ......
Page 3: ...BladeCenter LS21 Type 7971 and LS41 Type 7972 Problem Determination and Service Guide...
Page 8: ...vi BladeCenter LS21 Type 7971 and LS41 Type 7972 Problem Determination and Service Guide...
Page 16: ...xiv BladeCenter LS21 Type 7971 and LS41 Type 7972 Problem Determination and Service Guide...
Page 78: ...62 BladeCenter LS21 Type 7971 and LS41 Type 7972 Problem Determination and Service Guide...
Page 116: ...100 BladeCenter LS21 Type 7971 and LS41 Type 7972 Problem Determination and Service Guide...
Page 128: ...112 BladeCenter LS21 Type 7971 and LS41 Type 7972 Problem Determination and Service Guide...
Page 129: ......
Page 130: ...Part Number 24R9695 Printed in USA 1P P N 24R9695...
