
Diagnostic
error
message
tables
For
descriptions
of
the
error
messages
that
might
appear
when
you
run
the
diagnostic
programs,
see
“Diagnostic
error
codes”
on
page
84.
Notes:
1.
Depending
on
the
server
configuration,
some
of
the
error
messages
might
not
appear
when
you
run
the
diagnostic
programs.
2.
If
diagnostic
error
messages
appear
that
are
not
listed
in
the
tables,
make
sure
that
the
server
has
the
latest
levels
of
BIOS,
Advanced
System
Management
Processor,
ServeRAID,
and
diagnostics
microcode
installed.
Error
code
format
The
error
code
format
is
as
follows:
fff-ttt-iii-date-cc-text
message
where:
fff
is
the
three-digit
function
code
that
indicates
the
function
being
tested
when
the
error
occurred.
For
example,
function
code
089
is
for
the
microprocessor.
ttt
is
the
three-digit
failure
code
that
indicates
the
exact
test
failure
that
was
encountered.
(These
codes
are
for
trained
service
personnel;
see
“Diagnostic
error
codes”
on
page
84).
iii
is
the
three-digit
device
ID.
(These
codes
are
for
trained
service
personnel;
see
“Diagnostic
error
codes”
on
page
84).
date
is
the
date
that
the
diagnostic
test
was
run
and
the
error
recorded.
cc
is
the
check
value
that
is
used
to
verify
the
validity
of
the
information.
text
message
is
the
diagnostic
message
that
indicates
the
reason
for
the
problem.
Text
message
format
The
diagnostic
text
message
format
is
as
follows:
Function
Name:
Result
(test
specific
string)
where:
Function
Name
is
the
name
of
the
function
being
tested
when
the
error
occurred.
This
corresponds
to
the
function
code
(fff)
shown
in
the
error
code
format
in
the
previous
section.
Result
can
be
one
of
the
following:
Passed
This
result
occurs
when
the
diagnostic
test
is
completed
without
any
errors.
Failed
This
result
occurs
when
the
diagnostic
test
discovers
an
error.
User
Aborted
This
result
occurs
when
you
stop
the
diagnostic
test
before
it
is
complete.
24
xSeries
335
Type
8676,
Type
8830:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide
Summary of Contents for 8676 - Eserver xSeries 335
Page 2: ......
Page 6: ...iv xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 10: ...viii xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 88: ...78 xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 126: ...116 xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 139: ...Appendix B Related service information 129 ...
Page 140: ...130 xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 141: ...Appendix B Related service information 131 ...
Page 142: ...132 xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 143: ...Appendix B Related service information 133 ...
Page 144: ...134 xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 145: ...Appendix B Related service information 135 ...
Page 155: ...Appendix B Related service information 145 ...
Page 156: ...146 xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 157: ...Appendix B Related service information 147 ...
Page 158: ...148 xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 159: ...Appendix B Related service information 149 ...
Page 160: ...150 xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 161: ...Appendix B Related service information 151 ...
Page 170: ...160 xSeries 335 Type 8676 Type 8830 Hardware Maintenance Manual and Troubleshooting Guide ...
Page 171: ......