IBM 887022X Maintenance Manual - Page 87

IBM 887022X - Eserver xSeries 445 Manual

Page 87 highlights

If the problem still exists after checking the operating system documentation, try the following: v Make sure that the cable is installed correctly. The network cable must be securely attached at all connections. If the cable is attached but the problem remains, try a different cable. If you set the Ethernet controller to operate at 100 Mbps, you must use Category 5 cabling. If you directly connect two workstations (without a hub), or if you are not using a hub with X ports, use a crossover cable. Note: To determine whether a hub has an X port, check the port label. If the label contains an X, the hub has an X port. v Determine if the hub supports auto-negotiation. If not, try configuring the integrated Ethernet controller manually to match the speed and duplex mode of the hub. v Check the Ethernet controller lights on the server rear panel. These lights indicate whether a problem exists with the connector, cable, or hub. - The Ethernet Link Status light illuminates when the Ethernet controller receives a LINK pulse from the hub. If the light is off, there might be a defective connector or cable, or a problem with the hub. - The Ethernet Transmit/Receive Activity light illuminates when the Ethernet controller sends or receives data over the Ethernet Network. If the Ethernet Transmit/Receive Activity light is off, make sure that the hub and network are operating and that the correct device drivers are loaded. v Check the LAN activity light (if available) on the rear of the server. The LAN activity light is illuminated when data is active on the Ethernet network. If the LAN activity light is off, make sure that the hub and network are operating and that the correct device drivers are loaded. v Make sure that you are using the correct device drivers, which are supplied with the server. v Check for operating-system-specific causes for the problem. 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, inform the network administrator. Chapter 3. Diagnostics 77

  • 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
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324

If
the
problem
still
exists
after
checking
the
operating
system
documentation,
try
the
following:
v
Make
sure
that
the
cable
is
installed
correctly.
The
network
cable
must
be
securely
attached
at
all
connections.
If
the
cable
is
attached
but
the
problem
remains,
try
a
different
cable.
If
you
set
the
Ethernet
controller
to
operate
at
100
Mbps,
you
must
use
Category
5
cabling.
If
you
directly
connect
two
workstations
(without
a
hub),
or
if
you
are
not
using
a
hub
with
X
ports,
use
a
crossover
cable.
Note:
To
determine
whether
a
hub
has
an
X
port,
check
the
port
label.
If
the
label
contains
an
X
,
the
hub
has
an
X
port.
v
Determine
if
the
hub
supports
auto-negotiation.
If
not,
try
configuring
the
integrated
Ethernet
controller
manually
to
match
the
speed
and
duplex
mode
of
the
hub.
v
Check
the
Ethernet
controller
lights
on
the
server
rear
panel.
These
lights
indicate
whether
a
problem
exists
with
the
connector,
cable,
or
hub.
The
Ethernet
Link
Status
light
illuminates
when
the
Ethernet
controller
receives
a
LINK
pulse
from
the
hub.
If
the
light
is
off,
there
might
be
a
defective
connector
or
cable,
or
a
problem
with
the
hub.
The
Ethernet
Transmit/Receive
Activity
light
illuminates
when
the
Ethernet
controller
sends
or
receives
data
over
the
Ethernet
Network.
If
the
Ethernet
Transmit/Receive
Activity
light
is
off,
make
sure
that
the
hub
and
network
are
operating
and
that
the
correct
device
drivers
are
loaded.
v
Check
the
LAN
activity
light
(if
available)
on
the
rear
of
the
server.
The
LAN
activity
light
is
illuminated
when
data
is
active
on
the
Ethernet
network.
If
the
LAN
activity
light
is
off,
make
sure
that
the
hub
and
network
are
operating
and
that
the
correct
device
drivers
are
loaded.
v
Make
sure
that
you
are
using
the
correct
device
drivers,
which
are
supplied
with
the
server.
v
Check
for
operating-system-specific
causes
for
the
problem.
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,
inform
the
network
administrator.
Chapter
3.
Diagnostics
77