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

FusionStorage OBS 7.0 Planning Guide 06

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

This section describes the IP addresses that need to be planned in the network plane during the installation and deployment of FusionStorage OBS.

NOTE:

For the OBS service, the service plane, management plane, and BMC plane support IPv4 and IPv6 addresses, but only one of the IP address types can be configured. The storage plane and control plane support only IPv4 addresses.

For the HDFS service, all planes support only IPv4 addresses.

  • Table 2-30 shows the number of IP addresses to be planned and planning rules for FusionStorage OBS 7.0.0.
    Table 2-30 IP address planning

    Network Segment Type

    Number of IP Addresses

    Description

    Management plane

    1 (Number of management plane floating IP addresses) + 1 (Number of deployment tool management floating IP addresses) + Number of storage nodes x 1 + 1 (Number of management switch management plane IP addresses) + 1 (Number of BMC switch management plane IP addresses) +1 (Number of management plane IP addresses for switches shared by the front and back ends)

    • Management plane floating IP address is used to access DeviceManager.
    • Deployment tool management floating IP address is used to access DeployManager.
    • One management plane IP address is allocated to each storage node.
    • One management plane IP address is allocated to the management switch.
    • One management plane IP address is allocated to the BMC switches, and one to the switches shared by the front and back ends.
    NOTE:
    • If a single cabinet is used, the management plane floating IP address is floating on storage nodes 01 and 02 in the base cabinet.
    • If multiple cabinets are used, the management plane floating IP address is floating on storage node 01 in the base cabinet and storage node 01 in the first expansion cabinet.
    • Two switches shared by the front and back ends are stacked as one switch. Only one IP address needs to be allocated to float among ETH management network ports on the two switches shared by the front and back ends.

    BMC plane

    Number of storage nodes x 1

    One BMC plane IP address is allocated to each storage node.

    Service plane

    Number of storage nodes x 1

    One service plane IP address is allocated to each storage node.

    Storage plane

    Number of storage nodes x 1 + 1 (Number of storage plane floating IP addresses) + 1 (Number of GaussDB floating IP addresses) + 1 (Number of back-end floating IP addresses of the deployment tool) + 3 (Floating IP addresses of OAM-I, OAM-P, and OAM-S)

    • One storage plane IP address is allocated to each storage node.
    • One storage plane floating IP address is allocated for internal communication of components.
    • One GaussDB floating IP address is allocated to access GaussDB services.
    • One back-end floating IP address of the deployment tool is allocated for internal communication of the tool.
    • One floating IP address is allocated to OAM-I, OAM-P, and OAM-S each to access services at different layers.

    Control plane

    Number of storage nodes x 1

    One control plane IP address is allocated to each storage node.

  • Table 2-31 shows the number of IP addresses to be planned and planning rules for FusionStorage OBS 7.0.1.
    Table 2-31 IP address planning

    Network Segment Type

    Number of IP Addresses

    Description

    Management plane

    1 (Number of DeviceManager floating IP addresses) + 1 (Number of DeployManager management floating IP addresses) + Number of storage nodes x 1 + 1 (Number of management switch management plane IP addresses) + 1 (Number of BMC switch management plane IP addresses) +1 (Number of management plane IP addresses for switches shared by the front and back ends)

    • DeviceManager Floating IP Address is used to access DeviceManager.
    • DeployManager Floating IP Address is used to access DeployManager.
    • One management plane IP address is allocated to each storage node.
    • One management plane IP address is allocated to the management switch.
    • One management plane IP address is allocated to the BMC switch.
    • One management plane IP address is allocated to the switches shared by the front and back ends.
    NOTE:
    • If a single cabinet is used, the management plane floating IP address is floating on storage nodes 01 and 02 in the base cabinet.
    • If multiple cabinets are used, the management plane floating IP address is floating on storage node 01 in the base cabinet and storage node 01 in the first expansion cabinet.
    • Two switches shared by the front and back ends are stacked as one switch. Only one IP address needs to be allocated to float among ETH management network ports on the two switches shared by the front and back ends.

    BMC plane

    Number of storage nodes x 1

    One BMC plane IP address is allocated to each storage node.

    Service plane

    • Number of IP addresses for the OBS service = Number of storage nodes x 1
    • Rules for calculating the number of IP addresses for the HDFS service are as follows:
      • If Number of namespaces x 5 ≥ Number of storage nodes, then Number of IP addresses = Number of namespaces x 5
      • If Number of namespaces x 5 < Number of storage nodes, then Number of IP addresses = Number of storage nodes
    • For the OBS service, one service plane IP address is allocated to each storage node.
    • For the HDFS service, service plane IP addresses need to be configured for the storage nodes and namespaces.

    Storage plane

    Number of storage nodes x 1 + 1 (Number of DeployManager back-end floating IP addresses) + 1 (Number of HA floating IP addresses) + 1 (Number of GaussDB floating IP addresses) + 3 (Floating IP addresses of OAM-I, OAM-P, and OAM-S)

    • One storage plane IP address is allocated to each storage node.
    • One DeployManager back-end floating IP address is allocated for internal communication of the tool.
    • One HA floating IP address is allocated.
    • One GaussDB floating IP address is allocated to access GaussDB services.
    • One floating IP address is allocated to OAM-I, OAM-P, and OAM-S each to access services at different layers.

    Control plane

    Number of storage nodes x 1

    One control plane IP address is allocated to each storage node.

Translation
Download
Updated: 2019-07-17

Document ID: EDOC1100051332

Views: 3222

Downloads: 23

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