Ethernet Controller Troubleshooting Chart - IBM eserver xSeries 350 User Reference Manual

Hide thumbs Also See for eserver xSeries 350:
Table of Contents

Advertisement

Ethernet controller troubleshooting chart

You can use the following troubleshooting chart to find solutions to 10/100 Mbps
Ethernet controller problems that have definite symptoms.
Table 19. Ethernet troubleshooting chart.
Ethernet controller problem
The server stops running
when loading device drivers.
Ethernet-link status light
does not illuminate.
118
IBM® xSeries 350: User's Reference
— 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.
— The Ethernet speed light illuminates when the Ethernet controller LAN speed
is 100 Mbps.
Make sure that you are using the correct device drivers, which are supplied with
your server.
Check for operating system-specific causes for the problem.
Make sure that the device drivers on the client and server are using the same
protocol.
Test the Ethernet controller.
How you test the Ethernet controller depends on which operating system you are
using (see the Ethernet controller device driver README file).
The PCI BIOS interrupt settings are incorrect.
Check the following:
Determine if the interrupt (IRQ) setting that is assigned to the Ethernet controller
is also assigned to another device in the Configuration/Setup Utility program.
Although interrupt sharing is allowed for PCI devices, some devices do not
function well when they share an interrupt with a dissimilar PCI device. Try
changing the IRQ that is assigned to the Ethernet controller or the other device. For
example, for NetWare Versions 3 and 4, it is recommended that disk controllers not
share interrupts with LAN controllers.
Make sure that you are using the most recent device driver that is available from
the World Wide Web.
Run the network diagnostic program.
If the problem remains, call for service.
Check the following:
Make sure that the hub is turned on.
Check all connections at the Ethernet controller and the hub.
Check the cable. A crossover cable is required unless the hub has an X designation.
Use another port on the hub.
If the hub does not support auto-negotiation, manually configure the Ethernet
controller to match the hub.
If you manually configured the duplex mode, make sure that you also manually
configure the speed.
Run diagnostics on the LEDs.
If the problem remains, call for service.
Suggested Action

Advertisement

Table of Contents
loading

Table of Contents