Lenovo Flex System x220, Installation And Service Manual

Page: 623 / 714

3. If the problem remains, submit a service request (see Appendix A “Getting help and technical
assistance” on page 687).
Compute node start problems
Use this information to resolve compute node start problems.
Embedded hypervisor is not in the boot list
Complete the following steps until the problem is solved:
1. If the compute node has recently been installed, moved, or serviced, or if this is the first time the
embedded hypervisor is being used, make sure that the device is connected correctly and that there is
no physical damage to the connectors.
2. Check http://www.lenovo.com/ serverproven/ to validate that the compute node supports the
embedded hypervisor device.
3. Use the Setup utility to make sure that the embedded hypervisor device (USB key) is in the startup
sequence. From the Setup utility, select Start Options .
4. Check http://www.ibm.com for any service bulletins related to the embedded hypervisor and the
compute node.
5. Make sure that other software works on the compute node to ensure that the compute node is working
properly.
Connectivity problems
Use this information to solve connectivity problems.
Cannot communicate with the Flex System Manager management node
Use the information in this section to troubleshoot the compute node when you cannot communicate with
the Flex System Manager management node on the data network.
Complete the following steps until the problem is solved:
1. Make sure that all ports for the connection path are enabled and that you can ping the Flex System
Manager management node. If you are unable to ping the Flex System Manager management node, see
“Cannot ping the Flex System Manager management node on the data network” on page 622.
2. Make sure that the protocols you are using are enabled.
Note: By default, only secure protocols are enabled, for example, SSH and HTTPS.
3. If you cannot log into the Flex System Manager management node, see “Cannot log in to the Flex
System Manager management node” on page 618.
Cannot communicate with the CMM
Use the information in this section to troubleshoot the compute node when you cannot communicate with
the CMM on the data network.
Note: Communications errors from compute nodes can take up to 20 minutes to appear in the CMM
event log.
Complete the following steps until the problem is solved:
1. Make sure that all ports in the connection path are enabled and that you can ping the CMM. If you are
unable to ping the CMM, see “Cannot ping the CMM on the management network” on page 619.
2. Make sure that the protocols that you are using are enabled.
Note: By default, only secure protocols are enabled, for example, SSH and HTTPS.
Chapter 6
.
Troubleshooting
615