Skip to main content

Multiple nodes cannot ping the management node in a different chassis

Use the information in this section to troubleshoot multiple nodes that cannot ping the 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.
  2. Make sure that the Chassis Management Module is powered on and is not hung by pinging the Chassis Management Module from the management node:
    1. If the Chassis Management Module is powered on and hung, reset the Chassis Management Module.
    2. Make sure that the IMM, the management node, and the Chassis Management Module are all on the same subnet.
  3. Make sure that all cables between the CMMs and the top-of-rack switch are correctly connected and secure and that the activity LEDs are lit on the applicable ports
  4. Make sure that the Chassis Management Modules (the Chassis Management Module in the same chassis as the management node and the Chassis Management Module in the remote chassis) have the same subnet address and can ping one another. If they cannot, make sure that the ports on the top-of-rack switch are enabled. Attempt to connect the Chassis Management Modules directly if possible.
  5. Make sure that the management node has fully discovered the nodes within its chassis by viewing the chassis map. If it has not fully discovered the nodes, follow the steps in Multiple nodes cannot ping the management node in the same chassis.
  6. Make sure that the management processor for each compute node has a valid IP address by checking the chassis map of the remote chassis.
    Note
    If the Chassis Management Module recently lost connection to the DCHP server, you must reset the IMM by using the Chassis Management Module interface so that a new IP address can be acquired.
    If a system-management processor does not have a valid IP address, complete the following steps:
    1. Restart the Chassis Management Module in the remote chassis.
    2. Check the Lenovo Support Portal for any firmware or software 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.
    3. Remove and reinstall Chassis Management Module.
    4. Replace the Chassis Management Module.
  7. Check the Lenovo Support Portal for any service bulletins that are related to network connectivity.
  8. Remove the 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:
    1. Force the link/duplex speed.
    2. Check the connectors on the nodes and the chassis midplane to make sure that no pins are bent.
    3. Replace the I/O expansion card in the management node.