Solving power problems
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. To
diagnose a power problem, use the following general procedure:
1. Turn off the server and disconnect all power cords.
2. Check for loose cables in the power subsystem. Also check for short circuits, for
example, if a loose screw is causing a short circuit on a circuit board.
3. If a power error LED on the system board is lit, complete the following steps;
otherwise, go to step 5. See “System-board LEDs” on page 20 for the location
of the power error LEDs.
a. Disconnect the cables and power cords to all internal and external devices
(see “Internal cable routing and connectors” on page 136). Leave the
power-supply cords connected.
b. Remove each component that is associated with the LED, one at a time,
restarting the server each time, until the cause of the overcurrent condition
is identified.
Important:
Only a trained service technician should remove or replace a
FRU, such as a microprocessor or the system board. See Chapter 4, “Parts
listing, Type 7377 server,” on page 125 to determine whether a component
is a FRU.
c. Replace the identified component.
4. If the system-error LED on the front panel is lit, complete the following steps:
a. Check the IMM-event log. To access the web interface, see “Logging on to
the Web interface” on page 245.
b. If a log indicates that the power configuration is invalid, make sure that both
power supplies installed in the server are of the same type.
5. Remove the adapters and disconnect the cables and power cords to all internal
and external devices until the server is at the minimum configuration that is
required for the server to start (see “Solving undetermined problems” on page
121 for the minimum configuration).
6. Reconnect all power cords and turn on the server. If the server starts
successfully, replace 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.
Solving 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.
Try the following procedures:
v
Make sure that the correct and current device drivers and firmware, which come
with the server, are installed and that they are at the latest level.
Important:
Some cluster solutions require specific code levels or coordinated
code updates. If the device is part of a cluster solution, verify that the latest level
of code is supported for the cluster solution before you update the code.
v
Make sure that the Ethernet cable is installed correctly.
120
IBM System x3630 M3 Type 7377: Problem Determination and Service Guide
Summary of Contents for x3630 M3 7377
Page 1: ...IBM System x3630 M3 Type 7377 Problem Determination and Service Guide ...
Page 2: ......
Page 3: ...IBM System x3630 M3 Type 7377 Problem Determination and Service Guide ...
Page 40: ...22 IBM System x3630 M3 Type 7377 Problem Determination and Service Guide ...
Page 142: ...124 IBM System x3630 M3 Type 7377 Problem Determination and Service Guide ...
Page 250: ...232 IBM System x3630 M3 Type 7377 Problem Determination and Service Guide ...
Page 293: ......
Page 294: ... Part Number 00D3232 Printed in USA 1P P N 00D3232 ...