Database Reference
In-Depth Information
Spec and Order the ODA Network Cabling
The good news about deploying ODAs on your network is that once you deploy an ODA model the first time, all of the
additional ODAs released for that model are identical. You only have to work out the cabling diagrams for a model
once. It's a good idea to formally prepare network and cabling specs for each ODA deployment using a standard
template. Unless you are working for a very small IT shop, don't assume that your networking and data center teams
will remember what they did to deploy the last ODA.
A couple of other good rules of thumb include understanding the lead times in your data center for requesting
cabling, and to “make friends with your networking and data center people.” The lead times may vary according to
cabling type; for example, are you bridging copper to fiber? The point regarding making friends speaks for itself.
Request IP Addresses
The IP addresses needed to deploy an ODA are documented in the ODA Getting Started Guide chapter titled “About
Oracle Database Appliance.” The requirements to deploy an ODA are common to both the original Oracle Database
Appliance and second-generation X3-2 models. The IP address range requirements for a physical ODA deployment,
also known as a bare-metal install, are listed in Table
5-3
.
Table 5-3.
Oracle Database Appliance IP requirements for a Bare-Metal (Nonvirtualized) Install
IP Type
Number of IPs
Comment
Public
2
Two IP addresses are required for the two ODA server nodes.
Each server requires an IP address for the physical host name.
Scan IPs
2
Two IP addresses to support the scan listener. ODAs run 2 scan
listeners. The scan IP addresses need to be configured in DNS
to be returned in round-robin order.
RAC VIP IPs
2
Typical RAC VIP address needed for each server node.
ILOM IPs
2
One ILOM or management network IP address per server node.
Additional networks
2
Two IP addresses per additional network, or one per server node;
for example, a PBN or private backup network to support backups
or NFS file system mounts.
The six public (host, scan, VIP) IP addresses need to be on the same network subnet, and they should be
sequential. The minimum number of IP addresses needed to deploy an ODA is eight. This includes six public and
two ILOM IPs. The Getting Started Guide lists the ILOM as required. ILOM connections can be made through the
serial port, in addition to creating a permanent connection through the NetMgt interface. It should be noted that the
configuration utility does not require ILOM IPs for the deployment.
In addition to the external networks, an ODA assigns four additional IPs to support the RAC interconnect and the
deployment of two internal RAC networks to support HAIP (Highly Available IP) redundancy and failover. The RAC
interconnect IP addresses are internally assigned, so they do not need to be requested from your network team.
The additional IP addresses required for a virtualized ODA deployment are listed in Table
5-4
.
