Lenovo Flex SystemChassis Management Module 2: configuring the CMM for CLI

You must configure the CMM to use the command-line interface.

You configure only the primary (active) CMM. If a standby (redundant) CMM is installed, it receives the configuration and status information automatically from the primary CMM when necessary. The configuration information in this topic applies to the primary CMM, which might be the only CMM in the Lenovo Flex System chassis.

If the CMM that you are installing is the only CMM in the Lenovo Flex System chassis and you have a saved CMM configuration file, you can apply the saved configuration file to the replacement CMM. See read command for information about applying a saved configuration file.

For the primary CMM to communicate, you must configure the IP address for the remote management and console (Ethernet) port (eth0) of the CMM by using the CMM CLI ifconfig -eth0 command (see ifconfig command for information about command use). The initial automatic CMM configuration enables a remote console to connect to the CMM to configure the port completely and to configure the rest of the Lenovo Flex System chassis.

After you connect the primary CMM to the network, the Ethernet management port connection is configured in one of the following ways. Either of these actions enables the Ethernet management port on the primary CMM.

If you have an accessible, active, and configured dynamic host configuration protocol (DHCP) server on the network, the IP address, gateway address, subnet mask, and DNS server IP address are set automatically. The host name is set to the CMM MAC address by default, and the domain server cannot change it.
If the DHCP server does not respond within 2 minutes after the port is connected, the CMM uses the manufacturing-defined static IP address and default subnet address.
Note: If the CMM DHCP setting is set to try the DHCP server and then use the static IP address, the CMM uses the static IP address when the DHCP server is not available during CMM startup. When this occurs, the IP address might not be reachable if multiple CMMs were started with the same static IP address. Use the dhcpinfo command to view the DHCP settings for the CMM (see dhcpinfo command for information).

Important: You cannot connect to the CMM by using the manufacturing-defined static IP address and manufacturing default subnet address until at least 3 minutes after CMM startup.

Note: If the IP configuration is assigned by the DHCP server, you can use the MAC address of the CMM network interface to find out what IP address is assigned.

To configure the CMM Ethernet ports, complete the following steps:

Connect your system to the CMM command-line interface (see Starting the command-line interface for more information).
Configure the remote management and console (Ethernet) port (eth0), using the CMM CLI ifconfig command (see ifconfig command for information about command use).
Note:
- The internal Ethernet management port on each I/O module provides for communication with the CMM. You configure this port by configuring the IP address for the I/O module by using the web interface or the CMM CLI ifconfig command (see ifconfig command for information about command use). See the documentation that comes with each I/O module for information and instructions. Some types of I/O modules, such as the pass-thru module, have no management port. See the documentation that comes with each I/O module to determine what else you must configure for the I/O module.
- For I/O-module communication with a remote management station, such as the optional Lenovo XClarity Administrator or Flex System Manager management node, through the CMM external Ethernet (remote management and console) port, the I/O-module internal network interface and the CMM internal and external interfaces must be on the same subnet.
- To communicate with the compute nodes for functions such as deploying an operating system or application program, you also must configure at least one external (in-band) port on an Ethernet I/O module.

Configuring the CMM for CLI operation