IBM JS20 Hardware Maintenance Manual - Page 143

IBM JS20 - BladeCenter - 8842 Manual

Get IBM JS20 - BladeCenter - 8842 PDF manuals and user guides
UPC - 000435230263
View all IBM JS20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 143 highlights

Service request number A12-12x A12-13x A12-15x A12-16x A12-50x A13-00x A13-01x A13-02x SRN source Description FRU/action G A non-critical error has been detected, an 1. Check the BladeCenter management module I/O host bridge time-out error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. G A non-critical error has been detected, a 1. Check the BladeCenter management module I/O host bridge address/data parity error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. G A non-critical error has been detected, a 1. Check the BladeCenter management module system support function error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. G A non-critical error has been detected, a 1. Check the BladeCenter management module system bus internal hardware/switch event log; if an error was recorded by the error. system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. G Recoverable errors on resource indicate 1. If repair is not immediately available, reboot a trend toward an unrecoverable error. and the resource will be deconfigured; However, the resource could not be operations can continue in a degraded mode. deconfigured and is still in use. The system is operating with the potential for an unrecoverable error. 2. Check the BladeCenter management module event log for an entry around this time. If no entry is found, replace the system board. G A non-critical error has been detected, a 1. Check the BladeCenter management module error log analysis indicates an error event log; if an error was recorded by the detected by the I/O device, but the failure system or if a checkpoint code is displayed on could not be isolated. the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. G A non-critical error has been detected, an 1. Check the BladeCenter management module I/O bus address parity error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. G A non-critical error has been detected, an 1. Check the BladeCenter management module I/O bus data parity error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. Chapter 10. Symptom-to-FRU index 133

  • 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
Service
request
number
SRN
source
Description
FRU/action
A12-12x
G
A
non-critical
error
has
been
detected,
an
I/O
host
bridge
time-out
error.
1.
Check
the
BladeCenter
management
module
event
log;
if
an
error
was
recorded
by
the
system
or
if
a
checkpoint
code
is
displayed
on
the
console,
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
2.
If
no
entry
is
found,
replace
the
system
board.
A12-13x
G
A
non-critical
error
has
been
detected,
a
I/O
host
bridge
address/data
parity
error.
1.
Check
the
BladeCenter
management
module
event
log;
if
an
error
was
recorded
by
the
system
or
if
a
checkpoint
code
is
displayed
on
the
console,
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
2.
If
no
entry
is
found,
replace
the
system
board.
A12-15x
G
A
non-critical
error
has
been
detected,
a
system
support
function
error.
1.
Check
the
BladeCenter
management
module
event
log;
if
an
error
was
recorded
by
the
system
or
if
a
checkpoint
code
is
displayed
on
the
console,
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
2.
If
no
entry
is
found,
replace
the
system
board.
A12-16x
G
A
non-critical
error
has
been
detected,
a
system
bus
internal
hardware/switch
error.
1.
Check
the
BladeCenter
management
module
event
log;
if
an
error
was
recorded
by
the
system
or
if
a
checkpoint
code
is
displayed
on
the
console,
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
2.
If
no
entry
is
found,
replace
the
system
board.
A12-50x
G
Recoverable
errors
on
resource
indicate
a
trend
toward
an
unrecoverable
error.
However,
the
resource
could
not
be
deconfigured
and
is
still
in
use.
The
system
is
operating
with
the
potential
for
an
unrecoverable
error.
1.
If
repair
is
not
immediately
available,
reboot
and
the
resource
will
be
deconfigured;
operations
can
continue
in
a
degraded
mode.
2.
Check
the
BladeCenter
management
module
event
log
for
an
entry
around
this
time.
If
no
entry
is
found,
replace
the
system
board.
A13-00x
G
A
non-critical
error
has
been
detected,
a
error
log
analysis
indicates
an
error
detected
by
the
I/O
device,
but
the
failure
could
not
be
isolated.
1.
Check
the
BladeCenter
management
module
event
log;
if
an
error
was
recorded
by
the
system
or
if
a
checkpoint
code
is
displayed
on
the
console,
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
2.
If
no
entry
is
found,
replace
the
system
board.
A13-01x
G
A
non-critical
error
has
been
detected,
an
I/O
bus
address
parity
error.
1.
Check
the
BladeCenter
management
module
event
log;
if
an
error
was
recorded
by
the
system
or
if
a
checkpoint
code
is
displayed
on
the
console,
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
2.
If
no
entry
is
found,
replace
the
system
board.
A13-02x
G
A
non-critical
error
has
been
detected,
an
I/O
bus
data
parity
error.
1.
Check
the
BladeCenter
management
module
event
log;
if
an
error
was
recorded
by
the
system
or
if
a
checkpoint
code
is
displayed
on
the
console,
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
2.
If
no
entry
is
found,
replace
the
system
board.
Chapter
10.
Symptom-to-FRU
index
133