Exadata Cloud Service (ExaCS) Default Network Routing (Doc ID 2108581.1)

Last updated on DECEMBER 02, 2022

Applies to:

Goal

This article will guide new Exadata Cloud Service (ExaCS) customers through the process of setting up default routing in their ExaCS environments.

ExaCS is a highly configurable database environment.  Oracle provides root and sys level access to the environment which allows customers to modify their ExaCS environment to best suit their database needs and goals.

Each ExaCS environment has three networks and each is designed to serve a certain role.  The networks are :

• Management (eth0) - Used by root/non-root users to perform system and database maintenance
• SCAN/Client (bondeth0) - Used only for traffic into and out of the database for applications and SQL*Plus
• Backup (bondeth1) - Used to perform operating system & database backups to either Cloud Storage or back to the customer home network

Default routing is placed on the interface to which the first connection to ExaCS environment is made.  For example:  If the first connection as root user is via the Management network, then it will be eth0. 

Once the default routing is in place, this could cause issues with access via the other routes.  In the example above, if the Management network (eth0) is the default route, this could cause issues with the database client connections attempting to access the SCAN/Client network.
 

Solution