IBM JS20 Hardware Maintenance Manual - Page 50

Checkpoints, Accessing, Linux, system, error, Service

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

Note: The service processor runs on its own power boundary and continually monitors hardware attributes and the environmental conditions within the system. The service processor is controlled by firmware and does not require the operating system to be operational to perform its tasks. POST After power is turned on and before the operating system is loaded, the system does a power-on self-test (POST). This test performs checks to ensure that the hardware is functioning correctly before the operating system is started. During POST, a POST screen displays, and POST indicators appear on the Serial Over LAN (SOL) console (if one is connected). The next section describes the POST indicators and functions that can be accessed during POST. Checkpoints The system firmware uses checkpoints (progress codes and error codes) to indicate the status of the system. These codes can appear only on the Serial Over Lan (SOL) console. Firmware error codes and messages indicate that a problem exists; they are not intended to be used to identify a failing part. Checkpoints display in the system console from the time ac power is connected to the system until the operating system login prompt is displayed after a successful operating system boot. These checkpoints have the following forms: Exxx Exxx checkpoints indicate that a system processor is in control and is initializing the system resources. Control is being passed to the operating system when E105 displays on the operator panel display. Location code information may also display on the operator panel during this time (see "Physical location codes" on page 154). Error codes If a fault is detected, an 8-digit error code is displayed in the BladeCenter management module event log. A location code might be displayed at the same time on the second line. The management-module log, which can be accessed through the Blade Center unit, contains the most recent error codes and messages that the system generated during POST. Accessing the Linux system error log If the system information LED is lit, do one of the following: 1. Check for an entry in the BladeCenter management-module event log. If the information in this log is either a four-digit or eight-digit error code, go directly to "Firmware checkpoint (progress) codes" on page 94 or "Firmware error codes" on page 102. 2. Go to "General checkout" on page 37. Service aids and the Linux system error log Linux on pSeries® service aids for hardware diagnostics are available for customers who have installed and are running Linux. Users can install these free diagnostics tools for effective diagnosis and repair of their system in the rare instance when a system error occurs. This service aid toolkit provides the key tools required to take advantage of the inherent pSeries hardware reliability, availability, and serviceability (RAS) functions as outlined in the Linux on pSeries RAS Whitepaper, available from 40 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:
The
service
processor
runs
on
its
own
power
boundary
and
continually
monitors
hardware
attributes
and
the
environmental
conditions
within
the
system.
The
service
processor
is
controlled
by
firmware
and
does
not
require
the
operating
system
to
be
operational
to
perform
its
tasks.
POST
After
power
is
turned
on
and
before
the
operating
system
is
loaded,
the
system
does
a
power-on
self-test
(POST).
This
test
performs
checks
to
ensure
that
the
hardware
is
functioning
correctly
before
the
operating
system
is
started.
During
POST,
a
POST
screen
displays,
and
POST
indicators
appear
on
the
Serial
Over
LAN
(SOL)
console
(if
one
is
connected).
The
next
section
describes
the
POST
indicators
and
functions
that
can
be
accessed
during
POST.
Checkpoints
The
system
firmware
uses
checkpoints
(progress
codes
and
error
codes)
to
indicate
the
status
of
the
system.
These
codes
can
appear
only
on
the
Serial
Over
Lan
(SOL)
console.
Firmware
error
codes
and
messages
indicate
that
a
problem
exists;
they
are
not
intended
to
be
used
to
identify
a
failing
part.
Checkpoints
display
in
the
system
console
from
the
time
ac
power
is
connected
to
the
system
until
the
operating
system
login
prompt
is
displayed
after
a
successful
operating
system
boot.
These
checkpoints
have
the
following
forms:
Exxx
Exxx
checkpoints
indicate
that
a
system
processor
is
in
control
and
is
initializing
the
system
resources.
Control
is
being
passed
to
the
operating
system
when
E105
displays
on
the
operator
panel
display.
Location
code
information
may
also
display
on
the
operator
panel
during
this
time
(see
“Physical
location
codes”
on
page
154).
Error
codes
If
a
fault
is
detected,
an
8-digit
error
code
is
displayed
in
the
BladeCenter
management
module
event
log.
A
location
code
might
be
displayed
at
the
same
time
on
the
second
line.
The
management-module
log,
which
can
be
accessed
through
the
Blade
Center
unit,
contains
the
most
recent
error
codes
and
messages
that
the
system
generated
during
POST.
Accessing
the
Linux
system
error
log
If
the
system
information
LED
is
lit,
do
one
of
the
following:
1.
Check
for
an
entry
in
the
BladeCenter
management-module
event
log.
If
the
information
in
this
log
is
either
a
four-digit
or
eight-digit
error
code,
go
directly
to
“Firmware
checkpoint
(progress)
codes”
on
page
94
or
“Firmware
error
codes”
on
page
102.
2.
Go
to
“General
checkout”
on
page
37.
Service
aids
and
the
Linux
system
error
log
Linux
on
pSeries
®
service
aids
for
hardware
diagnostics
are
available
for
customers
who
have
installed
and
are
running
Linux.
Users
can
install
these
free
diagnostics
tools
for
effective
diagnosis
and
repair
of
their
system
in
the
rare
instance
when
a
system
error
occurs.
This
service
aid
toolkit
provides
the
key
tools
required
to
take
advantage
of
the
inherent
pSeries
hardware
reliability,
availability,
and
serviceability
(RAS)
functions
as
outlined
in
the
Linux
on
pSeries
RAS
Whitepaper,
available
from
40
BladeCenter
JS20
Type
8842:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide