You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/oracle/oracle-db/oracle-database-plan-ip.md
+30-30Lines changed: 30 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.date: 08/29/2024
9
9
ms.author: jacobjaygbay
10
10
---
11
11
12
-
# Plan for IP Address Space for Oracle Database@Azure
12
+
# Plan for IP address space for Oracle Database@Azure
13
13
14
14
When you set up Oracle Database@Azure, you need to plan your IP address space to ensure that you have enough IP addresses for your virtual machine clusters and networking services.
15
15
@@ -23,67 +23,67 @@ Consider the following points when setting up networking:
23
23
24
24
Other requirements specific to the Client Subnet and the Backup Subnet are provided in the sections for each subnet type that follow.
25
25
26
-
## Client Subnet requirements
26
+
## Client subnet requirements
27
27
28
28
The Client Subnet has the following IP address requirements:
29
29
30
-
- Four IP addresses are needed for each virtual machine. virtual machine clusters have a minimum of two virtual machines. Therefore, a virtual machine cluster with two virtual machines requires eight IP addresses in the Client Subnet. Each additional virtual machine added to a virtual machine cluster increases the number of IP addresses needed in the Client Subnet by 4 IPs.
30
+
- Four IP addresses are needed for each virtual machine. virtual machine clusters have a minimum of two virtual machines. Therefore, a virtual machine cluster with two virtual machines requires eight IP addresses in the Client Subnet. Each other virtual machine added to a virtual machine cluster increases the number of IP addresses needed in the Client Subnet by 4 IPs.
31
31
- Each virtual machine cluster requires three IP addresses for Single Client Access Names ([SCANs](https://docs.oracle.com/en/cloud/paas/exadata-cloud/csexa/connect-db-using-net-services.html)), regardless of how many virtual machines are present in the virtual machine cluster.
32
32
- 17 IP addresses are reserved for networking services in the Client Subnet, regardless of how many virtual machine clusters are present in the Client Subnet. The 17 addresses are the first 16 IP addresses, and the last IP address.
33
33
34
34
**Example**: IP addresses required for a Client Subnet that has one virtual machine cluster with two virtual machines.
35
35
36
36
``11 IPs *(virtual machine cluster with 2 virtual machines, plus 3 SCANs)* + 17 IPs *(Networking)* = 28 IPs.``
37
37
38
-
### virtual machine cluster scenarios: CIDR size needed for the Client Subnet
38
+
### Virtual machine cluster scenarios: CIDR size needed for the client subnet
39
39
40
-
The following table shows scenarios of provisioned virtual machine 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.
40
+
The following table shows scenarios of provisioned virtual machine clusters of varying 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.
|2 virtual machine clusters with 2 virtual machines each *(22 IPs + 17 Networking = 39)*||2|5|10|22|45|
48
-
|2 virtual machine clusters with 3 virtual machines each *(30 IPs + 17 Networking = 47)*||1|3|7|16|33|
49
-
|2 virtual machine clusters with 4 virtual machines each *(38 IPs + 17 Networking = 55)*||1|2|6|13|26|
44
+
|One virtual machine cluster with two virtual machines *(11 IPs + 17 Networking = 28)*|1|4|10|21|45|91|
45
+
|One virtual machine cluster with three virtual machines *(15 IPs + 17 Networking = 32*|1|3|7|15|33|67|
46
+
|One virtual machine cluster with four virtual machines *(19 IPs + 17 Networking = 36)*||2|5|12|26|53|
47
+
|Two virtual machine clusters with two virtual machines each *(22 IPs + 17 Networking = 39)*||2|5|10|22|45|
48
+
|Two virtual machine clusters with three virtual machines each *(30 IPs + 17 Networking = 47)*||1|3|7|16|33|
49
+
|Two virtual machine clusters with four virtual machines each *(38 IPs + 17 Networking = 55)*||1|2|6|13|26|
50
50
51
-
### virtual machine cluster scenarios: CIDR size needed for the Client Subnet
51
+
### Virtual machine cluster scenarios: CIDR size needed for the client subnet
52
52
53
-
The following table shows scenarios of provisioned virtual machine 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.
53
+
The following table shows scenarios of provisioned virtual machine clusters of varying 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.
|2 virtual machine clusters with 2 virtual machines each *(22 IPs + 17 Networking = 39)*||1|3|6|13|26|
61
-
|2 virtual machine clusters with 3 virtual machines each *(30 IPs + 17 Networking = 47)*||1|2|5|10|21|
62
-
|2 virtual machine clusters with 4 virtual machines each *(38 IPs + 17 Networking = 55)*||1|2|4|9|18|
57
+
|One virtual machine cluster with two virtual machines *(11 IPs + 17 Networking = 28)*|1|2|4|9|18|36|
58
+
|One virtual machine cluster with three virtual machines *(15 IPs + 17 Networking = 32)*|1|2|4|8|16|32|
59
+
|One virtual machine cluster with four virtual machines *(19 IPs + 17 Networking = 36)*||1|3|7|14|28|
60
+
|Two virtual machine clusters with two virtual machines each *(22 IPs + 17 Networking = 39)*||1|3|6|13|26|
61
+
|Two virtual machine clusters with three virtual machines each *(30 IPs + 17 Networking = 47)*||1|2|5|10|21|
62
+
|Two virtual machine clusters with four virtual machines each *(38 IPs + 17 Networking = 55)*||1|2|4|9|18|
63
63
64
-
## Backup Subnet requirements
64
+
## Backup subnet requirements
65
65
66
66
The Backup Subnet has the following IP address requirements:
67
67
68
-
-3 IP addresses for each virtual machine. virtual machine clusters have a minimum of 2 virtual machines. Therefore, a virtual machine cluster with 2 virtual machines requires 6 IP addresses in the backup subnet. Each additional virtual machine added to a virtual machine cluster increases the number of IP addresses needed in the Backup Subnet by 3 IPs.
69
-
- Networking services require 3 IP addresses for the Backup Subnet, regardless of how many virtual machine clusters are present in the Backup Subnet.
68
+
-Three IP addresses for each virtual machine. virtual machine clusters have a minimum of two virtual machines. Therefore, a virtual machine cluster with two virtual machines requires six IP addresses in the backup subnet. Each other virtual machine added to a virtual machine cluster increases the number of IP addresses needed in the Backup Subnet by 3 IPs.
69
+
- Networking services require three IP addresses for the Backup Subnet, regardless of how many virtual machine clusters are present in the Backup Subnet.
70
70
71
-
**Example**: IP addresses required for a Backup Subnet that has 1 virtual machine cluster with 2 virtual machines.
71
+
**Example**: IP addresses required for a Backup Subnet that has one virtual machine cluster with two virtual machines.
### virtual machine cluster scenarios: CIDR size needed for the Backup Subnet
75
+
### Virtual machine cluster scenarios: CIDR size needed for the Backup Subnet
76
76
77
77
The following table shows scenarios of provisioned virtual machine 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 display all possible scenarios.
0 commit comments