IBM 84885BU User Manual - Page 107

Symptom-to-FRU, index

Page 107 highlights

Chapter 6. Symptom-to-FRU index This index supports xSeries 226 servers. Notes: 1. Check the configuration before you replace a CRU or FRU. Configuration problems can cause false errors and symptoms. 2. For IBM devices that are not supported by this index, see the documentation for that device. 3. Always start with "General checkout" on page 11. The symptom-to-FRU index lists symptoms, errors, and the possible causes. The most likely cause is listed first. Use this symptom-to-FRU index to help you decide which FRUs to have available when servicing the server. The first column of the two-column tables in this index lists error codes or messages, and the last column lists one or more suggested actions or FRUs to replace. Take the action (or replace the FRU) that is suggested first in the list, and then try the server again to see whether the problem has been corrected. Note: Try reseating a suspected component or reconnecting a cable before replacing the component. The POST BIOS code displays POST error codes and messages on the screen. Beep symptoms Beep symptoms are short tones or a series of short tones separated by pauses (intervals without sound). See the examples in the following table. Beeps 1-2-3 4 Description v One beep v A pause (or break) v Two beeps v A pause (or break) v Three beeps Four continuous beeps One beep after successfully completing POST indicates the server is functioning properly. Note: See "System replaceable units" on page 131 to determine which components should be replaced by a field service technician. Beep/symptom FRU/action 1-1-2 v Microprocessor (Microprocessor register test failed.) 1-1-3 (CMOS write/read test failed.) 1. Battery 2. System board 1-1-4 (BIOS EEPROM checksum failed.) 1. Recover BIOS 2. System board © Copyright IBM Corp. 2004 97

  • 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
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200

Chapter
6.
Symptom-to-FRU
index
This
index
supports
xSeries
226
servers.
Notes:
1.
Check
the
configuration
before
you
replace
a
CRU
or
FRU.
Configuration
problems
can
cause
false
errors
and
symptoms.
2.
For
IBM
devices
that
are
not
supported
by
this
index,
see
the
documentation
for
that
device.
3.
Always
start
with
“General
checkout”
on
page
11.
The
symptom-to-FRU
index
lists
symptoms,
errors,
and
the
possible
causes.
The
most
likely
cause
is
listed
first.
Use
this
symptom-to-FRU
index
to
help
you
decide
which
FRUs
to
have
available
when
servicing
the
server.
The
first
column
of
the
two-column
tables
in
this
index
lists
error
codes
or
messages,
and
the
last
column
lists
one
or
more
suggested
actions
or
FRUs
to
replace.
Take
the
action
(or
replace
the
FRU)
that
is
suggested
first
in
the
list,
and
then
try
the
server
again
to
see
whether
the
problem
has
been
corrected.
Note:
Try
reseating
a
suspected
component
or
reconnecting
a
cable
before
replacing
the
component.
The
POST
BIOS
code
displays
POST
error
codes
and
messages
on
the
screen.
Beep
symptoms
Beep
symptoms
are
short
tones
or
a
series
of
short
tones
separated
by
pauses
(intervals
without
sound).
See
the
examples
in
the
following
table.
Beeps
Description
1-2-3
v
One
beep
v
A
pause
(or
break)
v
Two
beeps
v
A
pause
(or
break)
v
Three
beeps
4
Four
continuous
beeps
One
beep
after
successfully
completing
POST
indicates
the
server
is
functioning
properly.
Note:
See
“System
replaceable
units”
on
page
131
to
determine
which
components
should
be
replaced
by
a
field
service
technician.
Beep/symptom
FRU/action
1-1-2
(Microprocessor
register
test
failed.)
v
Microprocessor
1-1-3
(CMOS
write/read
test
failed.)
1.
Battery
2.
System
board
1-1-4
(BIOS
EEPROM
checksum
failed.)
1.
Recover
BIOS
2.
System
board
©
Copyright
IBM
Corp.
2004
97