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

FusionCube DB 3.1 Database Best Practice 03 (Oracle RAC 11g R2)

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).
Oracle RAC Node Network Plan

Oracle RAC Node Network Plan

During the Oracle RAC deployment, set IP addresses including public, private, virtual, and SCAN IP addresses.

  • Use the existing management IP address (ebond0) or new service IP address (for example, ebond1) as the public IP address. If you want to use the new service IP address, add service IP addresses for all database nodes. For details, see (Optional) Configuring the Service Network.
  • The private IP addresses are used for the heartbeat network plane of the Oracle RAC cluster. The IB network of FusionCube is used. You can use the existing storage plane IP address (Ibond0) or the heartbeat network plane IP address (for example, Ibond1) of the independent IB network adapter.
  • Configure the unused IP addresses in the same network plane as the public IP addresses as the VIP and SCAN IP addresses.
  • One SCAN IP is configured by default. You need to plan and configure three SCAN IP addresses only when the customer requires three DNS servers.
  • The IP addresses listed in the following table are only examples. Plan the IP addresses based on service requirements.
  • If the IB driver version of the database nodes is 3.0 or later when RAC is installed, use the Internet Protocol over InfiniBand (IPoIB) protocol because the private network between Oracle RAC nodes does not support the Relational Database Service (RDS) protocol.
Table 1-6 Node network plan

IP Address Type

Node Name

Port Name

IP Address

Remarks

Public IP address

dbn01

ebond0

10.32.213.4

Provided by the customer (you can use the existing management plane port ebond0 or a new service plane port ebond1 or ebond2. This document uses ebond0 as an example.)

dbn02

ebond0

10.32.213.5

Private IP address

dbn01

Ibond0

172.21.50.4

FusionCube internal IB network plane IP addresses (you can use the existing storage plane IP addresses. This document uses the storage plane port Ibond0 as an example.)

dbn02

Ibond0

172.21.50.5

Virtual IP address

dbn01

ebond0:1

10.32.213.6

Provided by the customer (unused IP addresses that are in the same network plane as the public IP addresses)

dbn02

ebond0:1

10.32.213.7

SCAN IP address

scan-IP

ebond0:2

10.32.213.8

Provided by the customer (unused IP addresses that are in the same network plane as the public IP addresses)

scan-IP

ebond0:2

10.32.213.9

Provided by the customer (required only when the DNS server is configured)

scan-IP

ebond0:2

10.32.213.10

Provided by the customer (required only when the DNS server is configured)

Translation
Download
Updated: 2018-12-26

Document ID: EDOC1100035759

Views: 20698

Downloads: 30

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