IBM 8872 Service Guide - Page 75

Diagnostic, programs, messages, error, codes, Running, diagnostic, programs

Get IBM 8872 - eServer xSeries 460 PDF manuals and user guides
UPC - 000435813060
View all IBM 8872 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 75 highlights

Diagnostic programs, messages, and error codes The server diagnostic programs are the primary method of testing the major components of the server. As you run the diagnostic programs, text messages and error codes are displayed on the screen and are saved in the test log. A diagnostic text message or error code indicates that a problem has been detected; to determine what action you should take as a result of a message or error code, see the table in "Diagnostic error codes" on page 60. Running the diagnostic programs To run the diagnostic programs, complete the following steps: 1. If the server is running, turn off the server and all attached devices. 2. Turn on all attached devices; then, turn on the server. 3. When the prompt F2 for Diagnostics appears, press F2. If you have set both a power-on password and an administrator password, you must type the administrator password to run the diagnostic programs. 4. From the top of the screen, select either Extended or Basic. 5. From the diagnostic programs screen, select the test that you want to run, and follow the instructions on the screen. When you are diagnosing hard disk drives, select SCSI Fixed Disk Test for the most thorough test. Select Fixed Disk Test for any of the following situations: v You want to run a faster test. v The server contains RAID arrays. v The server contains SATA or IDE hard disk drives. To determine what action you should take as a result of a diagnostic text message or error code, see the table in "Diagnostic error codes" on page 60. If the diagnostic programs do not detect any hardware errors but the problem remains during normal server operations, a software error might be the cause. If you suspect a software problem, see the information that comes with your software. A single problem might cause more than one error message. When this happens, correct the cause of the first error message. The other error messages usually will not occur the next time you run the diagnostic programs. Exception: If there are multiple error codes or light path diagnostics LEDs that indicate a microprocessor error, the error might be in a microprocessor or in a microprocessor socket. See "Microprocessor problems" on page 42 for information about diagnosing microprocessor problems. If the server stops during testing and you cannot continue, restart the server and try running the diagnostic programs again. If the problem remains, replace the component that was being tested when the server stopped. The keyboard and mouse (pointing device) tests assume that a keyboard and mouse are attached to the server. If no mouse or a USB mouse is attached to the server, you cannot use the Next Cat and Prev Cat buttons to select categories. All other mouse-selectable functions are available through function keys. You can use the regular keyboard test to test a USB keyboard, and you can use the regular mouse test to test a USB mouse. You can run the USB interface test only if no USB devices are attached. The USB test will not run if a Remote Supervisor Adapter II SlimLine is installed. Chapter 2. Diagnostics 59

  • 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
Diagnostic
programs,
messages,
and
error
codes
The
server
diagnostic
programs
are
the
primary
method
of
testing
the
major
components
of
the
server.
As
you
run
the
diagnostic
programs,
text
messages
and
error
codes
are
displayed
on
the
screen
and
are
saved
in
the
test
log.
A
diagnostic
text
message
or
error
code
indicates
that
a
problem
has
been
detected;
to
determine
what
action
you
should
take
as
a
result
of
a
message
or
error
code,
see
the
table
in
“Diagnostic
error
codes”
on
page
60.
Running
the
diagnostic
programs
To
run
the
diagnostic
programs,
complete
the
following
steps:
1.
If
the
server
is
running,
turn
off
the
server
and
all
attached
devices.
2.
Turn
on
all
attached
devices;
then,
turn
on
the
server.
3.
When
the
prompt
F2
for
Diagnostics
appears,
press
F2.
If
you
have
set
both
a
power-on
password
and
an
administrator
password,
you
must
type
the
administrator
password
to
run
the
diagnostic
programs.
4.
From
the
top
of
the
screen,
select
either
Extended
or
Basic
.
5.
From
the
diagnostic
programs
screen,
select
the
test
that
you
want
to
run,
and
follow
the
instructions
on
the
screen.
When
you
are
diagnosing
hard
disk
drives,
select
SCSI
Fixed
Disk
Test
for
the
most
thorough
test.
Select
Fixed
Disk
Test
for
any
of
the
following
situations:
v
You
want
to
run
a
faster
test.
v
The
server
contains
RAID
arrays.
v
The
server
contains
SATA
or
IDE
hard
disk
drives.
To
determine
what
action
you
should
take
as
a
result
of
a
diagnostic
text
message
or
error
code,
see
the
table
in
“Diagnostic
error
codes”
on
page
60.
If
the
diagnostic
programs
do
not
detect
any
hardware
errors
but
the
problem
remains
during
normal
server
operations,
a
software
error
might
be
the
cause.
If
you
suspect
a
software
problem,
see
the
information
that
comes
with
your
software.
A
single
problem
might
cause
more
than
one
error
message.
When
this
happens,
correct
the
cause
of
the
first
error
message.
The
other
error
messages
usually
will
not
occur
the
next
time
you
run
the
diagnostic
programs.
Exception:
If
there
are
multiple
error
codes
or
light
path
diagnostics
LEDs
that
indicate
a
microprocessor
error,
the
error
might
be
in
a
microprocessor
or
in
a
microprocessor
socket.
See
“Microprocessor
problems”
on
page
42
for
information
about
diagnosing
microprocessor
problems.
If
the
server
stops
during
testing
and
you
cannot
continue,
restart
the
server
and
try
running
the
diagnostic
programs
again.
If
the
problem
remains,
replace
the
component
that
was
being
tested
when
the
server
stopped.
The
keyboard
and
mouse
(pointing
device)
tests
assume
that
a
keyboard
and
mouse
are
attached
to
the
server.
If
no
mouse
or
a
USB
mouse
is
attached
to
the
server,
you
cannot
use
the
Next
Cat
and
Prev
Cat
buttons
to
select
categories.
All
other
mouse-selectable
functions
are
available
through
function
keys.
You
can
use
the
regular
keyboard
test
to
test
a
USB
keyboard,
and
you
can
use
the
regular
mouse
test
to
test
a
USB
mouse.
You
can
run
the
USB
interface
test
only
if
no
USB
devices
are
attached.
The
USB
test
will
not
run
if
a
Remote
Supervisor
Adapter
II
SlimLine
is
installed.
Chapter
2.
Diagnostics
59