Oracle Cloud Infrastructure Documentation

Task 2: Create an ODB Network for Oracle Database@AWS

An ODB network is a private network that hosts Oracle Exadata VM Clusters in a specified availability zone (AZ). You can set up peering between an ODB network and a VPC, which enables applications to connect to your Exadata Database.

Note

You can not peer the same VPC to two different ODB networks.

Customers can use AWS APIs (ODB namespace) to create and manage their ODB network. The ODB network requires a client subnet CIDR for Exadata VM Cluster launches, backup subnet CIDR for managed database backups, and an availability zone where the ODB network is created.

The ODB network is a private network, and by default, does not have connectivity to AWS VPCs, on-premises network or the internet. To connect to Exadata Databases in the ODB network privately, customers can set up a peering connection between one VPC and the ODB network. This peering between ODB Network and the VPC is referred to as ODB peering.

After ODB peering is set up, EC2 instances or applications in the VPC can connect to Exadata Databases in the ODB network. Customers must pass in the peer-vpc-arn to the ODB Network to setup ODB peering to set up connectivity between the ODB network and VPC.

Note

Restriction of CIDR blocks: In the setup flow, you will enter CIDR values for Client subnet CIDR and Backup subnet CIDR. These CIDR blocks must comply with the following:
  1. Valid Private IPV4 CIDR Ranges: The CIDR block must be private and IPV4. For example, 10.0.0.0/16, 172.16.0.0/16, 192.168.1.0/26.
  2. Allowed CIDR Range: The CIDR block range is from /16 to /27. The Upper Bound (/16) is limited by OCI’s VCN size. For more information, see Allowed VCN Size and Address Ranges. The Lower Bound (/27) is based on provisioning IP requirements for Exadata VM Clusters. For more information, see Requirements for IP addresses space.
    Note

    The ODB Network reserves three (3) IP addresses in the primary subnet. It is recommended that you allocate more space for the subnet than the minimum required. For example, using /25 instead of /27 reduces the impact of reserved addresses on the subnet's available space. For future growth, additional addresses provide availability to scale up your Exadata VM Cluster beyond your immediate needs.
  3. Restricted CIDR blocks:
    1. 100.106.0.0/16 - Reserved for the cluster interconnect by OCI automation.
    2. 100.107.0.0/16 - Reserved for the cluster interconnect by OCI automation.
    3. 100.105.0.0/16 - Reserved for local storage interconnect.
    4. 169.254.0.0/16 - IP Addresses Reserved for Use by Oracle.
    5. Reserved Class D 224.0.0.0 - 239.255.255.255 - IP Addresses Reserved for Use by Oracle
    6. Reserved Class E 240.0.0.0 - 255.255.255.255 - IP Addresses Reserved for Use by Oracle
  4. Restriction of CIDR blocks on AWS VPC: There are permitted and restricted VPC CIDR block associations. For more information, see https://docs.aws.amazon.com/vpc/latest/userguide/vpc-cidr-blocks.html#add-cidr-block-restrictions.
  5. CIDR blocks allocated for Client and Backup subnets must not overlap with each other or with the peered VPC.
  1. From the Oracle Database@AWS dashboard or the ODB network list, select the Create ODB network button.
  2. In the ODB network name field, enter an identifier of your choice for the name. The identifier can be up to 255 characters. It can include the following characters: a-z, A-Z, 0-9, underscore (_), and dash (-). It must start with a letter or underscore (_) and cannot contain two successive hyphens(-).
  3. The Availability Zone field is a drop-down that contains the AZ where the ODB network will exist. The list is limited by your subscription.
  4. In the Client subnet CIDR field, enter a CIDR block range for your client network. See the Note for more information on and restrictions for this CIDR block.
  5. In the Backup subnet CIDR field, enter a CIDR block range for your client network. See the Note for more information on and restrictions for this CIDR block.
  6. In the VPC ID drop-down field, select a VPC. This enables EC2 and applications instances in this VPC to connect to your Exadata Database. While marked as optional, it is only optional during the creation flow. It will have to be set now or later to enable the connection to your Exadata Database.
  7. Under the DNS configuration section, there are two options available to set your domain name. These options are Default and Custom domain name.
  8. If you select the Default option, you will notice that the Domain name field is read-only.
  9. In the Domain name prefix field, enter a name which will be concatenated with the Domain name to provide the IP name for your Exadata Database. The Domain name prefix must be 1-15 letters or numbers, and it must start with a letter.
  10. If you want to customize your domain name, select the Custom domain name option, and then specify a name.
    For the Custom domain name option, the Domain name must not exceed 254 characters.
    During the creation process of Exadata VM Cluster, if a Custom domain name is provided, the Host domain name displays the customized domain name depending on your ODB Network selection.
    If a Custom domain name is provided, during the process Create Network Anchor, you must use this customized domain name.
  11. You can enter Tags, if desired or required, by selecting the Add new tag button. Do this for each tag you want or need to add.
  12. When finished, select the Create ODB Network button to create your network, or the Cancel button to cancel ODB network creation. Either way, you will return to the ODB network list. You can monitor the status of your ODB network creation request, or manage existing ODB networks. This step can take several minutes until the status changes to Available.

What's Next?

Continue provisioning with Task 3: Create an Exadata Infrastructure for Oracle Database@AWS.