Adding Routes to a Route Table

Scenarios

Each route table comes with a default route, which is used to allow instances in a subnet to access public services on the cloud or different subnets in a VPC to communicate with each other. You can also add custom routes as required to control traffic routing.

If a route table is associated with a subnet, adding rules to the route table may affect how and where traffic is directed. Be careful with this operation as it may interrupt services.

Notes and Constraints

• Generally, the destination of a custom route cannot overlap with that of a local route. The destination of a local route can be a subnet CIDR block and CIDR blocks that are used for internal communications.
• You cannot add two routes with the same destination to a VPC route table even if their next hop types are different.

Procedure

1. Log in to the management console.

2. Click in the upper left corner and select the desired region and project.
3. Click in the upper left corner and choose Networking > Virtual Private Cloud.

   The Virtual Private Cloud page is displayed.

4. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.

   The route table list is displayed.

5. Locate the target route table and click its name.

   The route table details page is displayed.

6. Click Add Route and set parameters as prompted.

   You can click to add more routes.

   Table 1 Parameter descriptions

   Parameter	Description	Example Value
   Destination Type	Mandatory The destination type can only be IP address. You can set an IP address or CIDR block.	IP address
   Destination	Mandatory Enter the destination of the route. You can enter a single IP address or an IP address range in CIDR notation. NOTICE: If an IP address group contains an IP address range in the format of Start IP address-End IP address, the IP address group is not supported. For example, an IP address group cannot contain 192.168.0.1-192.168.0.62. You need to change 192.168.0.1-192.168.0.62 to 192.168.0.0/26.	IPv4: 192.168.0.0/16
   Next Hop Type	Mandatory Set the type of the next hop. NOTE: When you add or modify a custom route in a default route table, the next hop type of the route cannot be set to VPN gateway, Direct Connect gateway, or Cloud connection.	VPC peering connection
   Next Hop	Mandatory Set the next hop. The resources in the drop-down list box are displayed based on the selected next hop type.	peer-AB
   Description	Optional Enter the description of the route in the text box as required.	-

7. Click OK.

   You can view the new routes in the route list.