Skip to content

Commit 755bf25

Browse files
Merge pull request #292157 from jjaygbay1/docs-editor/oracle-database-plan-ip-1734557676
Update oracle-database-plan-ip.md
2 parents 816af7e + f1ecb8f commit 755bf25

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

articles/oracle/oracle-db/oracle-database-plan-ip.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,14 +25,22 @@ Other requirements that are specific to client subnets and backup subnets are de
2525

2626
## Client subnet requirements
2727

28-
The client subnet has the following IP address requirements:
28+
The Client Subnet has the following IP address requirements:
2929

30-
- Each virtual machine requires 4 IP addresses. Virtual machine clusters must have a minimum of two virtual machines. Therefore, a virtual machine cluster with two virtual machines requires 8 IP addresses in the client subnet. Each virtual machine that's added to a virtual machine cluster increases the number of IP addresses required in the client subnet by 4 IP addresses.
31-
- Each virtual machine cluster requires 3 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 in the virtual machine cluster.
32-
- In the client subnet, 17 IP addresses are reserved for networking services, regardless of how many virtual machine clusters are in the client subnet. The 17 IP addresses are the first 16 IP addresses and the last IP address.
30+
- 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 additional virtual machine added to a VM cluster increases the number of IP addresses needed in the Client Subnet by 4 IPs.
3331

34-
**Example**: The number of IP addresses required for a client subnet that has one virtual machine cluster with two virtual machines is *11 IPs (one virtual machine cluster with two virtual machines, plus three SCANs) + 17 IPs (for networking services) = 28 IPs*.
32+
- Each VM cluster requires 3 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 VM cluster.
3533

34+
- 13 IP addresses are reserved for networking services in the Client Subnet, regardless of how many VM clusters are present in the Client Subnet. The 13 addresses are: the first 4 IP addresses, the 9th to 16th IP address, and the last IP address.
35+
36+
For example, in a 10.0.0.0/24 subnet, the following 13 IPs are reserved:
37+
```
38+
- 10.0.0.0 to 10.0.0.3
39+
40+
- 10.0.0.8 to 10.0.0.15
41+
42+
- 10.0.0.255
43+
```
3644
### Scenarios: CIDR size required for a client subnet
3745

3846
The following table shows scenarios of provisioned virtual machine clusters of varying sizes. The number of instances of each scenario that can fit in a client subnet depends on the CIDR size of the subnet. This table doesn't show all possible scenarios.

0 commit comments

Comments
 (0)