Adding Nodes to a Cluster

This operation enables you to expand the capacity of a cluster when its capacity is insufficient.

Procedure

On the menu bar, click and select Add Node.

Select the nodes to be added to the cluster.

Batch Import Node
1. Click Batch Import Node.
2. In the Please choose files area, click , select the file to be uploaded, and click Open.
  
  You can click Download the template, enter parameters of the nodes to be added in the downloaded template, and upload the template.
3. Click Upload.
4. Authenticate all nodes. Click Authenticate and enter the user name and password of a node for authentication.
5. Click Submit.
6. After the nodes are configured successfully, click Next.

Manually Add Node

Click Manually Add Node.
The Add Node page is displayed on the right.

Configure basic node and authentication information. Table 1 describes related parameters.

**Table 1** Basic node and authentication information
Parameter	Description
Management IP Address	Indicates the management IP address of a node.
Cabinet	Indicates the cabinet where a node resides.
Chassis	Indicates the chassis where a node resides.
Slot	Indicates the slot number where a node resides.
Node Name	Indicates the name of a node.
Node Role	Indicates the role of a node. Possible options are Storage and Compute. Storage: The node provides storage resources. Compute: The node provides the service provisioning function.
Firewall	Determines whether to enable the firewall. NOTE: This parameter needs to be set only when the node to be added is a compute node and Regular installation is selected.
Installation Mode	Indicates the installation mode of the node. Possible options are Regular installation and Pre-installation. Parameters Username, Password, and Password of root are not required when Node Role is Compute and Installation Mode is Pre-installation.
iBMC Password	After this function is enabled, you need to configure a user name and password for authenticating the iBMC server. NOTE: This parameter needs to be set only for nodes that contain storage roles.
Username	If you use a pre-installed operating system, enter fsadmin for authentication. If you use a third-party operating system: User root is preferentially used for authentication. If you use a non-root user for authentication, the user must have the SUDO, remote SFTP, and SSH permissions. For the SUDO permission, when running the sudo su - root command, you must use the password of user root instead of the password of this user.
Password	Indicates the user password.
Password of root	Indicates the password of user root.

Click OK.
Click Submit.
After the node is configured successfully, click Next.

If Network Management Component Installation is Waiting for completion, the progress of installing network management components on the node is 100%. However, you need to wait until the installation is complete on all nodes and a notification is sent to related components. After the notification is sent to the related components, the installation process ends and the status changes to Successful.

Configure storage networks.

If a front- and back-end shared network is deployed during initialization, you can only deploy the shared network. If front- and back-end separated networks are deployed during initialization, you can only deploy separated networks.

The Configure Storage Network page varies depending on the selected transmission protocol. Configure the storage network as prompted. Table 2 describes related parameters.

The values of Transmission Protocol, Network Flow Classification, Multi-IP Address, and Bond Mode must be the same as those of the front-end storage network configured during cluster initialization and cannot be changed.

**Table 2** Storage network parameters
Parameter	Description
Use Configured Storage IP Address Only	Yes: Only storage IP addresses configured in advance are used. To select this option, all storage nodes must be configured with storage IP addresses in advance. No: If no storage network IP address is configured in advance, the system will assign new storage network IP addresses to the nodes based on the settings.
Shared IP Address on DPC Compute Node	This parameter is mandatory when Transmission Protocol is set to RoCE and Multiple IP Addresses is set to Yes. When a DPC compute node has only one front-end storage IP address and you select Yes, the control IP address must be the same as the front-end storage IP address. NOTE: This parameter can be configured only when a DPC compute node is added for the first time. If a DPC compute node is added later, the value of this parameter will be the same as that configured for the first time and cannot be changed.

Click Add Storage IP Address Range and set the IP address range, subnet mask/prefix, and port number of the storage network.
- The start and end IP addresses of each storage IP address range must be in the same subnet.
- The storage network configured for a node cannot be in the same subnet as other networks.
- If the storage IP addresses are IPv4 addresses, enter the corresponding subnet mask. If the storage IP addresses are IPv6 addresses, enter the corresponding prefix.
- If Use Configured IP Addresses Only is set to No, you need to configure the port of the storage network. Click to go to the Manage Bond Port page. You can configure a port as required.
- You can click Add Storage IP Address Range to configure multiple storage IP address ranges. In addition, cross-network segment configuration is supported. If storage IP addresses are on different network segments, you need to configure static routes or policy-based routes. If multiple IP addresses are used as storage IP addresses, you need to configure policy-based routes. Click Configure Route to go to the route configuration page. For details, see Managing Route Configuration.
- To remove an IP address range, select it and click Remove. You can also click More to modify or remove an added IP address range.
If Transmission Protocol of the back-end shared network or front-end storage network is set to RoCE and Multiple IP Addresses is set to Yes, you need to configure control IP addresses. Click Add Control IP Address Range and set the IP address range and subnet mask/prefix of the control network.
- An IP address range of the control network cannot be in the same network segment as that of the storage network.
- When the control IP addresses are IPv4 addresses, enter the corresponding subnet mask. When the control IP addresses are IPv6 addresses, enter the corresponding prefix.
- You can click Add Control IP Address Range to configure multiple control IP address ranges. In addition, cross-network segment configuration is supported.
- To remove an IP address range, select it and click Remove. You can also click More to modify or remove an added IP address range.
Click Preview. The system automatically reads the IP addresses configured on the nodes.
- If the storage or control IP addresses have been configured, the system displays the storage or control IP address of each node.
- If the storage or control IP addresses are not configured, the system displays the storage or control IP addresses to be allocated to storage nodes.
To improve reliability and performance, you are advised not to use physical ports and bond ports on the storage network at the same time. If there are both physical ports and bond ports on the storage network, in multi-IP address scenarios, all ports must be changed to physical ports in a unified manner, while in non-multi-IP address scenarios, you are advised to use bond ports in a unified manner.
Click Submit.
After the storage network is configured successfully, click Next.

Install nodes.
1. (Optional) If the installation fails, you can click Restore Factory Setting to reconfigure the nodes.
2. Click Install.
3. (Optional) After the cluster is installed successfully, you can choose to expand storage pools and replication clusters, and configure iSCSI services as required.
4. Click Finish.