IBM 8872 Service Guide - Page 104

Solving, problems, power, Ethernet, controller

Get IBM 8872 - eServer xSeries 460 PDF manuals and user guides
UPC - 000435813060
View all IBM 8872 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 104 highlights

Solving SCSI problems Note: This information also applies to Serial Attached SCSI (SAS) problems. For any SCSI error message, one or more of the following devices might be causing the problem: v A failing SCSI device (adapter, drive, or controller) v An incorrect SCSI termination jumper setting v Duplicate SCSI IDs in the same SCSI chain v A missing or incorrectly installed SCSI terminator v A defective SCSI terminator v An incorrectly installed cable v A defective cable For any SCSI error message, follow these suggested actions in the order in which they are listed until the problem is solved: 1. Make sure that external SCSI devices are turned on before you turn on the server. 2. Make sure that the cables for all external SCSI devices are connected correctly. 3. If an external SCSI device is attached, make sure that the external SCSI termination is set to automatic. 4. Make sure that the last device in each SCSI chain is terminated correctly. 5. Make sure that the SCSI devices are configured correctly. Solving power problems Power problems can be difficult to solve. For example, a short circuit can exist anywhere on any of the power distribution buses. Usually, a short circuit will cause the power subsystem to shut down because of an overcurrent condition. To diagnose a power problem, use the following general procedure: 1. Turn off the server and disconnect all ac power cords. 2. Check for loose cables in the power subsystem. Also check for short circuits, for example, if a loose screw is causing a short circuit on a circuit board. 3. Remove the adapters and disconnect the cables and power cords to all internal and external devices until the server is at the minimum configuration that is required for the server to start (see "Solving undetermined problems" on page 90 for the minimum configuration). 4. Reconnect all ac power cords and turn on the server. If the server starts successfully, replace the adapters and devices one at a time until the problem is isolated. If the server does not start from the minimum configuration, replace the components in the minimum configuration one at a time until the problem is isolated. Solving Ethernet controller problems The method that you use to test the Ethernet controller depends on which operating system you are using. See the operating-system documentation for information about Ethernet controllers, and see the Ethernet controller device-driver readme file. Try the following procedures: 88 IBM xSeries 460 Type 8872 and xSeries MXE 460 Type 8874: Problem Determination and Service Guide

  • 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
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
Solving
SCSI
problems
Note:
This
information
also
applies
to
Serial
Attached
SCSI
(SAS)
problems.
For
any
SCSI
error
message,
one
or
more
of
the
following
devices
might
be
causing
the
problem:
v
A
failing
SCSI
device
(adapter,
drive,
or
controller)
v
An
incorrect
SCSI
termination
jumper
setting
v
Duplicate
SCSI
IDs
in
the
same
SCSI
chain
v
A
missing
or
incorrectly
installed
SCSI
terminator
v
A
defective
SCSI
terminator
v
An
incorrectly
installed
cable
v
A
defective
cable
For
any
SCSI
error
message,
follow
these
suggested
actions
in
the
order
in
which
they
are
listed
until
the
problem
is
solved:
1.
Make
sure
that
external
SCSI
devices
are
turned
on
before
you
turn
on
the
server.
2.
Make
sure
that
the
cables
for
all
external
SCSI
devices
are
connected
correctly.
3.
If
an
external
SCSI
device
is
attached,
make
sure
that
the
external
SCSI
termination
is
set
to
automatic.
4.
Make
sure
that
the
last
device
in
each
SCSI
chain
is
terminated
correctly.
5.
Make
sure
that
the
SCSI
devices
are
configured
correctly.
Solving
power
problems
Power
problems
can
be
difficult
to
solve.
For
example,
a
short
circuit
can
exist
anywhere
on
any
of
the
power
distribution
buses.
Usually,
a
short
circuit
will
cause
the
power
subsystem
to
shut
down
because
of
an
overcurrent
condition.
To
diagnose
a
power
problem,
use
the
following
general
procedure:
1.
Turn
off
the
server
and
disconnect
all
ac
power
cords.
2.
Check
for
loose
cables
in
the
power
subsystem.
Also
check
for
short
circuits,
for
example,
if
a
loose
screw
is
causing
a
short
circuit
on
a
circuit
board.
3.
Remove
the
adapters
and
disconnect
the
cables
and
power
cords
to
all
internal
and
external
devices
until
the
server
is
at
the
minimum
configuration
that
is
required
for
the
server
to
start
(see
“Solving
undetermined
problems”
on
page
90
for
the
minimum
configuration).
4.
Reconnect
all
ac
power
cords
and
turn
on
the
server.
If
the
server
starts
successfully,
replace
the
adapters
and
devices
one
at
a
time
until
the
problem
is
isolated.
If
the
server
does
not
start
from
the
minimum
configuration,
replace
the
components
in
the
minimum
configuration
one
at
a
time
until
the
problem
is
isolated.
Solving
Ethernet
controller
problems
The
method
that
you
use
to
test
the
Ethernet
controller
depends
on
which
operating
system
you
are
using.
See
the
operating-system
documentation
for
information
about
Ethernet
controllers,
and
see
the
Ethernet
controller
device-driver
readme
file.
Try
the
following
procedures:
88
IBM
xSeries
460
Type
8872
and
xSeries
MXE
460
Type
8874:
Problem
Determination
and
Service
Guide