Lenovo System x3850 X6 Installation And Service Manual page 199

Table 46. Symptoms and user actions for observable problems (continued)
• Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
• See Chapter 5 "Parts listing, System x3850 X6 and x3950 X6 Type 6241" on page 201 to determine which
components are customer replaceable units (CRU) and which components are field replaceable units (FRU).
• If an action step is preceded by (Trained service technician only), that step must be performed only by a
Trained service technician.
Symptom
Fans - Clicking, or rattling
noise.
Visible physical damage;
Broken, damaged, or
malfunctioning door, bezel,
cover, or chassis part.
Server is unresponsive (POST
is complete and operating
system is running)
Action
1. This server has redundant hot-swap cooling. Remove and replace each fan
assembly, one at a time, to determine which assembly is causing the noise.
a. Make sure that the fan assembly causing the noise does not have an
obstruction (cable, cable label, etc) touching the fan blades during operation.
b. Replace the fan assembly.
2. If the noise can not be associated with a single fan assembly, it might be
coming from the cooling fans in a power supply.
If the part is a CRU, replace it. If the part is a FRU, the part must be replaced by a
trained service technician (see Chapter 5 "Parts listing, System x3850 X6 and x3950
X6 Type 6241" on page 201 to determine whether the part is a FRU or a CRU and
Chapter 6 "Removing and replacing components" on page 221.)
If you are in the same location as the server, complete the following steps:
1. If you are using a KVM connection, make sure that the connection is operating
correctly. Otherwise, make sure that the keyboard and mouse are operating
correctly.
2. If possible, log in to the server and verify that all applications are running (no
applications are hung).
3. Restart the server.
4. If the problem remains, make sure that any new software has been installed and
configured correctly.
5. Contact your place of purchase of the software or your software provider.
If you are accessing the server from a remote location, complete the following steps:
1. Make sure that all applications are running (no applications are hung).
2. Attempt to log out of the system and log back in.
3. Validate the network access by pinging or running a trace route to the server
from a command line.
a. If you are unable to get a response during a ping test, attempt to ping
another server in the chassis to determine whether it is a connection
problem or server problem.
b. Run a trace route to determine where the connection breaks down. Attempt
to resolve a connection issue with either the VPN or the point at which the
connection breaks down.
4. Restart the server remotely through the management interface.
5. If the problem remains, verify that any new software has been installed and
configured correctly.
6. Contact your place of purchase of the software or your software provider.
.
Chapter 4 Troubleshooting
185