IBM 86884RX Maintenance Manual - Page 85

Troubleshooting, Ethernet, controller, Network, connection, problems

Get IBM 86884RX - Eserver xSeries 450 PDF manuals and user guides View all IBM 86884RX manuals
Add to My Manuals
Save this manual to your list of manuals

Page 85 highlights

Troubleshooting the Ethernet controller If a problem occurs with the 10/100/1000 Mbps Ethernet controller, use the Ethernet diagnostic program on the Resource CD to diagnose the problem. For more information about this CD, see "Ethernet diagnostic tests" on page 70. For information about the Ethernet error codes and actions to take, see the documentation on the Resource CD. Network connection problems If the Ethernet controller cannot connect to the network, check the following conditions: 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 either 100 Mbps or 1000 Mbps, you must use Category 5 or higher cabling. v Determine whether the hub supports auto-negotiation. If it does not, try configuring the integrated Ethernet controller manually to match the speed and duplex mode of the hub. v Check the Ethernet controller LEDs on the rear of the server. These LEDs indicate whether a problem exists with the connector, cable, or hub. - The Ethernet transmit/receive activity LED on the rear of the server is lit when the Ethernet controller sends or receives data over the Ethernet network. If the Ethernet transmit/receive activity LED is off, make sure that the hub and network are operating and that the correct device drivers are installed. - The Ethernet link status LED on the rear of the server is lit when the Ethernet controller receives a LINK pulse from the hub. If the LED is off, there might be a defective connector or cable or a problem with the hub. v Make sure that you are using the correct device drivers, which are supplied with your 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. v Test the Ethernet controller. The way the Ethernet controller is tested depends on which operating system you are using (see the Ethernet controller device driver README files). Chapter 3. Diagnostics 75

  • 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
Troubleshooting
the
Ethernet
controller
If
a
problem
occurs
with
the
10/100/1000
Mbps
Ethernet
controller,
use
the
Ethernet
diagnostic
program
on
the
Resource
CD
to
diagnose
the
problem.
For
more
information
about
this
CD,
see
“Ethernet
diagnostic
tests”
on
page
70.
For
information
about
the
Ethernet
error
codes
and
actions
to
take,
see
the
documentation
on
the
Resource
CD.
Network
connection
problems
If
the
Ethernet
controller
cannot
connect
to
the
network,
check
the
following
conditions:
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
either
100
Mbps
or
1000
Mbps,
you
must
use
Category
5
or
higher
cabling.
v
Determine
whether
the
hub
supports
auto-negotiation.
If
it
does
not,
try
configuring
the
integrated
Ethernet
controller
manually
to
match
the
speed
and
duplex
mode
of
the
hub.
v
Check
the
Ethernet
controller
LEDs
on
the
rear
of
the
server.
These
LEDs
indicate
whether
a
problem
exists
with
the
connector,
cable,
or
hub.
–
The
Ethernet
transmit/receive
activity
LED
on
the
rear
of
the
server
is
lit
when
the
Ethernet
controller
sends
or
receives
data
over
the
Ethernet
network.
If
the
Ethernet
transmit/receive
activity
LED
is
off,
make
sure
that
the
hub
and
network
are
operating
and
that
the
correct
device
drivers
are
installed.
–
The
Ethernet
link
status
LED
on
the
rear
of
the
server
is
lit
when
the
Ethernet
controller
receives
a
LINK
pulse
from
the
hub.
If
the
LED
is
off,
there
might
be
a
defective
connector
or
cable
or
a
problem
with
the
hub.
v
Make
sure
that
you
are
using
the
correct
device
drivers,
which
are
supplied
with
your
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.
v
Test
the
Ethernet
controller.
The
way
the
Ethernet
controller
is
tested
depends
on
which
operating
system
you
are
using
(see
the
Ethernet
controller
device
driver
README
files).
Chapter
3.
Diagnostics
75