Complete the following steps until the problem is solved.
- If you recently installed, moved, or serviced the computer node,
reseat the compute node in the bay. If the compute node was not recently
installed, moved, or serviced, perform a virtual reseat through the
CMM service command. For more information about the CMM service command,
see the "Flex System Chassis Management Module: Command-Line
Interface Reference Guide".
- Check the event logs for any events that are related to the compute
node, and solve them. If a management node is available, check the
event log on the management node. Otherwise, check the event log on
the Chassis Management Module.
- Make sure that the CMM can
recognize the compute node. Log in to the CMM user
interface and verify that the compute node appears in the chassis
view. If the CMM cannot
recognize the compute node, remove the compute node and inspect the
compute node and the back of the node bay to make sure there is no
physical damage to the connectors.
- Make sure that the power policy that is implemented on the CMM is
sufficient to enable the compute node to power on. You can view the
power policy from the CMM pmpolicy command and the CMM web
interface.
- Make sure that the management node has completed the discovery
of the compute node. Log in to the management node user interface
and verify that the compute node appears in the list of manageable
systems.
- Replace the base assembly (see Removing and replacing the base assembly).
Note: Until you are able to replace the system-board
assembly, you can attempt to power on the compute node from the CMM or
from the management node user interface.
For additional information, see UEFI Compliant Firmware on System x® and BladeCenter®
Servers and the Flex System Quick start guides.