Use the information in this section to troubleshoot multiple
nodes that cannot ping the IBM Flex System Manager management node
in a different chassis on the management network.
- 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).
- 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:
- If the Chassis Management Module (CMM) is powered on and hung,
reset the Chassis Management Module (CMM).
- Make sure that the IMM, the management node, and the Chassis Management
Module (CMM) are all on the same subnet.
- 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.
- Make sure that the Chassis Management Module (CMM)s (the Chassis
Management Module (CMM) in the same chassis as the management node
and the Chassis Management Module (CMM) 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 Module (CMM)s directly if possible.
- 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.
- 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 (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.
- If a system-management processor does not have a valid IP address,
complete the following steps:
- Restart the Chassis Management Module (CMM) in the remote chassis.
- Check the IBM 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.
- Remove and reinstall Chassis Management Module (CMM).
- Replace the Chassis Management Module (CMM).
- Check the IBM Support Portal for any service bulletins that are
related to network connectivity.
- Remove the node and make sure that the connectors on the midplane
and the node are not damaged.
- (Trained service technician only) Complete the following steps:
- Force the link/duplex speed.
- Check the connectors on the nodes and the midplane to make sure
that no pins are bent.
- Replace the I/O expansion card in the management node.