This section describes how to expand the capacity of a cluster when its capacity is insufficient.
and select Add Node.
, 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.
The Add Node page is displayed on the right.
Parameter |
Description |
|---|---|
Management IP Address |
Management IP address of a node. |
Cabinet |
Cabinet where a node resides. |
Chassis |
Chassis where a node resides. |
Slot |
Serial number of a slot where a node resides. |
Node Name |
Name of a node. [Value range]
|
Node Role |
Role of a node. Possible options are Storage and Compute.
NOTE:
When Service Type is set to Intelligent video and image, DPC compute nodes cannot be added. |
Firewall |
Determine whether to enable the firewall.
NOTE:
This parameter is available only when Installation Mode is set to Regular installation. If firewall has been enabled on the node, enable Configure Firewall when adding the node. |
Installation Mode |
Installation mode of a 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 |
|
Password |
Password of the login user. |
Password of root |
Password of user root. |
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.
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 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.
Parameter |
Description |
|---|---|
Use Configured Storage IP Address Only |
|
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. |
to go to the Manage Bond Port page. You can configure a port as required.
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.
After a storage node is added to the cluster, the security sandbox function will be automatically enabled for the storage node. To check whether the security sandbox function is automatically enabled, after adding nodes, choose Cluster > Cluster > Hardware and click the Nodes tab to view the security sandbox status. If the security sandbox is disabled, enable it.