Last updated: 2021-07-01 16:17:55
    • The default route table of a VPC cannot be deleted.
    • After a VPC is created, its route table will be automatically provided with a default route, indicating that all resources in this VPC are interconnected through the private network. This routing policy cannot be modified or deleted.
    Destination Next hop type Next hop
    Local Local Local
    • Dynamic routing protocols such as BGP and OSPF are not supported.
    • The support for ECMP varies with routes, as shown in the following table.
    Next hop typeForming ECMP with the same typeForming ECMP with another typeMaximum number of ECMPs
    NAT GatewaySupportedNot supportedSame type: up to 8; different types: 1
    Inter-region peering connectionNot supportedNot supportedN/A
    Cross-region peering connectionNot supportedSupported, with CCNDifferent types: 1
    Direct connect gatewayNot supportedSupported, with CCNDifferent types: 1
    HAVIPNot supportedNot supportedN/A
    VPN gatewayNot supportedNot supportedN/A
    CVMSupportedNot supportedSame type: up to 8; different types: 1
    CCNNot supportedSupported, with direct connect gateway or cross-region peering connectionDifferent types: 1
    Note:

    • Equal Cost Multi-path (ECMP) means there are multiple equal-cost routes to a single destination.
    • That public IP of CVM has a higher priority than that of NAT Gateway when routing to the same destination.
    • Because of different priorities, EIP and other types of routes are not considered for ECMP.
    • Direct connect gateway and CCN can form ECMP. However, it will not check the route’s health status, or automatically exclude unhealthy routes. To form ECMP with CCN, first submit a ticket.
    • Multiple NAT Gateway routes can form ECMP. However, it will not check the route’s health status, or automatically exclude unhealthy routes.
    • Multiple CVM routes can form ECMP. However, it will not check the route’s health status, or automatically exclude unhealthy routes.
    • Routes can be published to CCN.
      The following routes can be published to CCN.
    Next hop type Publishing to CCN by default Manually publishing or withdrawing Description
    Local Supported Not supported Assigned by the system. The VPC IP range connecting to CCN will be automatically published to CCN, including primary and secondary CIDR blocks (except for TKE IP ranges).
    VPN Gateway Not supported Supported A custom route to VPN gateway. When the IP range is all 0 or the routing policy is disabled, the route cannot be published to CCN.
    CVM Not supported Supported A custom route to CVM. When the IP range is all 0 or the routing policy is disabled, the route cannot be published to CCN.
    HAVIP Not supported Supported Custom route to HAVIP. When the IP range is all 0 or the routing policy is disabled, the routes cannot be published to CCN.
    Note:

    • A disabled custom route cannot be published to CCN.
    • To disable a custom route that has been published to CCN, first withdraw it.

    Quota Limits

    Resource Limit
    Number of route tables per VPC 10
    Number of route tables associated with each subnet 1
    Number of routing policies per route table 50