Network / IP Address requirements for Exadata (Bare Metal)

If you have decided to buy Exadata Machine to run your Oracle Databases, then your Exadata deployment journey will start with network setup and configuration. For this blog, I would use Exadata ¼ Rack but same can apply for Exadata eight Rack. It is important to remember that there is a huge different between network / IP Address requirements for Bare Metal and virtualized Exadata Machine, this post only covers Bare Metal Exadata network configuration.

Basically, there are 4 different types of Networks in Exadata. You will need around 32+ ip address, depending on your backup network configuration and spine switch.  Subnet mask can be shared between Admin, Client Access and Backup network but Private InfiniBand needs to have a separate subnet mask

  1. Administration (Management) – 15 IP’s
  2. Client Access –  7 IP’s
  3. Private InfiniBand – 10 IP’s
  4. Additional ( Backup ) – 2 IP’s

 

Administration Network (Management Network) 

Each database server and Exadata Storage Server has two network interfaces for administration. One network provides management access to the operating system through the Ethernet interface, and the other network provides access to the Integrated Lights Out Manager (ILOM) through the ILOM Ethernet interface. All IP addresses and corresponding hostnames should be registered in DNS

 

Components Total IP’s
Database Server 2
Storage Server 3
Leaf Switch 2
PDU Switch 2
Admin Switch 1
ILOM Network 5
Total 15

Client Access Network

Applications access the database through the client Ethernet network using Single Client Access Name (SCAN) and Oracle RAC Virtual IP (VIP) addresses. All IP addresses and corresponding hostnames should be registered in DNS

 

Components Total IP’s
Database Server 2
VIP 2
SCAN IP 3
Total 7

Private InfiniBand Network

The InfiniBand network is the private network between database servers and storage servers. Oracle Database uses this network for Oracle RAC cluster interconnect traffic and for accessing data on Exadata Storage Servers. This non-routable network is fully contained in Oracle Exadata Database Machine, and does not connect to your existing network. This network is automatically configured during installation. All IP addresses and corresponding hostnames should be registered in DNS.

 

Components Total IP’s
Database Server 4
Storage Server 6
Total 10                            

Backup Network (Optional Network)

Database servers can connect to additional existing networks using the available open ports not used by the management and client networks.

 

Components Total IP’s
Database Server 2
Total 2                              

Conclusion

Network configuring is an important part of Exadata deployment, any mishaps or even a typo can cause delays and loss of revenue. Make sure you do it right the first time. Good Luck!