IBM 8676 Hardware Maintenance Manual - Page 34

Diagnostic, error, message, tables, Error, format

Get IBM 8676 - Eserver xSeries 335 PDF manuals and user guides
UPC - 087944770107
View all IBM 8676 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 34 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
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