Transit routing

You can implement an advanced VCN routing scenario called transit routing. It enables communication between an on-premises network and multiple VCNs over a single FastConnect or IPSec VPN. For more information, see Advanced Scenario: Transit Routing.

Changes to the API to Support Transit Routing

DRGs:

• The DrgAttachment object object includes a routeTableId attribute to indicate the OCID of the route table associated with the DRG attachment, if any.
• When you attach a DRG to a VCN, you can specify a route table to associate with the DRG attachment. See the CreateDrgAttachmentDetails object.
• When you update the DRG attachment, you can specify a route table to associate with the attachment. See the UpdateDrgAttachmentDetails object.

LPGs:

• The LocalPeeringGateway object includes a routeTableId attribute to indicate the OCID of the route table associated with the LPG, if any.
• When you create an LPG, you can specify a route table to associate with the LPG. See the CreateLocalPeeringGatewayDetails object.
• When you update an LPG, you can specify a route table to associate with the LPG. See the UpdateLocalPeeringGatewayDetails object.
• The LocalPeeringGateway object has changed to indicate all the CIDRs that are advertised by the VCN at the other end of the peering:
  • The peerAdvertisedCidr attribute's value has changed to support transit routing. It now shows the smallest aggregate CIDR that contains all the CIDR routes advertised by the VCN at the other end of the peering from the LPG. Example values for peerAdvertisedCidr: 192.168.0.0/16. Or if 192.168.0.0/16 is aggregated with 172.16.0.0/24, the value would be 128.0.0.0/1.
  • The new peerAdvertisedCidrDetails attribute lists all the individual CIDR routes that make up the peerAdvertisedCidr aggregate. Example value (to continue with the preceding example of the aggregate): [192.168.0.0/16, 172.16.0.0/24]