Connecting to Another LPG
Connect a local peering gateway (LPG) to another one in a different virtual cloud network (VCN) in the same region.
The requestor must perform this task, and must have the OCID of the acceptor's LPG.
After you've peered an LPG to an LPG in another VCN, you can't peer it to a different LPG. For details, see Repurposing an LPG fails.
- Tip
If you're using the Console and the peering is between two VCNs in the same tenancy: Instead of specifying the acceptor's LPG OCID, you can instead pick the acceptor's VCN and LPG from lists of resources in the tenancy. However, you need to know both the name and compartment of the acceptor's VCN and LPG instead of the LPG's OCID. For reference, see Task B: Share information.The connection is established, and the LPG's state changes to PEERED.
At this point, the details of each LPG update to show the Peer VCN CIDR Block value for the other VCN. This is the CIDR of the other VCN across the peering from the LPG. Each administrator can use this information to update the route tables and security rules for their own VCN.
Use the network local-peering-gateway connect command and required parameters to connect this local peering gateway (LPG) to another one in the same region:
oci network local-peering-gateway update --local-peering-gateway-id this-ocid --peer-id peer-ocid ... [OPTIONS]
For a complete list of parameters and values for CLI commands, see the CLI Command Reference.
Run the ConnectLocalPeeringGateways operation to connect this local peering gateway (LPG) to another one in the same region.