No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor 9000 V100R001C01 Planning Guide 07

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
IP Address Planning

IP Address Planning

When a 10GE network is used and P25/P36/P12/C36 nodes are deployed, plan IP addresses by following instructions in Table 2-3.

To avoid readjusting network segments in the future capacity expansion, reserve IP addresses for expansion nodes and switches.

You are advised to reserve more than two IP addresses for the management network segment for commissioning.

Table 2-3  IP address planning

Network Segment Type

Number of IP Addresses

Description

Front-end service network

DFS service deployed on nodes:
  • If a static or dynamic domain name is used to mount the client, the number of IP addresses equals to: number of nodes x 2 + 1
  • If static and dynamic domain names are used to mount the client, the number of IP addresses equals to: number of nodes x 2 + number of nodes x 2 + 1
  • If a static domain name is used to mount the client, assign two static front-end IP addresses to each node.
  • If a dynamic domain name is used to mount the client, assign n (n = number of nodes x 2) dynamic front-end IP addresses for the IP address pool of InfoEqualizer.
  • Plan one InfoEqualizer DNS IP address.
NOTE:

Front-end service network IP addresses can be configured and changed after deployment in DeviceManager.

If the number of clients is far more than the number of nodes (for example, more than 3 times), and the front-end service network IP addresses are sufficient, in order to ensure that the client can access the front-end service network in a more balanced manner, assign n (n = Number of clients) dynamic front-end IP addresses for the IP address pool of InfoEqualizer.

Object storage service deployed on nodes: number of nodes x 2

  • Assign two static front-end IP addresses for each node.
NOTE:

If the front-end service network IP addresses are not assigned during service deployment, you can add or change them in DeviceManager.

There is no need to assign dynamic front-end IP addresses when deploying the object storage service.

DFS service and object storage service deployed on nodes:
  • DFS service deployed on nodes:
    • If a static or dynamic domain name is used to mount the client, the number of IP addresses equals to: number of nodes x 2 + 1
    • If static and dynamic domain names are used to mount the client, the number of IP addresses equals to: number of nodes x 2 + number of nodes x 2 + 1
  • Object storage service deployed on nodes: number of nodes x 2

Follow the preceding independent deployment rules to assign IP addresses for the nodes for which DFS service and object storage service are deployed.

Back-end storage network

  • Actual number of IP addresses: number of nodes x 2 + 1 (optional)
  • Number of temporary IP addresses for software installation: number of nodes
  • Each storage node is assigned two back-end storage network IP addresses. By default, the planning tool assigns IP addresses that reside on the network segment 172.16.0.10 to 172.16.255.254 to the back-end storage network. The default subnet mask is 255.255.0.0 (the mask length is at least 16). An IP address can be used as long as it does not conflict with the IP address of an application.
  • Optional: If the object storage services are deployed, you also need to plan a gauss floating management IP address, which is used for object storage service (compatible with Amazon S3 APIs) and object storage service (compatible with OpenStack Swift APIs) to provide the internal database service.
  • The following temporary IP addresses must be obtained during OceanStor 9000 software installation:

    n (n = number of nodes) back-end storage network IP addresses. When the DHCP is used to assign IP addresses during the software installation, each storage node is assigned another IP address. Those IP addresses are temporarily assigned to each node during the software installation and will be automatically deleted after the software is installed. Those temporary IP addresses cannot be the same as the planned back-end network IP addresses.

NOTE:

Back-end storage network IP addresses cannot be changed after deployment in DeviceManager. Therefore, fill in the deployment template correctly and confirm the information during the deployment.

Management network

  • Actual number of IP addresses: number of nodes + number of management network switches + 1 (number of cluster management IP addresses) + 1 (number of back-end switch IP addresses) + 1 (optional)
  • Number of temporary IP addresses for software installation: 2
  • Each Mgmt on storage nodes is assigned one IP address.
  • Each management switch is assigned one IP address.
  • One OceanStor 9000 management IP address floats among the NIC0 on nodes 01 to 03 in the basic cabinet.
  • One IP address is assigned to the back-end storage network switch.
  • Optional: If the object storage service (compatible with Amazon S3 APIs) is deployed, you also need to plan a POE float management IP address, which is used for object storage service (compatible with Amazon S3 APIs) to provide the external service provisioning interface service of object storage.
  • Two temporary IP addresses must be obtained during OceanStor 9000 software installation, which are used to upload file packages during the software installation. The two temporary IP addresses need to be configured on the NIC0 port of the deployment node and the deployment terminal. You can delete them after finishing the software installation.
NOTE:

Two back-end storage network switches are stacked into one switch. You only need to assign one floating IP address to the management network ports on the two switches.

Management network IP addresses cannot be changed after deployment through the DeviceManager. Therefore, fill in the deployment template correctly and confirm the information during the deployment.

The following information about the user network must be obtained:

  • IPv4 network:
    • Front-end service network gateway and mask
    • Management network gateway and mask
Download
Updated: 2018-10-27

Document ID: EDOC1000042140

Views: 7798

Downloads: 122

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next