Last updated: 2021-09-06 16:35: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.

    • 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).
      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.
      • A custom route should be withdrawn first before it can be disabled if it has been published to a CCN.

      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