IBM 8478 Hardware Maintenance Manual - Page 33

Diagnosing, errors, Troubleshooting, Ethernet, controller, Network, connection, problems

Get IBM 8478 - Eserver xSeries 200 PDF manuals and user guides
UPC - 087944650553
View all IBM 8478 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 33 highlights

Diagnosing errors To find solutions to problems that have definite symptoms, see "Error symptoms" on page 107. If you cannot find the problem there, go to "Starting the diagnostic programs" on page 15 to test the server. If you have just added new software or a new option and the server is not working, do the following before using the error symptoms table: v Remove the software or device that you just added. v Run the diagnostic tests to determine if the server is running correctly. v Reinstall the new software or new device. Troubleshooting the Ethernet controller This section provides troubleshooting information for problems that might occur with the 10/100 Mbps Ethernet controller. Network connection problems If the Ethernet controller cannot connect to the network, check 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 persists, 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 LAN activity light (if available) on the front of the server. The LAN activity light illuminates when the Ethernet controller sends or receives data over 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, supplied with your server. Chapter 3. Diagnostics 23

  • 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
Diagnosing
errors
To
find
solutions
to
problems
that
have
definite
symptoms,
see
“Error
symptoms”
on
page
107.
If
you
cannot
find
the
problem
there,
go
to
“Starting
the
diagnostic
programs”
on
page
15
to
test
the
server.
If
you
have
just
added
new
software
or
a
new
option
and
the
server
is
not
working,
do
the
following
before
using
the
error
symptoms
table:
v
Remove
the
software
or
device
that
you
just
added.
v
Run
the
diagnostic
tests
to
determine
if
the
server
is
running
correctly.
v
Reinstall
the
new
software
or
new
device.
Troubleshooting
the
Ethernet
controller
This
section
provides
troubleshooting
information
for
problems
that
might
occur
with
the
10/100
Mbps
Ethernet
controller.
Network
connection
problems
If
the
Ethernet
controller
cannot
connect
to
the
network,
check
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
persists,
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
LAN
activity
light
(if
available)
on
the
front
of
the
server.
The
LAN
activity
light
illuminates
when
the
Ethernet
controller
sends
or
receives
data
over
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,
supplied
with
your
server.
Chapter
3.
Diagnostics
23