Oracle Cloud Infrastructure Documentation

Connecting Two Remote Peering Connections

Connects an RPC object to an RPC object on another DRG.

Prerequisite: The requestor must have:

  • The region the acceptor's VCN is in (the requestor's tenancy must be subscribed to the region).
  • The OCID of the acceptor's RPC.

The requestor RPC must perform this task.

When the connection is no longer needed, the RPCs can be disconnected by deleting one of the RPCs.

    1. On the Dynamic Routing Gateways list page, select the DRG that you want to work with. If you need help finding the list page or the DRG, see Listing DRGs.
    2. On the details page, perform one of the following actions depending on the option that you see:
      • On the Attachments tab, go to the Remote peering connection attachments section.
      • Under Resources, select Remote peering connection attachments.
    3. Select the name of the requestor RPC in the table.
    4. Select Establish Connection.

      Enter the following:

      • Region: The region that contains the acceptor's VCN. The list includes only those regions that both support remote VCN peering and that the requestor DRG's tenancy is subscribed to.
      • Remote Peering Connection OCID: The OCID of the acceptor's RPC.
    5. Select Establish Connection.

    The connection is established and the RPC's state changes to PEERED.

  • Use the network remote-peering-connection connect command and required parameters to connect an RPC to an RPC on another DRG:

    oci network remote-peering-connection connect --peer-id acceptor-ocid  --peer-region-name region --remote-peering-connection-id rpc-ocid ... [OPTIONS]

    The region names that could be used for --peer-region-name are listed in Regions and Availability Domains. For example: us-ashburn-1.

    For a complete list of parameters and values for CLI commands, see the CLI Command Reference.

  • Run the ConnectRemotePeeringConnections operation to connect an RPC to an RPC on another DRG.