Creates an associated forwarding correlation.

Description

After you establish a network instance connection, you can create an associated forwarding correlation to associate the network instance connection with a route table. Then, the network instance connection can forward network traffic based on the associated route table.

Limits

Only Enterprise Edition transit routers support associated forwarding correlations. 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 AssociateTransitRouterAttachmentWithRouteTable

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

TransitRouterAttachmentId String Yes tr-attach-nls9fzkfat8934****

The ID of the network instance connection.

TransitRouterRouteTableId String Yes vtb-bp1dudbh2d5na6b50****

The ID of the route table 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.

DryRun Boolean No false

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

  • false (default): sends a normal request. If the request passes the precheck, the associated forwarding correlation is created.
  • true: sends a request for precheck only. The associated forwarding correlation is not 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 4EC47282-1B74-4534-BD0E-403F3EE64CAF

The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?Action=AssociateTransitRouterAttachmentWithRouteTable
&TransitRouterAttachmentId=tr-attach-nls9fzkfat8934****
&TransitRouterRouteTableId=vtb-bp1dudbh2d5na6b50****
&<Common request parameters>

Sample success responses

XML format

<AssociateTransitRouterAttachmentWithRouteTableResponse> 
  <RequestId>4EC47282-1B74-4534-BD0E-403F3EE64CAF</RequestId>
</AssociateTransitRouterAttachmentWithRouteTableResponse>

JSON format

{
    "RequestId":"4EC47282-1B74-4534-BD0E-403F3EE64CAF"
    }

Error codes

HttpCode Error code Error message Description
400 AssociationExist.TransitRouterTable The specified association already exists. The error message returned because the specified route table is already associated with an associated forwarding correlation.
404 InvalidRouteTableId.NotFound The specified RouteTableId is not found. The error message returned because the specified route table ID does not exist.
404 InvalidAttachmentId.NotFound The specified AttachmentId is not found. The error message returned because the specified network instance connection ID does not exist.

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