DissociateTransitRouterAttachmentFromRouteTable -

Usage notes

DissociateTransitRouterAttachmentFromRouteTable is an asynchronous operation. After you send a request, the system returns the request ID but the operation is still being performed in the system background. You can call ListTransitRouterRouteTableAssociations to query an associated forwarding correlation between a network instance connection and a route table.

If an associated forwarding correlation is in the Dissociating state, the associated forwarding correlation is being deleted. You can query the associated forwarding correlation but cannot perform other operations.
If an associated forwarding correlation cannot be found, the associated forwarding correlation is deleted.

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	Yes	DissociateTransitRouterAttachmentFromRouteTable	The operation that you want to perform. Set the value to DissociateTransitRouterAttachmentFromRouteTable.
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 the value, but you must make sure that it is unique among different requests. ClientToken can contain only ASCII characters. Note If you do not set this parameter, ClientToken is set to the value of RequestId. The value of RequestId may be different for each API request.
DryRun	Boolean	No	false	Specifies whether to perform a precheck to check information such as the permissions and instance status. Valid values: false (default): sends the request. If the request passes the precheck, the associated forwarding correlation is deleted. true: sends a request for precheck only. The associated forwarding correlation is not deleted after the request passes the precheck. If you use this value, the system checks the required parameters and the request syntax. If the request fails to pass the precheck, an error message is returned. If the request passes the check, 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=DissociateTransitRouterAttachmentFromRouteTable
&TransitRouterAttachmentId=tr-attach-nls9fzkfat8934****
&TransitRouterRouteTableId=vtb-bp1dudbh2d5na6b50****
&ClientToken=02fb3da4-130e-11e9-8e44-001****
&DryRun=false
&Common request parameters

Sample success responses

XML format

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

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

JSON format

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

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

Error codes


HttpCode	Error code	Error message	Description
400	IncorrectStatus.Status	RouteTableAssociation status is invalid.	The error message returned because the associated forwarding correlation is in an invalid state. Try again later.
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.