Adding Nodes to a Cluster

Procedure

1. On the menu bar, click and select Add Node.
2. 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
     1. Click Manually Add Node.

        The Add Node page is displayed on the right.

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

        Table 1 Basic node and authentication information

        Parameter	Description
        Node Type	The value can be New node or Management node. New node: suitable for scenarios where all types of nodes are added as storage or compute nodes. In this mode, you need to enter the management IP address and authentication information of the nodes. Management node: suitable for scenarios where management nodes are added as storage or compute nodes. This mode is recommended for management nodes. In this mode, you can directly select the management IP address of a management node without entering authentication information.
        Management IP Address	Management IP address of the node. NOTE: When the management network is not isolated: The management network IP address cannot use the same subnet as the storage, control, service, or replication network. When the management network is isolated: The management network IP address of the management node (that is, the internal management network IP address) cannot use the same subnet as the storage, control, service, replication, or external management network. The management IP address of the compute or storage node must be able to communicate with the internal management network.
        Cabinet	Cabinet where the node resides. [Value range] The value contains 1 to 256 characters. The value can contain only letters, digits, underscores (_), and hyphens (-). The value cannot start or end with a space.
        Chassis	Chassis where the node resides.
        Slot	Serial number of the slot where the node resides.
        Node Name	Name of the node. [Value range] The name contains 1 to 64 characters. The name can contain only letters, digits, hyphens (-), underscores (_), and periods (.), and must start and end with a letter or digit. A period (.) cannot be adjacent to a period (.), hyphen (-), or underscore (_).
        Node Role	Role of the node. Possible options are Storage and Compute. Storage: The node provides storage resources. Compute: The node provides the service provisioning function. NOTE: When Service Type is set to Intelligent video and image, DPC compute nodes cannot be added.
        Configure 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 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 the current user.
        Password	Password of the login user.
        Password of root	Password of user root.

     3. Click OK.
     4. Click Submit.
     5. 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.

3. Configure the storage network.
   

   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.

   1. 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. For adding DPC compute nodes subsequently, the value of this parameter will be the same as that configured for the first time and cannot be changed.

   2. 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 use the same subnet.
      • In the multi-IP scenario, the storage network can use the same subnet as the control network, but cannot use the same subnet as the internal management, external management, service, and replication networks. The IP address range of the storage network cannot use the same subnet as the IP addresses of other ports on the nodes.
      • In non-multi-IP scenarios, the storage network cannot use the same subnet as the internal management, external management, service, and replication networks. The IP address range of the storage network cannot use the same subnet as the IP addresses of other ports on the nodes.
      • 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 across network segments. A maximum of 300 storage IP address ranges can be configured. 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 Port and Route to go to the route configuration page. For details, see Managing Port and Route Configurations.
      • 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.
   3. 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, subnet mask/prefix, and gateway of the control network.
      

      • The control and the front-end storage networks have same VLAN ID, and can use the same (recommended) or different subnets. When using the same subnet, they must use different IP address ranges.
      • A control network gateway needs to be configured in either of the following scenarios:
        • The control network crosses subnets.
        • The control network does not cross subnets currently but needs to cross subnets due to subsequent capacity expansion.
      • If the control IP addresses are IPv4 addresses, enter the corresponding subnet mask. If 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 across network segments.
      • 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.
   4. 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 scenarios, all ports must be changed to physical ports in a unified manner, while in non-multi-IP scenarios, you are advised to use bond ports in a unified manner.

   5. Click Submit.
   6. After the storage network is configured successfully, click Next.

4. Install nodes.
   1. (Optional) If the installation fails, you can click Restore Factory Settings 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.
   

   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.