IBM HC10 Service Guide - Page 55

Diagnostics

Page 55 highlights

Chapter 5. Diagnostics This chapter describes the diagnostic tools that are available to help you solve problems that might occur in the blade workstation. Note: The blade workstation uses shared resources that are installed in the BladeCenter unit. Problems with these shared resources might appear to be in the blade workstation (see "Solving shared BladeCenter resource problems" on page 75 for information about isolating problems with these resources). See the Problem Determination and Service Guide or the Hardware Maintenance Manual and Troubleshooting Guide for your BladeCenter unit and other BladeCenter component documentation for diagnostic procedures for shared BladeCenter components. If you cannot locate and correct the problem using the information in this chapter, see Appendix A, "Getting help and technical assistance," on page 83 for more information. Diagnostic tools The following tools are available to help you diagnose and solve hardware-related problems: v POST beep codes, error messages, and error logs The power-on self-test (POST) generates beep codes and messages to indicate successful test completion or the detection of a problem. See "POST" for more information. v Troubleshooting tables These tables list problem symptoms and actions to correct the problems. See "Troubleshooting tables" on page 56 for more information. v Diagnostic programs, messages, and error codes The diagnostic programs are the primary method of testing the major components of the blade workstation. These programs are stored in read-only memory (ROM) on the blade workstation. See "Diagnostic programs, messages, and error codes" on page 68 for more information. POST When you turn on the blade workstation, it performs a series of tests to check the operation of the blade workstation components and some optional devices in the blade workstation. This series of tests is called the power-on self-test, or POST. If a power-on password is set, you must type the password and press Enter, when prompted, for POST to run. If POST is completed without detecting any problems, a single beep sounds, and the blade workstation startup is completed. If POST detects a problem, more than one beep might sound, or an error message is displayed. See "Beep code descriptions" on page 40 and "POST error codes" on page 43 for more information. © Copyright IBM Corp. 2007 39

  • 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

Chapter
5.
Diagnostics
This
chapter
describes
the
diagnostic
tools
that
are
available
to
help
you
solve
problems
that
might
occur
in
the
blade
workstation.
Note:
The
blade
workstation
uses
shared
resources
that
are
installed
in
the
BladeCenter
unit.
Problems
with
these
shared
resources
might
appear
to
be
in
the
blade
workstation
(see
“Solving
shared
BladeCenter
resource
problems”
on
page
75
for
information
about
isolating
problems
with
these
resources).
See
the
Problem
Determination
and
Service
Guide
or
the
Hardware
Maintenance
Manual
and
Troubleshooting
Guide
for
your
BladeCenter
unit
and
other
BladeCenter
component
documentation
for
diagnostic
procedures
for
shared
BladeCenter
components.
If
you
cannot
locate
and
correct
the
problem
using
the
information
in
this
chapter,
see
Appendix
A,
“Getting
help
and
technical
assistance,”
on
page
83
for
more
information.
Diagnostic
tools
The
following
tools
are
available
to
help
you
diagnose
and
solve
hardware-related
problems:
v
POST
beep
codes,
error
messages,
and
error
logs
The
power-on
self-test
(POST)
generates
beep
codes
and
messages
to
indicate
successful
test
completion
or
the
detection
of
a
problem.
See
“POST”
for
more
information.
v
Troubleshooting
tables
These
tables
list
problem
symptoms
and
actions
to
correct
the
problems.
See
“Troubleshooting
tables”
on
page
56
for
more
information.
v
Diagnostic
programs,
messages,
and
error
codes
The
diagnostic
programs
are
the
primary
method
of
testing
the
major
components
of
the
blade
workstation.
These
programs
are
stored
in
read-only
memory
(ROM)
on
the
blade
workstation.
See
“Diagnostic
programs,
messages,
and
error
codes”
on
page
68
for
more
information.
POST
When
you
turn
on
the
blade
workstation,
it
performs
a
series
of
tests
to
check
the
operation
of
the
blade
workstation
components
and
some
optional
devices
in
the
blade
workstation.
This
series
of
tests
is
called
the
power-on
self-test,
or
POST.
If
a
power-on
password
is
set,
you
must
type
the
password
and
press
Enter,
when
prompted,
for
POST
to
run.
If
POST
is
completed
without
detecting
any
problems,
a
single
beep
sounds,
and
the
blade
workstation
startup
is
completed.
If
POST
detects
a
problem,
more
than
one
beep
might
sound,
or
an
error
message
is
displayed.
See
“Beep
code
descriptions”
on
page
40
and
“POST
error
codes”
on
page
43
for
more
information.
©
Copyright
IBM
Corp.
2007
39