Zones are used to divide a subnet. A zone contains a group of nodes with the same domain name and load balancing policy. Specify service network floating IP addresses for these nodes so that the nodes can process service access of clients.
A subnet has been created.
The Create Zone page is displayed.
Table 1 describes related parameters.
Parameter |
Description |
|---|---|
Name |
Indicates the name of the zone.
NOTE:
|
Home Subnet |
Indicates the subnet to which the zone belongs. |
Sub-domain Name |
Indicates the sub-domain name of the zone. The sub-domain name must be used together with the general DNS service of the subnet. This parameter needs to be set only when the file or HDFS service is enabled.
NOTE:
|
Network Type |
Indicates the network type of ports in the zone. After this parameter is specified, only ports of the specified network type can be added to the port pool. It is recommended that a subnet contain zones of only one network type. |
Associated Namespace |
If the HDFS service is enabled for the storage pool, click Select. On the Associate Namespace page that is displayed, select a namespace and click OK.
NOTE:
|
DNS Policy |
Indicates the DNS policy of the zone. Possible options are as follows:
NOTE:
This parameter can be set only after the general DNS service is enabled for the home subnet. |
DNS Service |
Indicates whether to enable the DNS service to resolve the sub-domain name of the Access zone. After the DNS service is enabled for the subnet, a sub-domain name is set for the zone, and the DNS service is enabled for the zone, you can access services in the zone through a domain name.
NOTE:
This parameter can be set only after the general DNS service is enabled for the home subnet. |
IP Address Failover |
Indicates whether to enable IP address failover. After this parameter is enabled, when a node is faulty, its IP address can be automatically allocated to another normal node. Therefore, clients can continue to access the storage system using this IP address. You are advised to enable this function for Access zones. |
To prevent IP address conflicts among multiple nodes, do not configure static IP addresses for service ports of storage nodes in advance.
The Add IP Address page is displayed.
Table 2 describes related parameters.
Plan IP addresses properly and ensure that the added IP addresses are not used by other services.
Parameter |
Description |
|---|---|
Type |
Indicates the IP address adding type. Possible options are Single Address and Address Segment. |
IP Address |
The value is the planned service IP address when Type is set to Single Address. |
Start IP Address |
The value is the planned start service IP address when Type is set to Address Segment. |
End IP Address |
The value is the planned end service IP address when Type is set to Address Segment.
NOTE:
A maximum of 512 IP addresses can be contained in an IP address segment. |
The Modify IP Address page is displayed.
By default, one port is assigned one service IP address. You can run the following command to change the number of service IP addresses that can be allocated to a port. A maximum of 16 service IP addresses can be allocated to a port.
change cluster_config general port_ip_number
The Add Port page is displayed.
You are advised to select bond ports.
The Manage Service Bond Port page is displayed.
The Create Bond Port page is displayed.
Parameter |
Description |
|---|---|
Bond Port Name |
Indicates the name of the bond port. |
Transmission Protocol |
Indicates the transmission protocol of the bond port. Possible options are TCP and IB. |
Physical Port |
Indicates the physical port to be bound. |
Bond Mode |
Indicates the bond mode. When Transmission Protocol is set to TCP, bond1 and bond4 are supported. When Transmission Protocol is set to IB, only bond1 is supported.
|
MTU (Bytes) |
Indicates the maximum transmission unit of the bond port. |