Observable problems

Use this information to solve observable problems.

Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.

  • Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
  • See Parts listing, Types 7917, 7167, 2590 and 2584 to determine which components are customer replaceable units (CRU) and which components are field replaceable units (FRU) that must be replaced only by a trained service technician.
  • If an action step is preceded by "(Trained service technician only)," that step must be performed only by a trained service technician.
Symptom Action
Compute node is unresponsive (POST is complete and operating system is running)
If you are in the same location as the compute node, 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 compute node and verify that all applications are running (no applications are hung).
  3. Restart the compute node.
  4. 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 compute node 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 compute node from a command line:
    1. If you are unable to get a response during a ping test, attempt to ping another compute node in the chassis to determine whether it is a connection problem or compute node problem.
    2. 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 compute node 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.
Unusual smell

An unusual smell might be coming from newly installed equipment. If the problem remains, contact IBM Support.
Compute node seems to be running hot

Multiple compute nodes or chassis:

  1. Make sure that the room temperature is within the specified range (see Features and specifications).
  2. Check the IBM® Flex System Manager management software or CMM event log for rising temperature events. If there are no events, the compute node is running within normal operating temperatures. Note that you can expect some variation in temperature.

Single compute node:

Check the IBM Flex System Manager management software or CMM event log for rising temperature events. If there are no events, the compute node is running within normal operating temperatures. Note that you can expect some variation in temperature.

Cracked parts or cracked chassis Contact IBM Support.
Parent topic: Troubleshooting by symptom