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

Creating Physical Standby using RMAN Duplicate Without Shutting down The Primary

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.4 - Release: 10.1 to 10.2 Information in this document applies to any platform. Oracle Server Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 Goal  - Ref Metalink ID - 789370.1 The following note describes step-by-step procedure to create physical standby by using RMAN duplicate without shutting down the primary (Production) database. Database Name :- prim Primary db_unique_name :- prim standby db_unique_name :- stdby Primary Hostname :- raca.idc.oracle.com standby Hostname :- core1.idc.oracle.com Solution 1.Enable force logging. 2.Create SRL(standby redo logs). 3.Make proper changes in the parameter file of primary. 4.Backup the database that includes backup of datafiles, archivelogs and controlfile for standby and copy the backups to standby server. 5.Create the parameter file for standby, 6.Establish the connectivity from primary to standby. 7. Move backup to standby. 8 and 9. Start the standby instance. 10.U
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

index rebuild candidates oracle

Steps... CREATE TABLE index_log (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  last_inspected DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     CLOB); ALTER TABLE index_log ADD CONSTRAINT pk_index_log PRIMARY KEY (owner,index_name); CREATE TABLE index_hist (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  inspected_date DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     VARCHAR2(4000)); ALTER TABLE index_hist ADD CONSTRAINT pk_index_hist PRIMARY KEY  (owner,index_name,inspected_date); CREATE OR REPLACE PACKAGE index_util AUTHID CURRENT_USER IS vMinBlks     CONSTANT POSITIVE := 1000; vScaleFactor CONSTANT NUMBER := 0.6; vTargetUse   CONSTANT POSITIVE := 90;  -- equates to pctfree 10  vHistRet     CONSTANT POSITIVE := 10;  -- (#) records to keep in index_hist  procedure inspect_schema (aSchemaName IN VARCHAR2);  procedure inspect_index (aIndexOwner IN VARCHAR2, aIndexName IN VARCHAR2, a
Read more