IBM JS20 Hardware Maintenance Manual - Page 137

IBM JS20 - BladeCenter - 8842 Manual

Page 137 highlights

Service request number A05-10x A05-14x A05-19x A05-21x A05-22x A05-24x A0D-00x SRN source Description FRU/action G System shutdown due to FRU that has 1. Check the BladeCenter management module failed. 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 System shutdown due to power fault with 1. Check the BladeCenter management module an unspecified cause. 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 System shutdown due to Fan failure. 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. G System shutdown due to Over temperature condition. 1. Verify that: a. The room ambient temperature is within the system operating environment. b. There is unrestricted air flow around the system. c. All system covers are closed. d. There are no fan failures 2. 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. 3. If no entry is found, replace the system board. G System shutdown due to over temperature and fan failure. 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. G Power Fault specifically due to internal 1. Check the BladeCenter management module battery failure. 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 Error log analysis indicates an error 1. Check the BladeCenter management module detected by the Service Processor, but event log; if an error was recorded by the the failure could not be isolated. 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 127

  • 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
A05-10x
G
System
shutdown
due
to
FRU
that
has
failed.
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.
A05-14x
G
System
shutdown
due
to
power
fault
with
an
unspecified
cause.
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.
A05-19x
G
System
shutdown
due
to
Fan
failure.
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.
A05-21x
G
System
shutdown
due
to
Over
temperature
condition.
1.
Verify
that:
a.
The
room
ambient
temperature
is
within
the
system
operating
environment.
b.
There
is
unrestricted
air
flow
around
the
system.
c.
All
system
covers
are
closed.
d.
There
are
no
fan
failures
2.
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.
3.
If
no
entry
is
found,
replace
the
system
board.
A05-22x
G
System
shutdown
due
to
over
temperature
and
fan
failure.
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.
A05-24x
G
Power
Fault
specifically
due
to
internal
battery
failure.
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.
A0D-00x
G
Error
log
analysis
indicates
an
error
detected
by
the
Service
Processor,
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.
Chapter
10.
Symptom-to-FRU
index
127