Associating a Route Table with an Existing LPG
To use transit routing, you must associate a route table to an LPG after you create the LPG.
Prerequisite: The route table must exist and belong to the VCN that the LPG belongs to.
This task is related to an advanced routing scenario called transit routing. Associating a route table to an LPG influences the behavior of traffic entering the VCN through the LPG.
An LPG can exist without having an associated route table. After you associate a route table with an LPG there must always be a route table associated with it, but you can associate a different route table. You can also edit the table's rules, or delete some or all of the rules.
The route rules in a route table associated with an LPG can point to a DRG or a private IP address in the same VCN as the LPG.
Use the network local-peering-gateway update command and required parameters to change the name and associated route table of a local peering gateway (LPG):
oci network local-peering-gateway update --local-peering-gateway-id ocid --route-table-id ocid ... [OPTIONS]
For a complete list of parameters and values for CLI commands, see the CLI Command Reference.
Run the UpdateLocalPeeringGateway operation to set the
routeTableId
to associate a route table to an LPG.