This section describes how to create a DPC compute node.
The Create DPC page is displayed.
If no DPC node has been created in the system, clicking Create DPC directly enters the Create DPC page.
and select the template, and then click Upload. The nodes are imported to the system in a batch.On the Authentication page, select an installation mode for the nodes. Possible options are Regular installation and Pre-installation. If you select Regular installation, set Username, Password, and Password of root for authentication.
Select Pre-installation when the DPC software has been pre-installed for compute nodes during the file service installation.
Parameter |
Description |
|---|---|
Management IP Address |
Indicates the management IP address of the node. |
Cabinet |
Indicates the cabinet where the node resides. |
Node Name |
Indicates the name of the node. |
Chassis |
Indicates the chassis where the node resides. |
Slot |
Indicates the slot number where the node resides. |
Node Role |
Indicates the role of the node. DPC compute is automatically selected. |
Firewall |
Indicates whether to automatically configure the node firewall. This function is enabled by default. If the firewall is disabled, manually enable it. For details, see the Communication Matrix to ensure that all ports of compute nodes are configured with correct firewall rules. |
Installation Mode |
Indicates the installation mode of the node. Possible options are Regular installation and Pre-installation. If you select Regular installation, set Username, Password, and Password of root for authentication.
NOTE:
Select Pre-installation when the DPC software has been pre-installed for compute nodes during the file service installation. |
Username |
Indicates the user name used for logging in to the DPC node. |
Password |
Indicates the password used for logging in to the DPC node. |
Password of root |
Indicates the password of user root of the DPC node.
NOTE:
If you log in to the DPC node as a non-root user, you need to enter the password of user root. |
Parameter |
Description |
|---|---|
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:
|
Parameter |
Description |
|---|---|
IP Address Range |
Indicates the IP address range of the control network.
NOTE:
Control IP Address Range cannot be the same as Storage IP Address Range. |
Subnet Mask/Prefix |
Indicates the subnet mask or prefix of the control network.
NOTE:
When IP addresses of the storage network are IPv4 addresses, enter the subnet mask. When IP addresses of the storage network are IPv6 addresses, enter the prefix. |
You can click Add Control IP Address Range to configure multiple control IP address ranges.
IP address ranges must contain the IP addresses of all nodes in a cluster.
Parameter |
Description |
|---|---|
IP Address Range |
Indicates the IP address range of the storage network.
NOTE:
IPv4 and IPv6 addresses are supported. |
Subnet Mask/Prefix |
Indicates the subnet mask or prefix of the storage network.
NOTE:
When IP addresses of the storage network are IPv4 addresses, enter the subnet mask. When IP addresses of the storage network are IPv6 addresses, enter the prefix. |
You can click Add Storage IP Address Range to configure multiple storage IP address ranges.
IP address ranges must contain the IP addresses of all nodes in a cluster.
Click Configure Route to go to the route configuration page. For details, see Managing Route Configuration.
For details about how to query static route information, see Managing Route Configuration.
For details about how to delete a static route, see Managing Route Configuration.
The system displays the storage IP address of each node and refresh the table.
Click Configure Route to go to the route configuration page. For details, see Managing Route Configuration.
For details about how to query policy-based route information, see Managing Route Configuration.
For details about how to delete a policy-based route, see Managing Route Configuration.