IBM eServer xSeries 335 Type 8676, Руководство по техническому обслуживанию и ремонту

Страница: 41 / 178

Power checkout
Power problems can be difficult to solve. For example, a short circuit can exist
anywhere on any of the power distribution buses. Usually a short circuit will cause
the power subsystem to shut down because of an overcurrent condition.
A general procedure for troubleshooting power problems is as follows:
1. Turn off the server and disconnect all ac power cords.
2. Check for loose cables in the power subsystem. Also check for short circuits, for
example, if there is a loose screw causing a short circuit on a circuit board.
3. Remove adapters and disconnect the cables and power connectors to all
internal and external devices until the server is at the minimum configuration
required to start the server (see “Minimum operating requirements” on page
112).
4. Reconnect all ac power cords and turn on the server. If the server starts up
successfully, replace adapters and devices one at a time until the problem is
isolated. If the server does not start up from the minimal configuration, replace
FRUs of minimal configuration one at a time until the problem is isolated.
To use this method, it is important to know the minimum configuration required for a
system to start (see page 112).
Troubleshooting the Ethernet controller
This section provides troubleshooting information for problems that might occur with
the 10/100/1000 Mbps Ethernet controller.
Ethernet plug wrap test
The way the Ethernet controller is tested depends on which operating system you
are using (see the Ethernet controller device driver README file).
You can use the Ethernet wrap test to determine if a hardware problem is causing
the Ethernet connection to fail. To perform the Ethernet wrap test, use the wrap
plug (FRU 60G3981) with the diagnostic tests.
If this testing method indicates that the hardware is functioning normally but the
problem still exists, see “Network connection problems” or inform the network
administrator.
Network connection problems
If the Ethernet controller cannot connect to the network, check the following
conditions:
v
Make sure that the cable is installed correctly.
The network 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 either 100 Mbps or 1000 Mbps,
you must use Category 5 or higher cabling.
v 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.
v Check the Ethernet controller LEDs on the rear of the server.
Chapter 3. Diagnostics
31