IBM JS20 Hardware Maintenance Manual - Page 49

Diagnostic, tools, overview

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 49 highlights

1. If a firmware checkpoint (progress) (3 or 4-digit) code or firmware error (8-digit) code is displayed on the console, see "Firmware checkpoint (progress) codes" on page 94 or "Firmware error codes" on page 102. 2. Check the BladeCenter management module event log and if the operating system is Linux, check the Linux Syslog (platform log). If an error was recorded by the system, see Chapter 10, "Symptom-to-FRU index," on page 93. 3. If an error was recorded or if you believe you have a problem, perform the "Performing AIX online concurrent mode diagnostics for problem determination" on page 25. 4. If the login prompt appears and you still suspect a problem, go to "Performing AIX online concurrent mode diagnostics for problem determination" on page 25 or see "Undetermined problems" on page 156. NO. 1. Check to see if a firmware checkpoint (progress) (3 or 4-digit) code or firmware error (8-digit) code is displayed on the console; if so, see "Firmware checkpoint (progress) codes" on page 94 or "Firmware error codes" on page 102. 2. Check the blade error LED on the information LED panel; if it is lit, see"Light path diagnostics" on page 46. 3. Record any POST error messages that are displayed on the screen; then, 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, perform Chapter 4, "Problem determination procedures for AIX and Linux," on page 21 or see Chapter 10, "Symptom-to-FRU index," on page 93. 4. If you do not have any error codes, perform Chapter 4, "Problem determination procedures for AIX and Linux," on page 21. Diagnostic tools overview The following tools are available to help you diagnose and solve hardware-related problems: v POST firmware checkpoints (progress codes) The power-on self-test (POST), or firmware checkpoints, tests the major components of the blade server. These firmware checkpoints (progress codes) indicate the detection of a problem if the server stops on a checkpoint during the startup process. - A four-digit code indicates successful completion of that portion of POST when the server does not stop on that checkpoint. - A result other than a four-digit code indicates that POST might have detected a problem. Error messages also appear during startup if POST detects a hardware-configuration problem. The last POST firmware checkpoint code posted is the most likely failure indicator. See "POST" on page 40 for more information. v Error symptom charts These charts list problem symptoms and steps to correct the problems. See "Error symptoms" on page 145 for more information. v Light path diagnostics Use the light path diagnostics feature to diagnose system errors quickly. See "Light path diagnostics" on page 46 for more information. Chapter 7. Diagnostics 39

  • 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
1.
If
a
firmware
checkpoint
(progress)
(3
or
4-digit)
code
or
firmware
error
(8-digit)
code
is
displayed
on
the
console,
see
“Firmware
checkpoint
(progress)
codes”
on
page
94
or
“Firmware
error
codes”
on
page
102.
2.
Check
the
BladeCenter
management
module
event
log
and
if
the
operating
system
is
Linux,
check
the
Linux
Syslog
(platform
log).
If
an
error
was
recorded
by
the
system,
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
3.
If
an
error
was
recorded
or
if
you
believe
you
have
a
problem,
perform
the
“Performing
AIX
online
concurrent
mode
diagnostics
for
problem
determination”
on
page
25.
4.
If
the
login
prompt
appears
and
you
still
suspect
a
problem,
go
to
“Performing
AIX
online
concurrent
mode
diagnostics
for
problem
determination”
on
page
25
or
see
“Undetermined
problems”
on
page
156.
NO.
1.
Check
to
see
if
a
firmware
checkpoint
(progress)
(3
or
4-digit)
code
or
firmware
error
(8-digit)
code
is
displayed
on
the
console;
if
so,
see
“Firmware
checkpoint
(progress)
codes”
on
page
94
or
“Firmware
error
codes”
on
page
102.
2.
Check
the
blade
error
LED
on
the
information
LED
panel;
if
it
is
lit,
see“Light
path
diagnostics”
on
page
46.
3.
Record
any
POST
error
messages
that
are
displayed
on
the
screen;
then,
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,
perform
Chapter
4,
“Problem
determination
procedures
for
AIX
and
Linux,”
on
page
21
or
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
4.
If
you
do
not
have
any
error
codes,
perform
Chapter
4,
“Problem
determination
procedures
for
AIX
and
Linux,”
on
page
21.
Diagnostic
tools
overview
The
following
tools
are
available
to
help
you
diagnose
and
solve
hardware-related
problems:
v
POST
firmware
checkpoints
(progress
codes)
The
power-on
self-test
(POST),
or
firmware
checkpoints,
tests
the
major
components
of
the
blade
server.
These
firmware
checkpoints
(progress
codes)
indicate
the
detection
of
a
problem
if
the
server
stops
on
a
checkpoint
during
the
startup
process.
–
A
four-digit
code
indicates
successful
completion
of
that
portion
of
POST
when
the
server
does
not
stop
on
that
checkpoint.
–
A
result
other
than
a
four-digit
code
indicates
that
POST
might
have
detected
a
problem.
Error
messages
also
appear
during
startup
if
POST
detects
a
hardware-configuration
problem.
The
last
POST
firmware
checkpoint
code
posted
is
the
most
likely
failure
indicator.
See
“POST”
on
page
40
for
more
information.
v
Error
symptom
charts
These
charts
list
problem
symptoms
and
steps
to
correct
the
problems.
See
“Error
symptoms”
on
page
145
for
more
information.
v
Light
path
diagnostics
Use
the
light
path
diagnostics
feature
to
diagnose
system
errors
quickly.
See
“Light
path
diagnostics”
on
page
46
for
more
information.
Chapter
7.
Diagnostics
39