Chapter
6.
Solving
problems
This
chapter
provides
basic
information
about
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
(see
“Installing
the
blade
server
in
a
BladeCenter
unit”
on
page
50).
v
If
the
power-on
LED
is
flashing
slowly,
turn
on
the
blade
server
(see
“Turning
on
the
blade
server”
on
page
13).
v
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
still
does
not
start,
see
the
Problem
Determination
and
Service
Guide
on
the
BladeCenter
Documentation
CD.
Diagnostic
tools
overview
The
following
tools
are
available
to
help
you
diagnose
and
solve
hardware-related
problems:
v
POST
beep
codes
The
power-on
self-test
beep
codes
can
indicate
the
detection
of
a
problem.
–
One
beep
indicates
successful
completion
of
POST
–
Repeating
long
beeps
indicate
a
memory
error.
Make
sure
that
all
DIMMs
are
correctly
installed.
–
Additional
beep
codes
are
listed
under
“Diagnostics”
in
the
Problem
Determination
and
Service
Guide
.
v
POST
error
messages
The
POST
error
messages
indicate
the
detection
of
a
problem.
See
the
Problem
Determination
and
Service
Guide
for
more
information.
v
ServerGuide
problems
The
table
in
“ServerGuide
problems”
on
page
64
lists
problem
symptoms
and
steps
to
correct
the
problems.
v
Troubleshooting
tables
Use
the
troubleshooting
tables
to
find
solutions
to
problems
that
have
identifiable
symptoms.
These
tables
are
in
the
Problem
Determination
and
Service
Guide
.
v
Diagnostic
programs
and
error
messages
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
the
Problem
Determination
and
Service
Guide
for
more
information.
Note:
If
you
are
unable
to
find
the
system
error
logs
in
the
blade-server
firmware
code,
view
the
system
event
log
in
the
BladeCenter
management
module.
©
Copyright
IBM
Corp.
2008,
63
Summary of Contents for LS42 - BladeCenter - 7902
Page 1: ......
Page 2: ......
Page 3: ...BladeCenter LS22 and LS42 Type 7901 and 7902 Installation and User s Guide...
Page 26: ...16 BladeCenter LS22 and LS42 Type 7901 and 7902 Installation and User s Guide...
Page 88: ...78 BladeCenter LS22 and LS42 Type 7901 and 7902 Installation and User s Guide...
Page 89: ......
Page 90: ...Part Number 44R5057 Printed in USA 1P P N 44R5057...
