Lenovo ThinkServer RD120 Hardware Maintenance Manual for RD120 - Page 212

Solving Ethernet controller problems, Solving undetermined problems, appears to be working

Get Lenovo ThinkServer RD120 PDF manuals and user guides View all Lenovo ThinkServer RD120 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 212 highlights

Solving Ethernet controller problems The method that you use to test the Ethernet controller depends on which operating system you are using. See the operating-system documentation for information about Ethernet controllers, and see the Ethernet controller device-driver readme file. Try the following procedures: 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. - You must use Category 5 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 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 Ethernet activity LED on the rear of the server. The Ethernet activity LED is lit when data is active on the Ethernet network. If the Ethernet 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. Solving undetermined problems If the diagnostic tests did not diagnose the failure or if the server is inoperative, use the information in this section. If you suspect that a software problem is causing failures (continuous or intermittent), see "Software problems" on page 160. Damaged data in CMOS memory or damaged BIOS code can cause undetermined problems. To reset the CMOS data, use the CMOS jumper to clear the CMOS memory and override the power-on password; see "System-board switches and jumpers" on page 13. If you suspect that the BIOS code is damaged, see "Recovering the BIOS code" on page 181. Check the LEDs on all the power supplies (see "Power-supply LEDs" on page 167). If the LEDs indicate that the power supplies are working correctly, complete the following steps: 1. Turn off the server. 2. Make sure that the server is cabled correctly. 194 ThinkServer RD120 server Machine Types 6444, 6445, 6446, and 6447: Hardware Maintenance Manual

  • 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
Solving Ethernet controller problems
The method that you use to test the Ethernet controller depends on which operating
system you are using. See the operating-system documentation for information
about Ethernet controllers, and see the Ethernet controller device-driver readme file.
Try the following procedures:
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.
–
You must use Category 5 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 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 Ethernet activity LED on the rear of the server. The Ethernet activity
LED is lit when data is active on the Ethernet network. If the Ethernet 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.
Solving undetermined problems
If the diagnostic tests did not diagnose the failure or if the server is inoperative, use
the information in this section.
If you suspect that a software problem is causing failures (continuous or
intermittent), see “Software problems” on page 160.
Damaged data in CMOS memory or damaged BIOS code can cause undetermined
problems. To reset the CMOS data, use the CMOS jumper to clear the CMOS
memory and override the power-on password; see “System-board switches and
jumpers” on page 13. If you suspect that the BIOS code is damaged, see
“Recovering the BIOS code” on page 181.
Check the LEDs on all the power supplies (see “Power-supply LEDs” on page 167).
If the LEDs indicate that the power supplies are working correctly, complete the
following steps:
1.
Turn off the server.
2.
Make sure that the server is cabled correctly.
194
ThinkServer RD120 server Machine Types 6444, 6445, 6446, and 6447: Hardware Maintenance Manual