Each virtual border router (VBR) is associated with a route table. You can configure routes in the route table of a VBR to control where network traffic is forwarded.

Background information

To forward network traffic between a virtual private cloud (VPC) and a data center, you must add two routes to the route table of the VBR that is used to connect the data center to the VPC. One of the routes points to the physical connection and the other route points to the VPC. You can configure Border Gateway Protocol (BGP) routes on VBRs for data centers. For more information, see Configure BGP.

When you manage routes of a VBR, take note of the following items:
  • You can query routes by type in the route table of a VBR. Fuzzy match is supported.
  • Each route table supports up to 48 custom routes.
  • Source address-specific policy-based routes are not supported.

Procedure

  1. Log on to the Express Connect console.
  2. In the left-side navigation pane, click Virtual Border Routers (VBRs).
  3. Select the region where the VBR that you want to manage is created and click its ID.
  4. On the Virtual Border Routers (VBRs) page, click the Routes tab and click Add Route.
  5. In the Add Route dialog box, set the following parameters and click OK.
    Parameter Description
    Next Hop Type
    Select the type of the next hop. Supported types are:
    • VPC: The VBR forwards network traffic of a destination CIDR block to a specified VPC.
    • Physical Connection Interface: The VBR forwards network traffic of a destination CIDR block to a specified physical connection port.
    Destination Subnet Enter the destination CIDR block.
    Next Hop Select a next hop based on the type of next hop that you selected.
    Warning When you use Cloud Enterprise Network (CEN), Express Connect, Smart Access Gateway (SAG), or Virtual Private Network (VPN) to access internal Object Storage Service (OSS) endpoints, you must configure routes that point to the CIDR blocks of the regions where the endpoints are created. For more information, see Regions and endpoints.