IBM JS20 Hardware Maintenance Manual - Page 48

Checkout, procedure

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

Note: If your system will not start, you can use the "Running the standalone diagnostics from CD-ROM" on page 25 procedure to isolate a hard disk drive failure that may be preventing the system from starting. v If your operating system is Linux, then you have the eSever Standalone Diagnostics CD available to check out your hardware. See "Running the standalone diagnostics from CD-ROM" on page 25. v The console must be open for error codes to be visible. Make sure that SOL is enabled. v A single problem might cause several error messages. When this occurs, correct the cause of the first error message. When the cause of the first error message is corrected, the other error messages might not occur the next time you run the test. Important: 1. If multiple error codes are displayed, diagnose the first code that is displayed. 2. If the server stops and a POST (3- or 4-digit) error code is displayed, see "Firmware checkpoint (progress) codes" on page 94. 3. If the server is suspended and no error message is displayed, see "Undetermined problems" on page 156. 4. For intermittent problems, go to Chapter 4, "Problem determination procedures for AIX and Linux," on page 21 and check the BladeCenter management module event log. If the operating system is Linux, the Linux Syslog (platform log) may have more information to help isolation the problem. 5. If the blade front panel shows no lit LEDs, verify blade status and errors in BladeCenter management-module web interface; also, see "Undetermined problems" on page 156. 6. If device errors occur, go to Chapter 4, "Problem determination procedures for AIX and Linux," on page 21 or see Chapter 10, "Symptom-to-FRU index," on page 93. Checkout procedure The checkout procedure can be used if the server does not start up after installation or if it experiences an undetermined error while running, such as if the server stops running with no error code displayed. Certain errors listed in the Symptom-to-FRU index will also direct you to perform the checkout procedure. If the operating system is AIX, you can also verify the system following the procedure "Performing AIX online concurrent mode diagnostics for system verification" on page 29. If the operating system is Linux, then you can use the standalone diagnostic CD in system verification mode to verify the JS20 blade server. 001 PERFORM THE CHECKOUT PROCEDURE: 1. Turn off the server, making sure to first turn off all external devices, if attached. 2. Check all cables and power cords. 3. Turn on all external devices; then, turn on the blade server. 4. Start the Serial Over Lan (SOL) console for the blade server to be tested and check for the following responses: a. Progress codes are displayed on the console. b. AIX or Linux login prompt appears. 002 DID THE LINUX OR AIX LOGIN PROMPT APPEAR? YES. 38 BladeCenter JS20 Type 8842: 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
Note:
If
your
system
will
not
start,
you
can
use
the
“Running
the
standalone
diagnostics
from
CD-ROM”
on
page
25
procedure
to
isolate
a
hard
disk
drive
failure
that
may
be
preventing
the
system
from
starting.
v
If
your
operating
system
is
Linux,
then
you
have
the
eSever
Standalone
Diagnostics
CD
available
to
check
out
your
hardware.
See
“Running
the
standalone
diagnostics
from
CD-ROM”
on
page
25.
v
The
console
must
be
open
for
error
codes
to
be
visible.
Make
sure
that
SOL
is
enabled.
v
A
single
problem
might
cause
several
error
messages.
When
this
occurs,
correct
the
cause
of
the
first
error
message.
When
the
cause
of
the
first
error
message
is
corrected,
the
other
error
messages
might
not
occur
the
next
time
you
run
the
test.
Important:
1.
If
multiple
error
codes
are
displayed,
diagnose
the
first
code
that
is
displayed.
2.
If
the
server
stops
and
a
POST
(3-
or
4-digit)
error
code
is
displayed,
see
“Firmware
checkpoint
(progress)
codes”
on
page
94.
3.
If
the
server
is
suspended
and
no
error
message
is
displayed,
see
“Undetermined
problems”
on
page
156.
4.
For
intermittent
problems,
go
to
Chapter
4,
“Problem
determination
procedures
for
AIX
and
Linux,”
on
page
21
and
check
the
BladeCenter
management
module
event
log.
If
the
operating
system
is
Linux,
the
Linux
Syslog
(platform
log)
may
have
more
information
to
help
isolation
the
problem.
5.
If
the
blade
front
panel
shows
no
lit
LEDs,
verify
blade
status
and
errors
in
BladeCenter
management-module
web
interface;
also,
see
“Undetermined
problems”
on
page
156.
6.
If
device
errors
occur,
go
to
Chapter
4,
“Problem
determination
procedures
for
AIX
and
Linux,”
on
page
21
or
see
Chapter
10,
“Symptom-to-FRU
index,”
on
page
93.
Checkout
procedure
The
checkout
procedure
can
be
used
if
the
server
does
not
start
up
after
installation
or
if
it
experiences
an
undetermined
error
while
running,
such
as
if
the
server
stops
running
with
no
error
code
displayed.
Certain
errors
listed
in
the
Symptom-to-FRU
index
will
also
direct
you
to
perform
the
checkout
procedure.
If
the
operating
system
is
AIX,
you
can
also
verify
the
system
following
the
procedure
“Performing
AIX
online
concurrent
mode
diagnostics
for
system
verification”
on
page
29.
If
the
operating
system
is
Linux,
then
you
can
use
the
standalone
diagnostic
CD
in
system
verification
mode
to
verify
the
JS20
blade
server.
±001²
PERFORM
THE
CHECKOUT
PROCEDURE:
1.
Turn
off
the
server,
making
sure
to
first
turn
off
all
external
devices,
if
attached.
2.
Check
all
cables
and
power
cords.
3.
Turn
on
all
external
devices;
then,
turn
on
the
blade
server.
4.
Start
the
Serial
Over
Lan
(SOL)
console
for
the
blade
server
to
be
tested
and
check
for
the
following
responses:
a.
Progress
codes
are
displayed
on
the
console.
b.
AIX
or
Linux
login
prompt
appears.
±002²
DID
THE
LINUX
OR
AIX
LOGIN
PROMPT
APPEAR?
YES.
38
BladeCenter
JS20
Type
8842:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide