Plan for IP Address Space in Oracle Database@Google Cloud
Use the tables in this topic to find the minimum subnet CIDR size for Oracle Database@Google Cloud database products.
Note the following points when setting up networking:
- For Autonomous Database, the minimum CIDR size is /27.
- For Exadata Database Service, we recommend using a CIDR size of /27 to make future hardware scaling easier.
- IP address ranges allocated to Autonomous Database and Exadata VM clusters must not overlap with other CIDRs in use, as this might cause routing issues. Take cross-region routing into consideration when configuring CIDRs for Oracle Database@Google Cloud.
- For Exadata X9M: IP addresses 100.106.0.0/16 and 100.107.0.0/16 are reserved for the interconnect, and can't be allocated to client or backup networks.
Other requirements specific to the Client Subnet and the Backup Subnet are provided in the sections for each subnet type that follow.
Details for Exadata Database Service
Client Subnet requirements
The Client Subnet has the following IP address requirements:
- 4 IP addresses are needed for each virtual machine. VM clusters have a minimum of 2 virtual machines. Therefore, a VM cluster with 2 virtual machines requires 8 IP addresses in the Client Subnet. Each extra virtual machine added to a VM cluster increases the number of IP addresses needed in the Client Subnet by 4 IPs.
- Each VM cluster requires 3 IP addresses for Single Client Access Names (SCANs), regardless of how many virtual machines are present in the VM cluster.
VM cluster scenarios: CIDR size needed for the Client Subnet
The following table shows scenarios of provisioned VM clusters of differing sizes. The number of each scenario that can fit in a Client Subnet depends on the CIDR size used by the subnet. This table doesn't show all possible scenarios.
| Scenario | /27 | /26 | /25 | /24 | /23 | /22 |
|---|---|---|---|---|---|---|
| 1 VM cluster with 2 virtual machines (11 IPs) | 2 | 5 | 11 | 23 | 46 | 93 |
| 1 VM cluster with 3 virtual machines (15 IPs) | 2 | 4 | 8 | 17 | 34 | 68 |
| 1 VM cluster with 4 virtual machines (19 IPs) | 1 | 3 | 6 | 13 | 26 | 53 |
| 2 VM clusters with 2 virtual machines each (22 IPs) | 1 | 2 | 5 | 11 | 23 | 46 |
| 2 VM clusters with 3 virtual machines each (30 IPs) | 1 | 2 | 4 | 8 | 17 | 34 |
| 2 VM clusters with 4 virtual machines each (38 IPs) | 1 | 3 | 6 | 13 | 26 |
Backup Subnet requirements
The Backup Subnet has the following IP address requirements:
- 3 IP addresses for each virtual machine. VM clusters have a minimum of 2 virtual machines. Therefore, a VM cluster with 2 virtual machines requires 6 IP addresses in the backup subnet. Each additional virtual machine added to a VM cluster increases the number of IP addresses needed in the Backup Subnet by 3 IPs.
VM cluster scenarios: CIDR size needed for the Backup Subnet
The following table shows scenarios of provisioned VM clusters of differing sizes. The number of each scenario that can fit in a Backup Subnet depends on the CIDR size used by the subnet. This table doesn't show all possible scenarios.
| Scenario | /28 | /27 | /26 | /25 | /24 | /23 |
|---|---|---|---|---|---|---|
| 1 VM cluster with 2 virtual machines (6 IPs) | 2 | 5 | 10 | 25 | 42 | 85 |
| 1 VM cluster with 3 virtual machines (9 IPs) | 1 | 3 | 7 | 14 | 28 | 56 |
| 1 VM cluster with 4 virtual machines (12 IPs) | 1 | 2 | 5 | 10 | 21 | 42 |
| 2 VM clusters with 2 virtual machines each (12 IPs) | 1 | 2 | 5 | 10 | 21 | 42 |
| 2 VM clusters with 3 virtual machines each (18 IPs) | 1 | 3 | 7 | 14 | 28 | |
| 2 VM clusters with 4 virtual machines each (24 IPs) | 1 | 2 | 5 | 10 | 21 |