Solving Ethernet controller problems
The method that you use to test the Ethernet controller depends on which operating system you are
using. For information about Ethernet controllers, see the Ethernet controller device-driver readme file and
the operating-system documentation.
Try the following procedures:
Step 1.
Make sure that the correct device drivers, which come with the server, are installed and that
they are at the latest level.
Step 2.
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.
Step 3.
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.
Step 4.
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 LED is off, make sure
that the hub and network are operating and that the correct device drivers are installed.
Step 5.
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.
Step 6.
Check for operating-system-specific causes of the problem.
Step 7.
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 Dynamic System Analysis (DSA) cannot diagnose the failure or if the server is inoperative, use the
information in this section to solve the undetermined problems.
If you suspect that a software problem is causing failures (continuous or intermittent), see “Software
problems” on page 71.
Corrupted data in CMOS memory or corrupted UEFI firmware can cause undetermined problems. To reset
the CMOS data, use the CMOS clear jumper (JP1) to clear the CMOS memory and override the power-on
password. See “System-board connectors” on page 21 for more information. If you suspect that the UEFI
firmware is corrupted, see “Recovering the server firmware (UEFI update failure)” on page 74.
If the power supplies are working properly, do the following:
72
Lenovo System x3250 M6 Installation and Service Guide
Summary of Contents for x3250 m6
Page 1: ...Lenovo System x3250 M6 Installation and Service Guide Machine Types 3633 and 3943 ...
Page 6: ...iv Lenovo System x3250 M6 Installation and Service Guide ...
Page 18: ...4 Lenovo System x3250 M6 Installation and Service Guide ...
Page 60: ...46 Lenovo System x3250 M6 Installation and Service Guide ...
Page 100: ...86 Lenovo System x3250 M6 Installation and Service Guide ...
Page 516: ...502 Lenovo System x3250 M6 Installation and Service Guide ...
Page 678: ...664 Lenovo System x3250 M6 Installation and Service Guide ...
Page 685: ...Taiwan Class A compliance statement Appendix E Notices 671 ...
Page 695: ......
Page 696: ......