Single node cannot ping the management node in a different chassis

Use the information in this section to troubleshoot a single compute node that cannot ping the IBM® Flex System Manager management node in a different chassis on the management network.

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 Chassis Management Module (CMM).
  2. Make sure that the Chassis Management Module (CMM) is powered on and is not hung, by pinging the Chassis Management Module (CMM) from the management node:
    1. If the Chassis Management Module (CMM) is powered on and hung, reset the Chassis Management Module (CMM)
    2. Make sure that the IMM, the management node, and Chassis Management Module (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 Multiple nodes cannot ping the management node in the same chassis. 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 Chassis Management Module (CMM) by using the Setup utility on the compute node.
    Note: If the Chassis Management Module (CMM) recently lost connection to the DCHP server, you must reset the IMM by using the Chassis Management Module (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 Chassis Management Module (CMM) recently lost connection to the DCHP server, you must reset the IMM by using the Chassis Management Module (CMM) interface so that a new IP address can be acquired.
  6. Check the IBM 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.
  7. Check the IBM Support Portal for any service bulletins that are related to network connectivity.
  8. Remove the compute node and make sure that the connectors on the midplane and the node are not damaged.
  9. (Trained service technician only) Check the connectors on the node and the midplane to make sure that no pins are bent.
Parent topic: Cannot ping the IBM Flex System Manager management node on the management network