IBM 8669 Hardware Maintenance Manual - Page 28

Ethernet controller troubleshooting chart, Ethernet controller problem, Suggested Action

Get IBM 8669 - Eserver xSeries 342 PDF manuals and user guides
UPC - 087944636496
View all IBM 8669 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 28 highlights

The way you test the Ethernet controller depends on which operating system you are using (see the Ethernet controller device driver README file). The Ethernet wrap test can be used to determine if a hardware problem is causing the Ethernet connection to fail. To perform the Ethernet wrap test, use the wrap plug (FRU # 60G3981) in conjunction with the diagnostic tests. If the testing methods above indicate that the hardware is functioning normally but the problem still exists, inform the network administrator. 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 1. Ethernet troubleshooting chart Ethernet controller problem Suggested Action The server stops running when loading device drivers. The PCI BIOS interrupt settings are incorrect. Check the following: v Determine if the interrupt (IRQ) setting 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 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. v Make sure that you are using the most recent device driver available from the World Wide Web. v Run the network diagnostic program. Ethernet Link Status light does not light. If the problem remains, go to "Starting the diagnostic programs" on page 15 to run the diagnostic programs. Check the following: v Make sure that the hub is turned on. v Check all connections at the Ethernet controller and the hub. v Check the cable. A crossover cable is required unless the hub has an X designation. v Use another port on the hub. v If the hub does not support auto-negotiation, manually configure the Ethernet controller to match the hub. v If you manually configured the duplex mode, make sure that you also manually configure the speed. v Run diagnostics on the LEDs. If the problem remains, go to "Starting the diagnostic programs" on page 15 to run the diagnostic programs. The Ethernet Transmit/Receive Activity light does not light. Check the following: Note: The Ethernet Transmit/Receive Activity LED illuminates only when data is sent to or by this Ethernet controller. v Make sure that you have loaded the network device drivers. v The network might be idle. Try sending data from this workstation. v Run diagnostics on the LEDs. v The function of this LED can be changed by device driver load parameters. If necessary, remove any LED parameter settings when you load the device drivers. Data is incorrect or sporadic. Check the following: v Make sure that you are using Category 5 cabling when operating the server at 100 Mbps. v Make sure that the cables do not run close to noise-inducing sources like fluorescent lights. 18 Hardware Maintenance Manual: xSeries 342 Type 8669

  • 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
The way you test the Ethernet controller depends on which operating system you
are using (see the Ethernet controller device driver README file).
The Ethernet wrap test can be used to determine if a hardware problem is
causing the Ethernet connection to fail. To perform the Ethernet wrap test, use
the wrap plug (FRU # 60G3981) in conjunction with the diagnostic tests.
If the testing methods above indicate that the hardware is functioning normally
but the problem still exists, inform the network administrator.
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 1. Ethernet troubleshooting chart
Ethernet controller problem
Suggested Action
The server stops running
when loading device drivers.
The PCI BIOS interrupt settings are incorrect.
Check the following:
v
Determine if the interrupt (IRQ) setting 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 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.
v
Make sure that you are using the most recent device driver available from the
World Wide Web.
v
Run the network diagnostic program.
If the problem remains, go to “Starting the diagnostic programs” on page 15 to run
the diagnostic programs.
Ethernet Link Status light
does not light.
Check the following:
v
Make sure that the hub is turned on.
v
Check all connections at the Ethernet controller and the hub.
v
Check the cable. A crossover cable is required unless the hub has an
X
designation.
v
Use another port on the hub.
v
If the hub does not support auto-negotiation, manually configure the Ethernet
controller to match the hub.
v
If you manually configured the duplex mode, make sure that you also manually
configure the speed.
v
Run diagnostics on the LEDs.
If the problem remains, go to “Starting the diagnostic programs” on page 15 to run
the diagnostic programs.
The Ethernet
Transmit/Receive Activity light
does not light.
Check the following:
Note:
The Ethernet Transmit/Receive Activity LED illuminates only when data is sent
to or by this Ethernet controller.
v
Make sure that you have loaded the network device drivers.
v
The network might be idle. Try sending data from this workstation.
v
Run diagnostics on the LEDs.
v
The function of this LED can be changed by device driver load parameters. If
necessary, remove any LED parameter settings when you load the device drivers.
Data is incorrect or sporadic.
Check the following:
v
Make sure that you are using Category 5 cabling when operating the server at 100
Mbps.
v
Make sure that the cables do not run close to noise-inducing sources like
fluorescent lights.
18
Hardware Maintenance Manual: xSeries 342 Type 8669