IBM 887022X Maintenance Manual - Page 72

Symptom-to-FRU

Get IBM 887022X - Eserver xSeries 445 PDF manuals and user guides
UPC - 000435151957
View all IBM 887022X manuals
Add to My Manuals
Save this manual to your list of manuals

Page 72 highlights

Follow the steps in this checkout procedure to identify server problems. Note: For a 16-way configuration, the server must be started up as a standalone server (see "Starting the diagnostic programs" on page 70). 001 IS THE SERVER PART OF A CLUSTER? YES. Schedule maintenance for the server. Shut down all servers related to the cluster. Run the storage test. NO. Go to step 002 . 002 IF THE SYSTEM IS NOT PART OF A CLUSTER: If the operating system is running, do the following: 1. Check the Light Path (see "Light path LED errors" on page 190). 2. Check the service processor system-error logs. a. If the system-error log indicates a damaged field replaceable unit (FRU), replace the FRU, and run diagnostics to confirm that the problem has been solved. b. If the system-error log does not indicate a damaged FRU, see "Error symptoms" on page 230 and "Undetermined problems" on page 246. If the operating system is not running, do the following: 1. Check the Light Path (see "Light path LED errors" on page 190). 2. Check the service processor system-error logs. a. If the error log indicates a damaged field replaceable unit (FRU), replace the FRU, and run diagnostics to confirm that the problem has been solved. b. If the error log does not indicate a damaged FRU, check the operating system event logs; if these logs do not specify a particular error, go to step 3. 3. Turn off the server and all external devices. 4. Check all cables and power cords. 5. Set all display controls to the middle position. 6. Turn on all external devices. 7. Turn on the server. 8. Monitor the screen and the serial port for POST errors, and record any POST error messages that are displayed on the screen. If an error is displayed, look up the first error (see "POST error codes" on page 224). 9. Run diagnostics (see "Starting the diagnostic programs" on page 70). 003 DID THE DIAGNOSTIC PROGRAM START? NO. Find the failure symptom in "Error symptoms" on page 230. YES. Run the diagnostic programs. If necessary, see "Diagnostic programs and error messages" on page 68. If you receive an error, see Chapter 7, "Symptom-to-FRU index," on page 187. If the diagnostic programs were completed successfully and you still suspect a problem, see "Undetermined problems" on page 246. If the server does not turn on, see "Error symptoms" on page 230. 62 xSeries 445 Type 8870: 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
  • 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
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
Follow
the
steps
in
this
checkout
procedure
to
identify
server
problems.
Note:
For
a
16-way
configuration,
the
server
must
be
started
up
as
a
standalone
server
(see
“Starting
the
diagnostic
programs”
on
page
70).
±001²
IS
THE
SERVER
PART
OF
A
CLUSTER?
YES.
Schedule
maintenance
for
the
server.
Shut
down
all
servers
related
to
the
cluster.
Run
the
storage
test.
NO.
Go
to
step
±002²
.
±002²
IF
THE
SYSTEM
IS
NOT
PART
OF
A
CLUSTER:
If
the
operating
system
is
running,
do
the
following:
1.
Check
the
Light
Path
(see
“Light
path
LED
errors”
on
page
190).
2.
Check
the
service
processor
system-error
logs.
a.
If
the
system-error
log
indicates
a
damaged
field
replaceable
unit
(FRU),
replace
the
FRU,
and
run
diagnostics
to
confirm
that
the
problem
has
been
solved.
b.
If
the
system-error
log
does
not
indicate
a
damaged
FRU,
see
“Error
symptoms”
on
page
230
and
“Undetermined
problems”
on
page
246.
If
the
operating
system
is
not
running,
do
the
following:
1.
Check
the
Light
Path
(see
“Light
path
LED
errors”
on
page
190).
2.
Check
the
service
processor
system-error
logs.
a.
If
the
error
log
indicates
a
damaged
field
replaceable
unit
(FRU),
replace
the
FRU,
and
run
diagnostics
to
confirm
that
the
problem
has
been
solved.
b.
If
the
error
log
does
not
indicate
a
damaged
FRU,
check
the
operating
system
event
logs;
if
these
logs
do
not
specify
a
particular
error,
go
to
step
3.
3.
Turn
off
the
server
and
all
external
devices.
4.
Check
all
cables
and
power
cords.
5.
Set
all
display
controls
to
the
middle
position.
6.
Turn
on
all
external
devices.
7.
Turn
on
the
server.
8.
Monitor
the
screen
and
the
serial
port
for
POST
errors,
and
record
any
POST
error
messages
that
are
displayed
on
the
screen.
If
an
error
is
displayed,
look
up
the
first
error
(see
“POST
error
codes”
on
page
224).
9.
Run
diagnostics
(see
“Starting
the
diagnostic
programs”
on
page
70).
±003²
DID
THE
DIAGNOSTIC
PROGRAM
START?
NO.
Find
the
failure
symptom
in
“Error
symptoms”
on
page
230.
YES.
Run
the
diagnostic
programs.
If
necessary,
see
“Diagnostic
programs
and
error
messages”
on
page
68.
If
you
receive
an
error,
see
Chapter
7,
“Symptom-to-FRU
index,”
on
page
187.
If
the
diagnostic
programs
were
completed
successfully
and
you
still
suspect
a
problem,
see
“Undetermined
problems”
on
page
246.
If
the
server
does
not
turn
on,
see
“Error
symptoms”
on
page
230.
62
xSeries
445
Type
8870:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide