Communicating with the optional Flex System Manager management software

The optional Flex System Manager program communicates with the Flex System chassis through the remote management and console Ethernet port on the primary CMM.

To communicate with the Flex System chassis, the optional Flex System Manager management software needs a managed object (in the Group Contents pane of the optional Flex System Manager management console main window) that represents the Flex System chassis. If the CMM IP address is known, the network administrator can create an Flex System Manager managed object for the unit. If the IP address is not known, the optional Flex System Manager software can automatically discover the Flex System chassis (out-of-band, using the remote management and console Ethernet port on the CMM) and create a managed object for the unit.

For the optional Flex System Manager software to discover the Flex System chassis, your network must initially provide connectivity from the optional Flex System Manager management server to the CMM remote management and console (Ethernet) connector. To establish connectivity, the CMM attempts to use DHCP to acquire its initial IP address for the remote management and console Ethernet port. If the DHCP request fails, the CMM uses the static IP address that is assigned to it. Therefore, the DHCP server (if used) must be on the management LAN for your Flex System chassis.

Note

For I/O-module communication with the optional Flex System Manager management server through the CMM remote management and console Ethernet port, the I/O-module internal network interface and the CMM external interfaces must be on the same subnet.

If you do not want to keep the manufacturing default static values, you can configure the static IP address, host name, and subnet mask for the CMM through the web interface or the CMM CLI.

Give documentation feedback