IBM 79717au User Guide - Page 67

Solving, problems

Get IBM 79717au - Servers Blade Server Opteron 2.8ghz PDF manuals and user guides
UPC - 883436004305
View all IBM 79717au manuals
Add to My Manuals
Save this manual to your list of manuals

Page 67 highlights

Chapter 6. Solving problems This chapter provides basic information about the diagnostic tools that are available to help you solve some common problems that might occur while you are setting up the blade server. If you install the blade server in the BladeCenter unit and the blade server does not start, perform the following actions: v Make sure that the BladeCenter unit is correctly connected to a power source. v Reseat the blade server in the BladeCenter unit (see "Installing the blade server in a BladeCenter unit" on page 40). v If the power-on LED is flashing slowly, turn on the blade server (see "Turning on the blade server" on page 13). v If you have just added a new optional device or component, make sure that it is correctly installed and compatible with the blade server and its components. If the device or component is not compatible, remove it from the blade server, reinstall the blade server in the BladeCenter unit, and then restart the blade server. If the blade server does not start after you have performed the preceding actions, see the Problem Determination and Service Guide on the BladeCenter Documentation CD. Diagnostic tools overview The following tools are available to help you diagnose and solve hardware-related problems: v POST beep codes The power-on self-test beep codes can indicate the detection of a problem. - One beep indicates successful completion of POST - Repeating long beeps indicate a memory error. Make sure that all DIMMs are correctly installed. - Additional beep codes are listed under "Diagnostics" in the Problem Determination and Service Guide for your blade server type. v POST error codes The POST error codes indicate the detection of a problem. See the Problem Determination and Service Guide for more information. v ServerGuide problems The table in "ServerGuide problems" on page 56 lists problem symptoms and steps to correct the problems. v Troubleshooting tables Use the troubleshooting tables to find solutions to problems that have identifiable symptoms. These tables are in the Problem Determination and Service Guide for your blade server. © Copyright IBM Corp. 2006 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
Chapter
6.
Solving
problems
This
chapter
provides
basic
information
about
the
diagnostic
tools
that
are
available
to
help
you
solve
some
common
problems
that
might
occur
while
you
are
setting
up
the
blade
server.
If
you
install
the
blade
server
in
the
BladeCenter
unit
and
the
blade
server
does
not
start,
perform
the
following
actions:
v
Make
sure
that
the
BladeCenter
unit
is
correctly
connected
to
a
power
source.
v
Reseat
the
blade
server
in
the
BladeCenter
unit
(see
“Installing
the
blade
server
in
a
BladeCenter
unit”
on
page
40).
v
If
the
power-on
LED
is
flashing
slowly,
turn
on
the
blade
server
(see
“Turning
on
the
blade
server”
on
page
13).
v
If
you
have
just
added
a
new
optional
device
or
component,
make
sure
that
it
is
correctly
installed
and
compatible
with
the
blade
server
and
its
components.
If
the
device
or
component
is
not
compatible,
remove
it
from
the
blade
server,
reinstall
the
blade
server
in
the
BladeCenter
unit,
and
then
restart
the
blade
server.
If
the
blade
server
does
not
start
after
you
have
performed
the
preceding
actions,
see
the
Problem
Determination
and
Service
Guide
on
the
BladeCenter
Documentation
CD.
Diagnostic
tools
overview
The
following
tools
are
available
to
help
you
diagnose
and
solve
hardware-related
problems:
v
POST
beep
codes
The
power-on
self-test
beep
codes
can
indicate
the
detection
of
a
problem.
–
One
beep
indicates
successful
completion
of
POST
–
Repeating
long
beeps
indicate
a
memory
error.
Make
sure
that
all
DIMMs
are
correctly
installed.
–
Additional
beep
codes
are
listed
under
“Diagnostics”
in
the
Problem
Determination
and
Service
Guide
for
your
blade
server
type.
v
POST
error
codes
The
POST
error
codes
indicate
the
detection
of
a
problem.
See
the
Problem
Determination
and
Service
Guide
for
more
information.
v
ServerGuide
problems
The
table
in
“ServerGuide
problems”
on
page
56
lists
problem
symptoms
and
steps
to
correct
the
problems.
v
Troubleshooting
tables
Use
the
troubleshooting
tables
to
find
solutions
to
problems
that
have
identifiable
symptoms.
These
tables
are
in
the
Problem
Determination
and
Service
Guide
for
your
blade
server.
©
Copyright
IBM
Corp.
2006
55