IBM 8649 Hardware Maintenance Manual - Page 115

Error, Code/Symptom, FRU/Action, XXX-000, XXX-001, XXX-002, XXX-003, XXX-005, XXX-0NN, XXX-001, XXX-

Page 115 highlights

Error Code/Symptom FRU/Action 165-060-000 (Service Processor: RSA may be busy) 1. Rerun the diagnostic test. 2. Fix other error conditions that may be keeping ASM busy. Refer to the error log and diagnostic panel. 3. Disconnect all server and option power cords from server, wait 30 seconds, reconnect, and retry. 4. System Board. . 165-198-000 (Service Processor: Aborted) 1. Rerun the diagnostic test. 2. Fix other error conditions that may be keeping ASM busy. Refer to the error log and diagnostic panel. 3. Disconnect all server and option power cords from server, wait 30 seconds, reconnect, and retry. 4. System Board. 165-201-000 (Service Processor: Failed) 1. Disconnect all server and option power cords from server, wait 30 seconds, reconnect, and retry. 2. System Board. 165-330-000 (Service Processor: Failed) Update to the latest ROM diagnostic level, and retry. 165-342-000 (Service Processor: Failed) 1. Ensure latest firmware levels for ASM and BIOS. 2. Disconnect all server and option power cords from server, wait 30 seconds, reconnect, and retry. 3. System Board. 180-XXX-000 (Diagnostics LED failure) Run Diagnostic LED test for the failing LED. 180-XXX-001 (Failed Front LED panel test) Information LED Panel 180-XXX-002 (Failed Diagnostics LED panel test) System board 180-XXX-003 (Failed System Board LED test) System board 180-XXX-005 (Failed SCSI Backplane LED test) 1. SCSI Backplane 2. SCSI Backplane Cable 3. System Board 201-XXX-0NN (Failed Memory test, see "Installing memory modules" on page 55). 1. DIMM Location slots 1-4 where NN = DIMM location. Note: NN 1=DIMM 1 NN 2=DIMM 2 NN 3=DIMM 3 NN 4=DIMM 4 2. System Board 202-XXX-001 (Failed System Cache test) 1. Microprocessor 1 2. System Board 202-XXX-002 (Failed System Cache test) 1. Microprocessor 2 2. System Board 206-XXX-000 (Failed Diskette Drive test) 1. Try test with another diskette. 2. Cable. 3. Diskette Drive. 4. System Board. Chapter 6. Symptom-to-FRU index 105

  • 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

Error
Code/Symptom
FRU/Action
165-060-000
(Service
Processor:
RSA
may
be
busy)
1.
Rerun
the
diagnostic
test.
2.
Fix
other
error
conditions
that
may
be
keeping
ASM
busy.
Refer
to
the
error
log
and
diagnostic
panel.
3.
Disconnect
all
server
and
option
power
cords
from
server,
wait
30
seconds,
reconnect,
and
retry.
4.
System
Board.
.
165-198-000
(Service
Processor:
Aborted)
1.
Rerun
the
diagnostic
test.
2.
Fix
other
error
conditions
that
may
be
keeping
ASM
busy.
Refer
to
the
error
log
and
diagnostic
panel.
3.
Disconnect
all
server
and
option
power
cords
from
server,
wait
30
seconds,
reconnect,
and
retry.
4.
System
Board.
165-201-000
(Service
Processor:
Failed)
1.
Disconnect
all
server
and
option
power
cords
from
server,
wait
30
seconds,
reconnect,
and
retry.
2.
System
Board.
165-330-000
(Service
Processor:
Failed)
Update
to
the
latest
ROM
diagnostic
level,
and
retry.
165-342-000
(Service
Processor:
Failed)
1.
Ensure
latest
firmware
levels
for
ASM
and
BIOS.
2.
Disconnect
all
server
and
option
power
cords
from
server,
wait
30
seconds,
reconnect,
and
retry.
3.
System
Board.
180-XXX-000
(Diagnostics
LED
failure)
Run
Diagnostic
LED
test
for
the
failing
LED.
180-XXX-001
(Failed
Front
LED
panel
test)
Information
LED
Panel
180-XXX-002
(Failed
Diagnostics
LED
panel
test)
System
board
180-XXX-003
(Failed
System
Board
LED
test)
System
board
180-XXX-005
(Failed
SCSI
Backplane
LED
test)
1.
SCSI
Backplane
2.
SCSI
Backplane
Cable
3.
System
Board
201-XXX-0NN
(Failed
Memory
test,
see
“Installing
memory
modules”
on
page
55).
1.
DIMM
Location
slots
1-4
where
NN
=
DIMM
location.
Note:
NN
1=DIMM
1
NN
2=DIMM
2
NN
3=DIMM
3
NN
4=DIMM
4
2.
System
Board
202-XXX-001
(Failed
System
Cache
test)
1.
Microprocessor
1
2.
System
Board
202-XXX-002
(Failed
System
Cache
test)
1.
Microprocessor
2
2.
System
Board
206-XXX-000
(Failed
Diskette
Drive
test)
1.
Try
test
with
another
diskette.
2.
Cable.
3.
Diskette
Drive.
4.
System
Board.
Chapter
6.
Symptom-to-FRU
index
105