• 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 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) 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 102.
Corrupted data in CMOS memory or corrupted UEFI firmware can cause undetermined problems. To reset
the CMOS data, use the CMOS clear jumper (J11) to clear the CMOS memory and override the power-on
password; see Table 2 “System board jumpers” on page 36 for more information. If you suspect that the
UEFI firmware is corrupted, see “Recovering the server firmware (UEFI update failure)” on page 108.
If the power supplies are working correctly, complete the following steps:
Step 1.
Turn off the server.
Step 2.
Make sure that the server is cabled correctly.
Step 3.
Remove or disconnect the following devices, one at a time, until you find the failure. Turn on the
server and reconfigure it each time.
• Any external devices.
• Surge-suppressor device (on the server).
• Printer, mouse, and non-Lenovo devices.
• Each adapter.
• Hard disk drives.
• Memory modules. The minimum configuration requirement is 4 GB DIMM in DIMM slot 1.
Step 4.
Turn on the server.
106
Lenovo System x3650 M5 Installation and Service Guide
Summary of Contents for x3650 M5
Page 1: ...Lenovo System x3650 M5 Installation and Service Guide Machine Type 8871 ...
Page 47: ...Figure 35 System board switches jumpers and buttons Chapter 1 The System x3650 M5 server 35 ...
Page 60: ...48 Lenovo System x3650 M5 Installation and Service Guide ...
Page 80: ...68 Lenovo System x3650 M5 Installation and Service Guide ...
Page 124: ...112 Lenovo System x3650 M5 Installation and Service Guide ...
Page 146: ...134 Lenovo System x3650 M5 Installation and Service Guide ...
Page 1322: ...1310 Lenovo System x3650 M5 Installation and Service Guide ...
Page 1330: ...Taiwan BSMI RoHS declaration 1318 Lenovo System x3650 M5 Installation and Service Guide ...
Page 1339: ......
Page 1340: ......