Lenovo Flex System x440 Compute Node Installation And Service Manual page 873

2. Make sure that the CMM is powered on and is not hung, by pinging the CMM from the management
node:
a. If the CMM is powered on and hung, reset the CMM
b. Make sure that the IMM, the management node, and CMM are all on the same subnet.
3. Make sure that the compute node is the only one in the chassis that the management node cannot ping.
If it is not, follow the steps in
on page 863. Make sure that the compute node appears on the chassis map (it might not be fully
discovered by the management node software).
4. Make sure that the IMM has acquired an IP address from the CMM by using the Setup utility on the
compute node.
Note: If the CMM recently lost connection to the DCHP server, you must reset the IMM by using the
CMM interface so that a new IP address can be acquired.
5. Make sure that the system-management processor in each compute node has a valid IP address by
checking the chassis map of the remote chassis.
Note: If the CMM recently lost connection to the DCHP server, you must reset the IMM by using the
CMM interface so that a new IP address can be acquired.
6. Check
http://www.lenovo.com/support
view the release notes for a firmware update to determine the issues that are addressed by the update.
7. Check
http://www.lenovo.com/support
8. Remove the compute node and make sure that the connectors on the chassis midplane and the node
are not damaged.
9. (Trained service technician only) Complete the following steps:
a. Check the connectors on the node and the chassis midplane to make sure that no pins are bent.
b. Replace the base assembly in the compute node.
Multiple nodes cannot ping the management node in the same chassis
Use the information in this section to troubleshoot multiple nodes that cannot ping the Flex System Manager
management node in the same chassis on the management network.
Action
Complete the following steps until the problem is solved:
1. Make sure that the management node is powered on and is not hung, by logging in to the management
node. If you are unable to log in from the management network, attempt to log in from the data network.
If the management node is powered on and hung, perform a virtual reseat of the management node from
the CMM.
2. Make sure that the CMM is powered on and is not hung, by pinging the CMM from the management
node:
a. If the CMM is powered on and hung, reset the CMM.
b. Make sure that the IMM, the management node, and CMM are all on the same subnet.
3. Make sure that the management network port (eth0) in the management node is enabled.
4. Make sure that the management node has an IP address, is on the same subnet as the CMM, and is able
to ping the CMM.
5. Make sure that the system-management processor in each compute node has a valid IP address by
checking the chassis map of the remote chassis.
Note: If the CMM recently lost connection to the DCHP server, you must reset the IMM by using the
CMM interface so that a new IP address can be acquired.
"Multiple nodes cannot ping the management node in the same chassis"
for any firmware updates that might apply to this issue. You can
for any service bulletins that are related to network connectivity.
.
Chapter 6 Troubleshooting
863