1.10.3 IP Address Requirements for Oracle Exadata Rack
Oracle Exadata Database Machine and Oracle Exadata Storage Expansion Rack require a dedicated allocation of host names and IP addresses. The number of required IP addresses primarily depends on the size of the system and whether it is configured to use virtual machines (VMs).
The detailed network configuration, including host names and IP addresses, is generated from information supplied to Oracle Exadata Deployment Assistant (OEDA).
You should configure the IP addresses in your existing networks after you run OEDA. All IP addresses in the configuration file must be unassigned at the time of initial configuration. In addition, all IP addresses must be statically-assigned IP addresses, not dynamically-assigned (DHCP) addresses.
All RDMA Network Fabric IP addresses must be in the same subnet, with a minimum subnet mask of 255.255.240.0 (or /20). The subnet mask chosen should be wide enough to accommodate possible future expansion of the Oracle Exadata and the internal network.
You can use the information in the following sections to calculate the IP address requirement for Oracle Exadata. However, ensure that you use the configuration information generated in OEDA as your authoritative guide.
Rack-Level IP Address Requirements
The following table outlines the rack-level IP address requirements for Oracle Exadata Database Machine. These addresses are required regardless of the configuration options that are selected for the system. For Oracle Exadata Storage Expansion Rack, no further IP addresses are required beyond these rack-level IP addresses.
Network | IP Address Requirements |
---|---|
Administration Network |
|
RDMA Network Fabric (Private Network) |
2 IP addresses for each database server or storage server. Note: Older configurations (typically X3 and prior) may be configured with Linux Ethernet bonding, which uses 1 IP address for each database server or storage server. |
Bare-Metal IP Address Requirements
When Oracle Exadata Database Machine is configured without VMs (otherwise known as a bare-metal configuration), one additional set of cluster-level IP addresses is required in addition to the rack-level addresses outlined in the previous table. Use the following table to determine the additional IP addresses required for a bare-metal configuration.
Network | IP Address Requirements |
---|---|
Client Network |
|
Additional Network(s) |
1 IP address for each additional network interface on each database server. |
VM Cluster IP Address Requirements
When Oracle Exadata Database Machine is configured with virtual machines (VMs), each VM cluster requires a separate set of IP addresses, which are in addition to the system-level addresses outlined previously. Use the following table to determine the additional IP addresses required for each VM cluster.
Network | IP Address Requirements |
---|---|
Administration Network |
1 IP address for the administration network interface on each database server VM. |
Client Network |
|
Additional Network(s) |
1 IP address for each additional network interface on each database server VM. |
RDMA Network Fabric (Private Network) |
2 IP addresses for each database server VM. |