Resolving Suspected Ethernet Controller Problems - Lenovo ThinkSystem SD650 V3 User Manual

Neptune dwc tray
Hide thumbs Also See for ThinkSystem SD650 V3:
Table of Contents

Advertisement

Complete the following steps to diagnose and resolve a suspected power problem.
Step 1.
Check the event log and resolve any errors related to the power.
Note: Start with the event log of the application that is managing the server. For more information
about event logs, see
Step 2.
Check for short circuits, for example, if a loose screw is causing a short circuit on a circuit board.
Step 3.
Remove the adapters and disconnect the cables and power cords to all internal and external
devices until the server is at the minimal configuration for debugging that is required for the server
to start. To determine the minimal configuration for your server, see "Minimal configuration for
debugging" in
Step 4.
Reconnect all AC power cords and turn on the server. If the server starts successfully, reseat the
adapters and devices one at a time until the problem is isolated.
If the server does not start from the minimal configuration, replace the components in the minimal
configuration one at a time until the problem is isolated.

Resolving suspected 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.
Complete the following steps to attempt to resolve suspected problems with the Ethernet controller.
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 or 1000 Mbps, you must use Category
5 cabling.
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 server. These LEDs indicate whether there is a problem
with the connector, cable, or hub.
Ethernet controller LED locations are specified in
diagnostics display" on page
• 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 Network activity LED on the server. The Network activity LED is lit when data is active on
the Ethernet network. If the Network activity LED is off, make sure that the hub and network are
operating and that the correct device drivers are installed.
Network activity LED location is specified in
display" on page
Step 6.
Check for operating-system-specific causes of the problem, and also make sure that the operating
system drivers are installed correctly.
"Event logs" on page
"Technical specifications" on page
211.
211.
209.
4.
"Troubleshooting by system LEDs and
"Troubleshooting by system LEDs and diagnostics
Chapter 8
.
Problem determination
225

Advertisement

Table of Contents
loading

Table of Contents