Skip to main content

Configuring the XClarity Management Hub 2.0 network

Review these network considerations to help you set up the network in your datacenter to use XClarity Management Hub 2.0.

To configure network settings, click Network on the context menu from the Administration view.

Network interface (eth0)​

XClarity Management Hub 2.0 uses a single network interface (eth0) for management and data communication. Review the following considerations before configuring the network.
  • The network interface is used for discovery and management. XClarity Management Hub 2.0 must be able to communicate with all devices that you intend to manage.
  • The network interface must be connected to the Internet, preferably through a firewall.

IPv4 address settings​

XClarity Management Hub 2.0 uses IPv4 network settings. You can configure the IP assignment method, IPv4 address, network mask, and default gateway.

For the IP assignment method, you can choose to use a statically-assigned IP address or obtain an IP address from a Dynamic Host Configuration Protocol (DHCP) server. When using a static IP address, you must provide an IP address, network mask, and default gateway. The default gateway must be a valid IP address and must be on the same subnet as the network interface.

If DHCP is used to obtain an IP address, the default gateway also uses DHCP.

Attention
  • Network address translation (NAT), which remaps one IP address space into another, is not supported.
  • Changing the IP address of the XClarity Management Hub 2.0 virtual-appliance after the management hub is up and running will cause connectivity issues with the XClarity Orchestrator portal and all managed devices. If you need to change the IP address, disconnect management hub from the portal, and unmanage all managed devices before changing the IP address. After the IP address change is complete, reconnect management hub to the portal and re-manage the devices.
  • If the network interface is configured to use the DHCP, ensure that IP address changes are minimized by basing the DHCP address on a MAC address or configuring DHCP so that the lease does not expire to avoid communication issues. If the IP address changes when the DHCP lease expires, you must disconnect (delete) the management hub from the portal, and then connect it again.

DNS settings​

XClarity Management Hub 2.0 uses IPv4 network settings. You can configure the IP assignment method, up to two static DNS IPv4 addresses, and custom host name and domain.

For the IP assignment method, you can choose to use a statically-assigned IP address or obtain an IP address from a DHCP server. When using a static IP address, you must provide an IP address for at least one and up to two DNS servers.

Specify the DNS host name and domain name. You can choose to retrieve the domain name from a DHCP server or specify a custom domain name.

Note
If you choose to use a DHCP server to assign IPv4 address, ensure that the DHCP server is configured such that the DHCP address lease is permanent to avoid communication issues. If the IP address changes when the DHCP lease expires, the host name and domain that you provided are overwritten when the DHCP lease is renewed.

Open ports​

Lenovo XClarity Management Hub 2.0 requires certain ports to be open to facilitate communication. If the required ports are blocked or used by another process, some management hub functions might not perform correctly.

If devices are behind a firewall and if you intend to manage those devices from a management hub that is outside of that firewall, you must ensure that all ports involved with communications between the management hub and the baseboard management controller in each device are open.

Service or componentOutbound (ports open to external systems)Inbound (ports open on target devices)
XClarity Management Hub 2.0
  • DNS - UDP on port 53
  • NTP - UDP on port 123
  • HTTPS - TCP on port 443
  • SSDP - UDP on port 1900
  • DHCP - UDP on port 67
  • HTTPS - TCP on port 443
  • SSDP - UDP on ports 32768-65535
ThinkSystem and ThinkAgile servers
  • HTTPS – TCP on port 443
  • SSDP discovery – UDP on port 1900
  • HTTPS – TCP on port 443