Creates a custom route table for an Enterprise Edition transit router.

Limits

Only Enterprise Edition transit routers support custom route tables. For more information about the regions and zones that support Enterprise Edition transit routers, see Transit routers.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String No CreateTransitRouterRouteTable

The operation that you want to perform. Set the value to CreateTransitRouterRouteTable.

TransitRouterId String Yes tr-bp1su1ytdxtataupl****

The ID of the Enterprise Edition transit router.

ClientToken String No 02fb3da4-130e-11e9-8e44-001****

The client token that is used to ensure the idempotence of the request.

You can use the client to generate a token, but you must ensure that it is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length.

TransitRouterRouteTableName String No testname

The name of the custom route table.

The name must be 1 to 128 characters in length, and can contain letters, digits, and the following special characters: , . ; / @ _ -. You can also leave the name empty.

TransitRouterRouteTableDescription String No testdesc

The description of the custom route table.

The description must be 2 to 256 characters in length, and can contain letters, digits, and the following special characters: , . ; / @ _ -. You can also leave the description empty.

DryRun Boolean No false

Specifies whether to only precheck the request. Check items include permissions and the status of the specified instances. Valid values:

  • false (default): sends a normal request. If the request passes the precheck, the custom route table is created.
  • true: sends a request for precheck only. No custom route table is created after the request passes the precheck. If you select this option, the system checks whether the required parameters are set, and whether the request syntax is valid. If the request fails to pass the precheck, the system returns an error. If the request passes the precheck, the system returns the ID of the request.

Response parameters

Parameter Type Example Description
RequestId String 599904C8-A3DA-4E5F-83B6-D5364E664247

The ID of the request.

TransitRouterRouteTableId String vtb-bp1xbcgpgcz9axl9m****

The ID of the custom route table.

Examples

Sample requests

http(s)://[Endpoint]/?Action=CreateTransitRouterRouteTable
&TransitRouterId=tr-bp1su1ytdxtataupl****
&<Common request parameters>

Sample success responses

XML format

<CreateTransitRouterRouteTableResponse>
  <TransitRouterRouteTableId>vtb-bp1xbcgpgcz9axl9m****</TransitRouterRouteTableId>
  <RequestId>599904C8-A3DA-4E5F-83B6-D5364E664247</RequestId>
</CreateTransitRouterRouteTableResponse>

JSON format

{
  "TransitRouterRouteTableId": "vtb-bp1xbcgpgcz9axl9m****",
  "RequestId": "599904C8-A3DA-4E5F-83B6-D5364E664247"
}

Error codes

HttpCode Error code Error message Description
400 DryRunOperation Request validation has been passed with DryRun flag set. The error message returned because the dry run request passes the precheck.

For a list of error codes, visit the API Error Center.