A
single
problem
might
cause
more
than
one
error
message.
When
this
happens,
correct
the
cause
of
the
first
error
message.
The
other
error
messages
usually
will
not
occur
the
next
time
you
run
the
diagnostic
programs.
Exception:
If
there
are
multiple
error
codes
or
light
path
diagnostics
LEDs
that
indicate
a
microprocessor
error,
the
error
might
be
in
a
microprocessor
or
in
a
microprocessor
socket.
See
“Microprocessor
problems”
on
page
30
for
information
about
diagnosing
microprocessor
problems.
If
the
blade
server
stops
during
testing
and
you
cannot
continue,
restart
the
blade
server
and
try
running
the
diagnostic
programs
again.
If
the
problem
remains,
replace
the
component
that
was
being
tested
when
the
blade
server
stopped.
The
diagnostic
programs
assume
that
a
keyboard
and
mouse
are
attached
to
the
BladeCenter
unit
and
that
the
blade
server
controls
them.
If
you
run
the
diagnostic
programs
with
either
no
mouse
or
a
mouse
attached
to
the
BladeCenter
unit
that
is
not
controlled
by
the
blade
server,
you
cannot
use
the
Next
Cat
and
Prev
Cat
buttons
to
select
categories.
All
other
mouse-selectable
functions
are
available
through
function
keys.
To
view
server
configuration
information
(such
as
system
configuration,
memory
contents,
interrupt
request
(IRQ)
use,
direct
memory
access
(DMA)
use,
device
drivers,
and
so
on),
select
Hardware
Info
from
the
top
of
the
screen.
Diagnostic
text
messages
Diagnostic
text
messages
are
displayed
while
the
tests
are
running.
A
diagnostic
text
message
contains
one
of
the
following
results:
Passed:
The
test
was
completed
without
any
errors.
Failed:
The
test
detected
an
error.
User
Aborted:
You
stopped
the
test
before
it
was
completed.
Not
Applicable:
You
attempted
to
test
a
device
that
is
not
present
in
the
blade
server.
Aborted:
The
test
could
not
proceed
because
of
the
blade
server
configuration.
Warning:
The
test
could
not
be
run.
There
was
no
failure
of
the
hardware
that
was
being
tested,
but
there
might
be
a
hardware
failure
elsewhere,
or
another
problem
prevented
the
test
from
running;
for
example,
there
might
be
a
configuration
problem,
or
the
hardware
might
be
missing
or
is
not
being
recognized.
The
result
is
followed
by
an
error
code
or
other
additional
information
about
the
error.
42
BladeCenter
HS20
Type
7981
and
1884:
Problem
Determination
and
Service
Guide
Summary of Contents for eServer BladeCenter HS20 Type 8832
Page 1: ...BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 2: ......
Page 3: ...BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 8: ...vi BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 16: ...xiv BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 68: ...52 BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 98: ...82 BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 110: ...94 BladeCenter HS20 Type 7981 and 1884 Problem Determination and Service Guide ...
Page 111: ......
Page 112: ... Part Number 31R1716 Printed in USA 1P P N 31R1716 ...
