IBM x3655 Service Guide - Page 195

Solving, undetermined, problems

Page 195 highlights

v Make sure that the device drivers on the client and server are using the same protocol. If the Ethernet controller still cannot connect to the network but the hardware appears to be working, the network administrator must investigate other possible causes of the error. Solving undetermined problems If the diagnostic tests did not diagnose the failure or if the server is inoperative, use the information in this section. If you suspect that a software problem is causing failures (continuous or intermittent), see "Software problems" on page 137. Damaged data in CMOS memory or damaged BIOS code can cause undetermined problems. To reset the CMOS data, use the password override jumper to override the power-on password and clear the CMOS memory, see "System-board jumpers" on page 13. If you suspect that the BIOS code is damaged, see "Recovering the BIOS code" on page 156. Check the LEDs on all the power supplies (see "Power-supply LEDs" on page 142). If the LEDs indicate that the power supplies are working correctly, complete the following steps: 1. Turn off the server. 2. Make sure that the server is cabled correctly. 3. Remove or disconnect the following devices, one at a time, until you find the failure. Turn on the server and reconfigure it each time. v Any external devices. v Surge-suppressor device (on the server). v Modem, printer, mouse, and non-IBM devices. v Each adapter. v Hard disk drives. v Memory modules. The minimum configuration requirement is 1 GB (two 512 MB DIMM, in DIMM slots 1 and 2). v Service processor (Remote Supervisor Adapter II SlimLine). The following minimum configuration is required for the server to start: v One microprocessor v Two 512 MB DIMMs v One power supply v Power backplane v Power cord v ServeRAID SAS controller 4. Turn on the server. If the problem remains, suspect the following components in the following order: a. Power backplane b. Memory card (DIMM) c. System board If the problem is solved when you remove an adapter from the server but the problem recurs when you reinstall the same adapter, suspect the adapter; if the problem recurs when you replace the adapter with a different one, suspect the riser card. Chapter 5. Diagnostics 177

  • 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
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212

v
Make
sure
that
the
device
drivers
on
the
client
and
server
are
using
the
same
protocol.
If
the
Ethernet
controller
still
cannot
connect
to
the
network
but
the
hardware
appears
to
be
working,
the
network
administrator
must
investigate
other
possible
causes
of
the
error.
Solving
undetermined
problems
If
the
diagnostic
tests
did
not
diagnose
the
failure
or
if
the
server
is
inoperative,
use
the
information
in
this
section.
If
you
suspect
that
a
software
problem
is
causing
failures
(continuous
or
intermittent),
see
“Software
problems”
on
page
137.
Damaged
data
in
CMOS
memory
or
damaged
BIOS
code
can
cause
undetermined
problems.
To
reset
the
CMOS
data,
use
the
password
override
jumper
to
override
the
power-on
password
and
clear
the
CMOS
memory,
see
“System-board
jumpers”
on
page
13.
If
you
suspect
that
the
BIOS
code
is
damaged,
see
“Recovering
the
BIOS
code”
on
page
156.
Check
the
LEDs
on
all
the
power
supplies
(see
“Power-supply
LEDs”
on
page
142).
If
the
LEDs
indicate
that
the
power
supplies
are
working
correctly,
complete
the
following
steps:
1.
Turn
off
the
server.
2.
Make
sure
that
the
server
is
cabled
correctly.
3.
Remove
or
disconnect
the
following
devices,
one
at
a
time,
until
you
find
the
failure.
Turn
on
the
server
and
reconfigure
it
each
time.
v
Any
external
devices.
v
Surge-suppressor
device
(on
the
server).
v
Modem,
printer,
mouse,
and
non-IBM
devices.
v
Each
adapter.
v
Hard
disk
drives.
v
Memory
modules.
The
minimum
configuration
requirement
is
1
GB
(two
512
MB
DIMM,
in
DIMM
slots
1
and
2).
v
Service
processor
(Remote
Supervisor
Adapter
II
SlimLine).
The
following
minimum
configuration
is
required
for
the
server
to
start:
v
One
microprocessor
v
Two
512
MB
DIMMs
v
One
power
supply
v
Power
backplane
v
Power
cord
v
ServeRAID
SAS
controller
4.
Turn
on
the
server.
If
the
problem
remains,
suspect
the
following
components
in
the
following
order:
a.
Power
backplane
b.
Memory
card
(DIMM)
c.
System
board
If
the
problem
is
solved
when
you
remove
an
adapter
from
the
server
but
the
problem
recurs
when
you
reinstall
the
same
adapter,
suspect
the
adapter;
if
the
problem
recurs
when
you
replace
the
adapter
with
a
different
one,
suspect
the
riser
card.
Chapter
5.
Diagnostics
177