Solving undetermined problems

Use this information to solve undetermined problems.

Isolating problem to the Flex System x222 Compute Node

Note: When you are diagnosing a problem in the compute node, you must determine whether the problem is in the Flex System x222 Compute Node or in the Flex System chassis.

If the Flex System chassis contains more than one compute node and only one of the compute nodes has the problem, troubleshoot the compute node that has the problem.

If DSA did not diagnose the failure or if the Flex System x222 Compute Node is inoperative, use the information in this topic.

If you suspect that a software problem is causing failures (continuous or intermittent), see Software problems.

Corrupted data in CMOS memory or corrupted UEFI code can cause undetermined problems. To reset the CMOS data in the upper or lower compute node, remove and replace the CMOS battery in the upper or lower compute node to override the power-on password and clear the CMOS memory; see Removing a CMOS battery. If you suspect that the UEFI code is corrupted, see Recovering a UEFI image.

Check the LEDs on all the power supplies of the Flex System chassis in which the Flex System x222 Compute Node is installed. If the LEDs indicate that the power supplies are working correctly and reseating the Flex System x222 Compute Node does not correct the problem, complete the following steps:
  1. If no LEDs on the control panel of the Flex System x222 Compute Node are working, try to turn on the upper or lower compute node from the Chassis Management Module (see the documentation for the Flex System chassis and Chassis Management Module for more information).
  2. Turn off the upper and lower compute nodes.
  3. Remove the Flex System x222 Compute Node from the Flex System chassis and remove the upper compute node.
  4. Remove or disconnect the following devices in the upper and lower compute nodes, one at a time, until you find the failure. Reinstall, turn on, and reconfigure the upper and lower compute nodes each time.
    • I/O expansion adapter.
    • Hard disk drives.
    • DIMMs. The minimum configuration requirement is 4 GB for each compute node (one 4 GB DIMM each on the upper and lower system boards).

    The following minimum configuration is required for the upper or lower compute node to start:

    • System board
    • One microprocessor
    • One 4 GB DIMM
    • A functioning Flex System chassis
  5. Install and turn on the Flex System x222 Compute Node. If the problem remains, suspect the following components in the following order:
    1. DIMM
    2. System board
    3. Microprocessor

If the problem is solved when you remove an I/O expansion adapter from the compute node but the problem recurs when you reinstall the same adapter, suspect the I/O expansion adapter; if the problem recurs when you replace the adapter with a different one, suspect the system board.

If you suspect a networking problem and the compute node passes all the system tests, suspect a network cabling problem that is external to the system.

Any undetermined problem

Complete the following steps until the problem is solved.
  1. Check the IMM event log and follow the suggested actions to resolve any event codes (see IMM event log).
  2. Try to find the symptoms that you are experiencing in Troubleshooting by symptom and follow the suggested actions to resolve any problems.
  3. If the problem remains, submit a service request (see Getting help and technical assistance).

Compute nodes are not discovered by the Flex System Manager management node or the CMM

Complete the following steps until the problem is solved.
  1. Make sure that the compute node is recognized by the Flex System Manager management node (if installed) or the CMM. It may appear as an unknown device in the chassis map. If it is not recognized, perform the following steps.
    1. Remove the Flex System x222 Compute Node and inspect both the compute node and the back of the compute node bay to ensure there is no physical damage to connectors.
    2. Move the Flex System x222 Compute Node to another bay.
    3. Replace the system-board assembly that is not discoverable (see Removing a system-board assembly and Installing a system-board assembly).
  2. Make sure that the Flex System Manager management node or the CMM can ping the compute nodes, if they cannot, see Cannot ping the Flex System Manager management node on the management network.
  3. If the compute nodes are in another chassis, make sure that you have the proper software entitlements to manage that chassis with the Flex System Manager management node.
  4. Check the Lenovo Support Portal for any firmware updates that might apply to this issue. You can view the release notes for a firmware update to determine the issues that are addressed by the update.
  5. Check the Lenovo Support Portal for any service bulletins that are related to network connectivity.
Parent topic: Troubleshooting