IBM QS21 Service Guide - Page 81

Diagnostic, messages, Viewing, error

Get IBM QS21 - BladeCenter - 0792 PDF manuals and user guides
UPC - 883436016940
View all IBM QS21 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 81 highlights

5. When the boot prompt appears, press enter, type dsa and press enter again. Alternatively you can wait for the timeout to expire. 6. The command line interface prompt will then appear on the SOL connection. The BladeCenter QS21 does not support the graphical user interface. 7. Follow the on screen directions to run preboot DSA. Diagnostics are run from within preboot DSA. When you are using the CPU or Memory stress tests, call your IBM service representative if you experience any system instability. To determine what action you should take as a result of a diagnostic text message, see "DSA error messages." Open firmware memory diagnostic results are output to the SOL connection. They are also logged in NVRAM. All NVRAM logs (more than just OF diags) are collected as part of the DSA merged log. 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. 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 Table 20 on page 90 for further 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. Diagnostic text messages Diagnostic text messages are displayed while the tests are running. A diagnostic text message contains one of the following results: v Passed: The test was completed without any errors v Failed: The test detected an error v Aborted: The test could not proceed because of the server configuration Additional information concerning test failures is available in the extended diagnostic results for each test. Viewing the test log To view the test log when the tests are completed, issue the view command from the DSA command line interface. DSA collections may also be transferred to an external USB device using the copy command from the DSA command line interface. DSA error messages The tables below describe the messages that the diagnostic programs might generate and suggested actions to correct the detected problems. Follow the suggested actions in the order given. Chapter 5. Diagnostics and troubleshooting 63

  • 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
5.
When
the
boot
prompt
appears,
press
enter,
type
dsa
and
press
enter
again.
Alternatively
you
can
wait
for
the
timeout
to
expire.
6.
The
command
line
interface
prompt
will
then
appear
on
the
SOL
connection.
The
BladeCenter
QS21
does
not
support
the
graphical
user
interface.
7.
Follow
the
on
screen
directions
to
run
preboot
DSA.
Diagnostics
are
run
from
within
preboot
DSA.
When
you
are
using
the
CPU
or
Memory
stress
tests,
call
your
IBM
service
representative
if
you
experience
any
system
instability.
To
determine
what
action
you
should
take
as
a
result
of
a
diagnostic
text
message,
see
“DSA
error
messages.”
Open
firmware
memory
diagnostic
results
are
output
to
the
SOL
connection.
They
are
also
logged
in
NVRAM.
All
NVRAM
logs
(more
than
just
OF
diags)
are
collected
as
part
of
the
DSA
merged
log.
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.
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
Table
20
on
page
90
for
further
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.
Diagnostic
text
messages
Diagnostic
text
messages
are
displayed
while
the
tests
are
running.
A
diagnostic
text
message
contains
one
of
the
following
results:
v
Passed
:
The
test
was
completed
without
any
errors
v
Failed
:
The
test
detected
an
error
v
Aborted
:
The
test
could
not
proceed
because
of
the
server
configuration
Additional
information
concerning
test
failures
is
available
in
the
extended
diagnostic
results
for
each
test.
Viewing
the
test
log
To
view
the
test
log
when
the
tests
are
completed,
issue
the
view
command
from
the
DSA
command
line
interface.
DSA
collections
may
also
be
transferred
to
an
external
USB
device
using
the
copy
command
from
the
DSA
command
line
interface.
DSA
error
messages
The
tables
below
describe
the
messages
that
the
diagnostic
programs
might
generate
and
suggested
actions
to
correct
the
detected
problems.
Follow
the
suggested
actions
in
the
order
given.
Chapter
5.
Diagnostics
and
troubleshooting
63