IBM 8872 Service Guide - Page 105

IBM 8872 - eServer xSeries 460 Manual

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 105 highlights

v Make sure that the correct device drivers, which come with the server are installed and that they are at the latest level. v Make sure that the Ethernet cable is installed correctly. - The 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 servers (without a hub), or if you are not using a hub with X ports, use a crossover cable. 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 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 panel of the server. These LEDs indicate whether there is a problem with the connector, cable, or hub. - The Ethernet link status LED 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. - The Ethernet transmit/receive activity LED is lit 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 installed. v Check the LAN activity LED on the rear of the server. The LAN activity LED is lit when data is active on the Ethernet network. If the LAN activity LED is off, make sure that the hub and network are operating and that the correct device drivers are installed. v Check for operating-system-specific causes of 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 but the hardware appears to be working, the network administrator must investigate other possible causes of the error. Chapter 2. Diagnostics 89

  • 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
v
Make
sure
that
the
correct
device
drivers,
which
come
with
the
server
are
installed
and
that
they
are
at
the
latest
level.
v
Make
sure
that
the
Ethernet
cable
is
installed
correctly.
–
The
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
servers
(without
a
hub),
or
if
you
are
not
using
a
hub
with
X
ports,
use
a
crossover
cable.
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
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
panel
of
the
server.
These
LEDs
indicate
whether
there
is
a
problem
with
the
connector,
cable,
or
hub.
–
The
Ethernet
link
status
LED
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.
–
The
Ethernet
transmit/receive
activity
LED
is
lit
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
installed.
v
Check
the
LAN
activity
LED
on
the
rear
of
the
server.
The
LAN
activity
LED
is
lit
when
data
is
active
on
the
Ethernet
network.
If
the
LAN
activity
LED
is
off,
make
sure
that
the
hub
and
network
are
operating
and
that
the
correct
device
drivers
are
installed.
v
Check
for
operating-system-specific
causes
of
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
but
the
hardware
appears
to
be
working,
the
network
administrator
must
investigate
other
possible
causes
of
the
error.
Chapter
2.
Diagnostics
89