Virtual Private Cloud:CreateRouteEntry

Usage notes

• CreateRouteEntry is an asynchronous operation. After you send a request, the system returns a request ID and runs the task in the background. You can call the DescribeRouteEntryList operation to query the status of a route entry.
  • If the route entry is in the Creating state, the route entry is being created.
  • If the route entry is in the Created state, the route entry is created.
• You cannot repeatedly call the CreateRouteEntry operation to add a custom route entry to the route table of a vRouter or a VBR within the specified period of time.

• A route table can contain up to 200 custom route entries.
• The destination CIDR block (DestinationCidrBlock) of a custom route entry cannot be the same as or overlap with the CIDR block of a vSwitch in the virtual private cloud (VPC).
• The destination CIDR block (DestinationCidrBlock) of a custom route entry cannot be 100.64.0.0/10 or a subset of it.
• The destination CIDR blocks (DestinationCidrBlock) of route entries in the same route table must be unique.
• If you do not include the mask length when you specify the destination CIDR block (DestinationCidrBlock), the destination CIDR block is considered a host IP address whose mask length is 32 bits.
• Multiple custom route entries can point to the same next hop (NextHopId).
• The next hop (NextHopId) of a custom route entry must belong to the same VPC as the route table.
• Equal-cost multi-path (ECMP) routing can be configured by specifying the NextHopList parameter.
  • When you add non-ECMP route entries, you must specify DestinationCidrBlock, NextHopType, and NextHopId, and you must not specify NextHopList.
  • When you add route entries for ECMP routing, you must specify DestinationCidrBlock and NextHopList, and you must not specify NextHopType or NextHopId.

• A route table can contain up to 200 custom route entries.
• The NextHopList parameter is not supported.
• The destination CIDR block (DestinationCidrBlock) of a custom route entry cannot be 100.64.0.0/10 or a subset of it.
• The destination CIDR blocks (DestinationCidrBlock) of route entries in the same route table must be unique.
• If you do not include the mask length when you specify the destination CIDR block (DestinationCidrBlock), the destination CIDR block is considered a host IP address whose mask length is 32 bits.
• Multiple custom route entries can point to the same next hop (NextHopId).
• The next hop (NextHopId) of a custom route entry must be a router interface associated with the VBR.
• You can add route entries only when the VBR is in the Active state, and the Express Connect circuit associated with the VBR is in the Enabled state and is not locked due to overdue payments.
• Only non-ECMP route entries are supported. When you add non-ECMP route entries, you must specify DestinationCidrBlock, NextHopType, and NextHopId, and you cannot specify NextHopList.

Request parameters

Response parameters

Examples

Sample requests

http(s)://[Endpoint]/?Action=CreateRouteEntry
&RegionId=cn-hangzhou
&RouteTableId=vtb-bp145q7glnuzd****
&DestinationCidrBlock=192.168.0.0/24
&NextHopId=i-j6c2fp57q8rr4jlu****
&ClientToken=02fb3da4-130e-11e9-8e44-001****
&RouteEntryName=test
&Description=test
&NextHopType=RouterInterface
&NextHopList=[{"NextHopId":"ri-2zeo3xzyf3cd8r4****","Weight":10,"NextHopType":"RouterInterface"}]
&<Common request parameters>

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<CreateRouteEntryResponse>
    <RouteEntryId>rte-sn6vjkioxte1gz83z****</RouteEntryId>
    <RequestId>0ED8D006-F706-4D23-88ED-E11ED28DCAC0</RequestId>
</CreateRouteEntryResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RouteEntryId" : "rte-sn6vjkioxte1gz83z****",
  "RequestId" : "0ED8D006-F706-4D23-88ED-E11ED28DCAC0"
}

Error codes

For a list of error codes, see Service error codes.