• 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) 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 156.
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 internal connectors” on page 25 for more information. If you suspect that the
UEFI firmware is corrupted, see “Recovering the server firmware (UEFI update failure)” on page 160.
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.
Note:
The minimum configuration required for the server to start is one microprocessor and one 2
GB DIMM.
Step 4.
Turn on the server. If the problem remains, suspect the following components in the following order:
1. Power supply
2. Memory
158
System x3500 M5 Installation and Service Guide
Содержание System x3500 M5 Type 5464
Страница 1: ...System x3500 M5 Installation and Service Guide Machine Type 5464 ...
Страница 6: ...iv System x3500 M5 Installation and Service Guide ...
Страница 16: ...xiv System x3500 M5 Installation and Service Guide ...
Страница 140: ...124 System x3500 M5 Installation and Service Guide ...
Страница 194: ...178 System x3500 M5 Installation and Service Guide ...
Страница 1056: ...1040 System x3500 M5 Installation and Service Guide ...
Страница 1214: ...1198 System x3500 M5 Installation and Service Guide ...
Страница 1218: ...1202 System x3500 M5 Installation and Service Guide ...
Страница 1225: ...People s Republic of China Class A electronic emission statement Taiwan Class A compliance statement Appendix E Notices 1209 ...
Страница 1226: ...Taiwan BSMI RoHS declaration 1210 System x3500 M5 Installation and Service Guide ...
Страница 1235: ......
Страница 1236: ......