The Client Subnet has the following IP address requirements:
4 IP addresses are needed for each virtual machine. 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.
3 IP addresses in the client subnet are reserved for the ODB network resource in AWS. Also, 3 IPs are reserved by OCI's networking service.
The minimum CIDR size for the client subnet is /27, and the maximum size is /16.
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 + 6 Networking = 17)
1
3
7
15
30
60
1 VM cluster with 3 virtual machines (15 IPs + 6 Networking = 21)
1
3
6
12
24
48
1 VM cluster with 4 virtual machines (19 IPs + 6 Networking = 25)
1
2
5
10
20
40
2 VM clusters with 2 virtual machines each (22 IPs + 6 Networking = 28)
1
2
4
9
18
36
2 VM clusters with 3 virtual machines each (30 IPs + 6 Networking = 36)
1
3
7
14
28
2 VM clusters with 4 virtual machines each (38 IPs + 6 Networking = 44)
1
2
5
11
23
Backup Subnet requirements 🔗
The Backup Subnet has the following IP address requirements:
3 IP addresses for each virtual machine. Each extra virtual machine added to a VM cluster increases the number of IP addresses needed in the Backup Subnet by 3 IPs.
Networking services require 3 IP addresses for the Backup Subnet, regardless of how many VM clusters are present in the Backup Subnet.
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
/27
/26
/25
/24
/23
/22
1 VM cluster with 2 virtual machines (6 IPs + 3 Networking = 9)
3
7
14
28
56
113
1 VM cluster with 3 virtual machines (9 IPs + 3 Networking = 12)
2
5
10
21
42
85
1 VM cluster with 4 virtual machines (12 IPs + 3 Networking = 15)
2
4
8
17
34
68
2 VM clusters with 2 virtual machines each (12 IPs + 3 Networking = 15)
2
4
8
17
34
68
2 VM clusters with 3 virtual machines each (18 IPs + 3 Networking = 21)
1
3
6
12
24
48
2 VM clusters with 4 virtual machines each (24 IPs + 3 Networking = 27)