• One 16 GB ECC UDIMM in DIMM slot 1
• One power supply
• One power cord
• One 3.5-inch SATA drive in drive bay 0
• One system front fan (if debugging is out of chassis)
Step 3. 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 minimum configuration, replace the components in the minimum
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 try 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 port LEDs on the rear panel of the server. These LEDs indicate whether there is
a problem with the connector, cable, or hub.
• The link 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 activity LED is lit when the Ethernet controller sends or receives data over the Ethernet
network. If the activity LED is off, make sure that the hub and network are operating and that the
correct device drivers are installed.
Step 5. Check for operating-system-specific causes of the problem, and also make sure that the operating
system drivers are installed correctly.
Step 6. 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.
Troubleshooting by symptom
Use this information to find solutions to problems that have identifiable symptoms.
To use the symptom-based troubleshooting information in this section, complete the following steps:
1. Review this section to find the symptoms that you are experiencing, and follow the suggested actions to
resolve the issue.
2. If the problem persists, contact support (see
“Contacting Support” on page 188).
170
ThinkSystem ST45 V3 User Guide
To Next Page
Loading...
