Network considerations – XClarity Orchestrator

XClarity Orchestrator uses a single subnet (eth0) for management and data communication. Review the following considerations before configuring the network.

• The network interface is used for discovery and management. It must be able to communicate with all devices that you intend to manage.
• If you intend to manually send collected service data to Lenovo Support or use automatic problem notification (Call Home), the interfaces must be connected to the Internet, preferably through a firewall.
• If you change the XClarity Orchestrator virtual-appliance IP address after connecting resource managers, XClarity Orchestrator will lose communication with the managers, and the managers will appear offline. If you need to change the virtual-appliance IP address after XClarity Orchestrator is up and running, ensure that all resource managers are disconnected (deleted) before changing the IP address.
• Configure the devices and components in ways that minimize IP address changes. Consider using static IP addresses instead of Dynamic Host Configuration Protocol (DHCP). If DHCP is used, ensure that IP address changes are minimized, such as basing the DHCP address on a MAC address or configuring DHCP so that the lease does not expire.

  If the IP address changes, you must disconnect (delete) the managed devices, and then connect them again.

• Network address translation (NAT), which remaps one IP address space into another, is not supported.