How to setup Dynamic Routing Gateway (DRG) in Oracle Cloud Infrastructure (OCI)

 To create a Dynamic Routing Gateway (DRG) in Oracle Cloud Infrastructure (OCI), follow these steps:

1. Access the OCI Console:

  • Log in to your OCI account.
  • Navigate to the Networking section from the main menu.

2. Create a DRG:

  1. Go to DRG:
    • In the Networking section, click on Dynamic Routing Gateways.
  2. Create New DRG:
    • Click Create Dynamic Routing Gateway.
    • Enter a name for the DRG (e.g., "DRG for VCN1").
    • Optionally, provide a description for easier identification.
    • Select the compartment where you want to create the DRG.
    • Click Create DRG.

3. Attach DRG to a Virtual Cloud Network (VCN):

  1. After the DRG is created, attach it to a VCN.
  2. In the VCN section, choose the VCN to which you want to attach the DRG.
  3. Under the Resources tab, click Dynamic Routing Gateways.
  4. Select Attach DRG and choose the DRG you just created.
  5. Click Attach.

4. Configure Route Tables:

  • Go to the Route Tables in the VCN.
  • Add a route rule for the DRG. This ensures traffic is routed through the DRG for external or on-premises networks.
  • Set the Target Type as Dynamic Routing Gateway and configure the route details based on your networking needs.

5. Configure DRG Attachments (Optional):

If needed, configure attachments like FastConnect or Site-to-Site VPN for your DRG.

  1. Navigate to Dynamic Routing Gateways and select your DRG.
  2. Click on Create Attachment and follow the prompts to set up connections with external networks or on-premises systems.

6. Update Security Rules:

  • Update your security lists and network security groups (NSGs) to allow traffic through the DRG as per your requirements.

7. Verify Configuration:

  • Ensure all necessary connections and route rules are configured correctly.
  • Test the connectivity between OCI and on-premises (if applicable).

Comments

Post a Comment

Popular posts from this blog

Key points on Read-Only Instance and Read-Only Database

 In Oracle, both Read-Only Instance and Read-Only Database provide mechanisms to limit data modifications, but they are used in different contexts and for different purposes. Here's a comparison: 1. Read-Only Instance Definition : A read-only instance is a configuration in Oracle Real Application Clusters (RAC) where one or more instances of a multi-instance database are set up to operate in read-only mode. This is typically done in environments with high concurrency for both read and write operations. Key Features : Allows real-time query scaling by dedicating specific instances to read-only operations. Write operations are not allowed on the designated read-only instance, but other instances in the cluster can still handle write operations. Useful in RAC configurations for load balancing , where read workloads can be distributed across multiple read-only instances. Instance-specific: The database remains fully functional (read-write) when accessed through other instances. Us...
Read more

Steps to create database link between Oracle database and SQL Server

 Creating a database link between SQL Server and Oracle allows seamless data exchange between the two systems. Here’s a step-by-step guide: Step 1: Install the Required Drivers Install Oracle Database Gateway for SQL Server (ODG4MS). This acts as a bridge between Oracle and SQL Server. Ensure the Oracle Client is installed on the Oracle database server or the server acting as the gateway. Step 2: Configure the Oracle Database Gateway Locate Configuration Files: Navigate to the $ORACLE_HOME/network/admin directory on the Oracle Gateway server. Edit tnsnames.ora: Add an entry for the database link pointing to the SQL Server database: dg4msql =   (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = <SQL_SERVER_HOSTNAME>)(PORT = 1521))     (CONNECT_DATA = (SID = dg4msql))     (HS=OK)  -- Required for heterogeneous services   )   Edit listener.ora: Update the Oracle listener configuration to recognize the gateway: SID_LIST_LISTENE...
Read more

How to Configure Logging for EM 12c Management Agent

The goal of this article is to provide instruction on how to enable logging for the Enterprise Manager 12c Management Agent.. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The logging properties for the agent are stored in $EMSTATE/sysman/config/emd.properties file, same as in 11.1. But the properties that control logging follow the log4j configuration syntax instead of the syntax supported by the 11.1 agent. To active changes to the logging parameters, you can use either of the emctl commands: emctl reload agent emctl setproperty agent Overview Agent logging entries look similar to the standard log4j logging, with the only significant difference being the prefix 'Logger.' that you will see on each line. For example: # logging properties Logger.log4j.appender.Rolling=org.apache.log4j.RollingFileAppender Logger.lo...
Read more