Table of Contents
Advertisement
v Determine whether the hub supports auto-negotiation. If it does not, try
v Check the Ethernet controller LEDs on the rear panel of the server. These LEDs
v Check for operating-system-specific causes of the problem.
v Make sure that the device drivers on the client and server are using the same
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 "Power problems" on page 254.
Corrupted data in CMOS memory or corrupted UEFI firmware can cause
undetermined problems. To reset the CMOS data, use the CMOS jumper to clear
the CMOS memory and override the power-on password; see "System-board
jumpers" on page 27. If you suspect that the UEFI firmware is corrupted, see
"Recovering the server firmware" on page 261.
If the power supplies are working correctly, complete the following steps:
1. Turn off the server.
2. Make sure that the server cover is closed and latched correctly.
3. Make sure that the server top cover/power cut-off switch cable is connected
4. Make sure that the server is cabled correctly.
5. Remove or disconnect the following devices, one at a time, until you find the
6. Turn on the server.
configuring the integrated Ethernet controller manually to match the speed and
duplex mode of the hub.
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.
protocol.
correctly.
failure. Turn on the server and reconfigure it each time.
v Any external devices.
v Surge-suppressor device (on the server).
v Printer, mouse, and non-IBM devices.
v Each adapter.
v Hard disk drives.
v Memory modules. The minimum configuration requirement is 2 GB DIMM
in slot 1 when one microprocessor is installed in the server.
Chapter 4. Troubleshooting
259
Advertisement
Table of Contents
Troubleshooting
