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.

Note

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.
    1. Open the navigation menu, click Networking, and then click Virtual cloud networks.
    2. Click the VCN you're interested in.
    3. Under Resources, click Local Peering Gateways.
    4. For the LPG you're interested in, click the Actions menu (Actions Menu), and then click either: 
      • Associate With Route Table: If the LPG has no route table associated with it yet.
      • Replace Route Table Association: If you're changing which route table is associated with the LPG.
    5. Select the compartment where the route table resides, and select the route table itself.
    6. Click Associate.
  • Use the network local-peering-gateway update command and required parameters to change the name of a local peering gateway (LPG):

    oci network local-peering-gateway update --local-peering-gateway-id ocid --display-name new-name ... [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.