Perform this task to discovery the hosts installed with Space Console and add them to the system.
Space Console scans hosts based on Layer 2 protocols and can discover all hosts that are in the same VLAN as the management network physical interfaces of Space Console. During the joining process of a host, Space Console will deploy initial settings such as physical NIC IP, subnet mast, LAGG settings, and load balancing modes, to the host. If the host fails to join Space Console, the system will set the management IP and subnet mask of the host to 192.168.0.162 and 255.255.255.0, respectively.
Figure-1 Host discovery process
Perform host discovery to expand clusters.
If you add new hosts to the cluster, you must re-upload an optimization tool package compatible with the management platform. The optimization tool package will overwrite the existing one and be issued to the added hosts. For more information about the optimization tool package, see "Tool images."
You can discover hosts in a host pool or cluster. When you discover hosts in a host pool, you can assign the hosts to clusters in the host pool. When you discover hosts in a cluster, you can assign the hosts only to that cluster.
Make sure the Space Console software version of the hosts is the same as the Space Console system.
Make sure the number of NIC physical interfaces and reuse settings of the management, service, storage front-end, and storage back-end networks on the hosts are the same as those configured on the Space Console Setup Wizard.
For example, if the network settings of Space Console are as follows:
Management and service—Physical interfaces eth0 and eth1, static link aggregation mode. The management network uses VLAN 10.
Storage front-end and storage back-end—Physical interfaces eth2 and eth3 in VLAN 12, dynamic link aggregation mode. The storage back-end and front-end networks use VLAN 12 and VLAN 13, respectively.
The host and the connected switch settings must be the following:
Management and service networks—Trunk type, permitting VLAN 10 and the service VLAN, sharing two physical interfaces.
Storage front-end and back-end networks—Trunk type, permitting VLANs 12 and 13, sharing two physical interfaces.
From the navigation pane, select Data Center > Virtualization > Host pool name.
Click the Hosts tab, and then click Host Discovery.
Click Configure NICs for a host, configure the network parameters as planned, and then click OK.
Click Add to Cluster for a host, select a cluster, and then click OK.
From the navigation pane, select Data Center > Virtualization > Host pool name > Cluster name.
Click Host Discovery.
Click Configure NICs for a host, configure the network parameters as planned, and then click OK.
Click Add to Cluster for a host, and then click OK.
NIC Template: After you enable this feature for a host, the system automatically configures network settings based on those of the host for other hosts that meet the following requirements:
Have physical NICs with the same names as those of the host, and the physical NICs are active.
The physical NICs meet the minimum rate requirements of corresponding networks.
Assume that you enable this feature for Host A, which uses eth0 as the management network NIC, eth1 as the service network NIC, and eth2 and eth3 as the storage network NICs. The system automatically configures network settings for a host only when the host meets the following requirements:
Has physical NICs eth0, eth1, eth2, and eth3, and the physical NICs are active.
The rate of eth0 and eth1 is not lower than 1000 Mbps.
The rate of eth2 and eth3 is not lower than 10000 Mbps.
IP: If you do not configure IP addresses for the hosts, the system automatically assigns IP addresses to the hosts in sequence. You do not need to configure a service network IP address for a host.
Physical NIC: Specify physical NICs for the management, storage back-end, and storage front-end networks. The service network NIC is optional. If you do not specify a service network NIC, the system does not create a service network virtual switch for the host after the host joins the cluster. In this case, you must manually configure a service network virtual switch for the host.
LAGG Mode: Select a link aggregation mode for the physical NICs. Options include Static and Dynamic. As a best practice, use dynamic link aggregation mode. If you select the dynamic link aggregation mode, you must enable LACP on the physical switch. This parameter is available only when you select multiple physical interfaces.
LB Mode: Select the load balancing mode for physical NICs. This parameter is available only when you select multiple physical interfaces.
Advanced—Balances load based on Ethernet type, IP protocol, source IP address, destination IP address, source port, and destination port of the packets. As a best practice, use advanced load balancing mode in an environment that requires precise load balancing.
Basic—Balances load based on the source MAC address and VLAN tag of the packets. As a best practice, use this mode to increase the network bandwidth and reduce the single-NIC load.