IBM Flex System x440 Compute Node, Installation And Service Manual, Page: 481 / 584

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 I/O module is powered on and is not hung, by pinging the
I/O module from the management node. If the I/O module is powered on and
hung, reset the I/O module. Make sure that the correct ports are enabled for
the node on the I/O module.
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 “Multiple nodes
cannot ping the management node in the same chassis.”
4. Make sure that the IP configuration settings on the node are correct and that
the port is enabled.
5. Check http://www.ibm.com/supportportal/ 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.
6. Check http://www.ibm.com/supportportal/ for any service bulletins that are
related to network connectivity.
7. Remove the compute node and make sure that the connectors on the midplane
and the node are not damaged.
8. (Trained service technician only) Complete the following steps:
a. Force the link/duplex speed.
b.
Check the connectors on the node and the midplane to make sure that no
pins are bent.
c. Replace the system board 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 IBM Flex System Manager management node in the same chassis on the data
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 I/O module is powered on and is not hung, by pinging the
I/O module from the management node. If the I/O module is powered on and
hung, reset the I/O module. Make sure that the correct ports are enabled for
the node on the I/O module.
3. Make sure that the management network port (eth1) is enabled in the
management node. Make sure that the port configuration settings are correct
for the data network.
4. Make sure that the configuration settings for each node are correct and that the
data network ports are enabled.
5. Make sure that the configuration settings in the I/O module are correct and
that the applicable ports are enabled for your compute nodes and the
management node on the I/O module. If the problem remains, complete the
following steps:
Chapter 6. Troubleshooting
469