IBM HC10 Service Guide - Page 71

Checkout, procedure, About, checkout, Performing

Page 71 highlights

Checkout procedure The checkout procedure is the sequence of tasks that you should follow to diagnose a problem in the blade workstation. About the checkout procedure Before performing the checkout procedure for diagnosing hardware problems, review the following information: v Read the safety information that begins on page vii. v The diagnostic programs provide the primary methods of testing the major components of the blade workstation. If you are not sure whether a problem is caused by the hardware or by the software, you can use the diagnostic programs to confirm that the hardware is working correctly. v When you run the diagnostic programs, 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 that indicate a microprocessor error, the error might be in a microprocessor or in a microprocessor socket. See "Microprocessor problems" on page 59 for information about diagnosing microprocessor problems. v If the blade workstation is halted and a POST error code is displayed, see "POST error codes" on page 43. If the blade workstation is halted and no error message is displayed, see "Troubleshooting tables" on page 56 and "Solving undetermined problems" on page 80. v For intermittent problems, check the error log; see "POST" on page 39 and "Diagnostic programs, messages, and error codes" on page 68. v If no LEDs are lit on the blade workstation front panel, verify the blade workstation status and errors in the management-module Web interface; also see "Solving undetermined problems" on page 80. v If device errors occur, see "Troubleshooting tables" on page 56. Performing the checkout procedure To perform the checkout procedure, complete the following steps: 1. If the blade workstation is running, turn off the blade workstation. 2. Turn on the blade workstation. Make sure that the blade workstation has control of the video (the keyboard/video/mouse button is lit). If the blade workstation does not start, see "Troubleshooting tables" on page 56. 3. Record any POST beep codes that sound or POST error messages that are displayed on the monitor. If an error is displayed, look up the first error in the "POST error codes" on page 43. 4. Check for the following results: v Successful completion of POST, indicated by a single beep. v Successful completion of startup, indicated by a readable display of the operating-system desktop. 5. Did a single beep sound and are there readable instructions on the main menu? v No: Find the failure symptom in "Troubleshooting tables" on page 56; if necessary, see "Solving undetermined problems" on page 80. v Yes: Run the diagnostic programs (see "Running the diagnostic programs" on page 69). Chapter 5. Diagnostics 55

  • 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

Checkout
procedure
The
checkout
procedure
is
the
sequence
of
tasks
that
you
should
follow
to
diagnose
a
problem
in
the
blade
workstation.
About
the
checkout
procedure
Before
performing
the
checkout
procedure
for
diagnosing
hardware
problems,
review
the
following
information:
v
Read
the
safety
information
that
begins
on
page
vii.
v
The
diagnostic
programs
provide
the
primary
methods
of
testing
the
major
components
of
the
blade
workstation.
If
you
are
not
sure
whether
a
problem
is
caused
by
the
hardware
or
by
the
software,
you
can
use
the
diagnostic
programs
to
confirm
that
the
hardware
is
working
correctly.
v
When
you
run
the
diagnostic
programs,
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
that
indicate
a
microprocessor
error,
the
error
might
be
in
a
microprocessor
or
in
a
microprocessor
socket.
See
“Microprocessor
problems”
on
page
59
for
information
about
diagnosing
microprocessor
problems.
v
If
the
blade
workstation
is
halted
and
a
POST
error
code
is
displayed,
see
“POST
error
codes”
on
page
43.
If
the
blade
workstation
is
halted
and
no
error
message
is
displayed,
see
“Troubleshooting
tables”
on
page
56
and
“Solving
undetermined
problems”
on
page
80.
v
For
intermittent
problems,
check
the
error
log;
see
“POST”
on
page
39
and
“Diagnostic
programs,
messages,
and
error
codes”
on
page
68.
v
If
no
LEDs
are
lit
on
the
blade
workstation
front
panel,
verify
the
blade
workstation
status
and
errors
in
the
management-module
Web
interface;
also
see
“Solving
undetermined
problems”
on
page
80.
v
If
device
errors
occur,
see
“Troubleshooting
tables”
on
page
56.
Performing
the
checkout
procedure
To
perform
the
checkout
procedure,
complete
the
following
steps:
1.
If
the
blade
workstation
is
running,
turn
off
the
blade
workstation.
2.
Turn
on
the
blade
workstation.
Make
sure
that
the
blade
workstation
has
control
of
the
video
(the
keyboard/video/mouse
button
is
lit).
If
the
blade
workstation
does
not
start,
see
“Troubleshooting
tables”
on
page
56.
3.
Record
any
POST
beep
codes
that
sound
or
POST
error
messages
that
are
displayed
on
the
monitor.
If
an
error
is
displayed,
look
up
the
first
error
in
the
“POST
error
codes”
on
page
43.
4.
Check
for
the
following
results:
v
Successful
completion
of
POST,
indicated
by
a
single
beep.
v
Successful
completion
of
startup,
indicated
by
a
readable
display
of
the
operating-system
desktop.
5.
Did
a
single
beep
sound
and
are
there
readable
instructions
on
the
main
menu?
v
No:
Find
the
failure
symptom
in
“Troubleshooting
tables”
on
page
56;
if
necessary,
see
“Solving
undetermined
problems”
on
page
80.
v
Yes:
Run
the
diagnostic
programs
(see
“Running
the
diagnostic
programs”
on
page
69).
Chapter
5.
Diagnostics
55