IBM JS20 User Guide - Page 59

Solving, problems

Page 59 highlights

Chapter 7. Solving problems This chapter provides basic troubleshooting information to help you solve some common problems that might occur while setting up your blade server. If you cannot locate and correct the problem using the information in this chapter, see the BladeCenter JS20 Type 8842 Hardware Maintenance Manual and Troubleshooting Guide that comes with the blade server, and the Server Support flowchart in the front of this book. A problem with the BladeCenter JS20 Type 8842 might relate to either the BladeCenter JS20 Type 8842 or the BladeCenter unit. v A blade-server problem exists if the BladeCenter unit contains more than one blade server and only one of the blade servers has the symptom. v If all of the blade servers have the same symptom, then the problem relates to the BladeCenter unit. For more information, see the Hardware Maintenance Manual and Troubleshooting Guide or Problem Determination and Service Guide for your BladeCenter unit. For troubleshooting information about other BladeCenter components, see the Hardware Maintenance Manual and Troubleshooting Guide or Problem Determination and Service Guide for your BladeCenter unit, product-specific documentation, and other related documentation. For the latest editions of the IBM BladeCenter documentation, go to http://www.ibm.com/support on the World Wide Web. See "Related documentation" on page 2 for additional information. Important: If you cannot access the CD drive on the BladeCenter unit, contact a service support representative for assistance. Diagnostic tools overview The following tools are available to help you identify and solve hardware-related problems: v Power-on self-test (POST) firmware checkpoints and error codes The firmware checkpoints are progress codes that your blade server displays during POST. See "Checkpoint codes" on page 49 for more information. v Firmware error codes and location codes For detailed descriptions of the firmware error codes, see "Firmware error codes" on page 65. Some firmware error codes also include location codes. The location code information is required to identify the failing component. Check the system error logs and event logs to determine the location code information that corresponds to the firmware error code. v Troubleshooting charts These charts list problem symptoms and steps to correct the problems. See the "Troubleshooting charts" on page 77 for more information. v Light path diagnostics Use light path diagnostics to diagnose system errors. See "Light path diagnostics overview" on page 80 for more information. © Copyright IBM Corp. 2006 47

  • 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

Chapter
7.
Solving
problems
This
chapter
provides
basic
troubleshooting
information
to
help
you
solve
some
common
problems
that
might
occur
while
setting
up
your
blade
server.
If
you
cannot
locate
and
correct
the
problem
using
the
information
in
this
chapter,
see
the
BladeCenter
JS20
Type
8842
Hardware
Maintenance
Manual
and
Troubleshooting
Guide
that
comes
with
the
blade
server,
and
the
Server
Support
flowchart
in
the
front
of
this
book.
A
problem
with
the
BladeCenter
JS20
Type
8842
might
relate
to
either
the
BladeCenter
JS20
Type
8842
or
the
BladeCenter
unit.
v
A
blade-server
problem
exists
if
the
BladeCenter
unit
contains
more
than
one
blade
server
and
only
one
of
the
blade
servers
has
the
symptom.
v
If
all
of
the
blade
servers
have
the
same
symptom,
then
the
problem
relates
to
the
BladeCenter
unit.
For
more
information,
see
the
Hardware
Maintenance
Manual
and
Troubleshooting
Guide
or
Problem
Determination
and
Service
Guide
for
your
BladeCenter
unit.
For
troubleshooting
information
about
other
BladeCenter
components,
see
the
Hardware
Maintenance
Manual
and
Troubleshooting
Guide
or
Problem
Determination
and
Service
Guide
for
your
BladeCenter
unit,
product-specific
documentation,
and
other
related
documentation.
For
the
latest
editions
of
the
IBM
BladeCenter
documentation,
go
to
on
the
World
Wide
Web.
See
“Related
documentation”
on
page
2
for
additional
information.
Important:
If
you
cannot
access
the
CD
drive
on
the
BladeCenter
unit,
contact
a
service
support
representative
for
assistance.
Diagnostic
tools
overview
The
following
tools
are
available
to
help
you
identify
and
solve
hardware-related
problems:
v
Power-on
self-test
(POST)
firmware
checkpoints
and
error
codes
The
firmware
checkpoints
are
progress
codes
that
your
blade
server
displays
during
POST.
See
“Checkpoint
codes”
on
page
49
for
more
information.
v
Firmware
error
codes
and
location
codes
For
detailed
descriptions
of
the
firmware
error
codes,
see
“Firmware
error
codes”
on
page
65.
Some
firmware
error
codes
also
include
location
codes.
The
location
code
information
is
required
to
identify
the
failing
component.
Check
the
system
error
logs
and
event
logs
to
determine
the
location
code
information
that
corresponds
to
the
firmware
error
code.
v
Troubleshooting
charts
These
charts
list
problem
symptoms
and
steps
to
correct
the
problems.
See
the
“Troubleshooting
charts”
on
page
77
for
more
information.
v
Light
path
diagnostics
Use
light
path
diagnostics
to
diagnose
system
errors.
See
“Light
path
diagnostics
overview”
on
page
80
for
more
information.
©
Copyright
IBM
Corp.
2006
47