Deletes a virtual border router (VBR) connection for an Enterprise Edition transit router.

Usage notes

DeleteTransitRouterVbrAttachment 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 ListTransitRouterVbrAttachments to query the status of VBR connection.

  • If a VBR connection is in the Detaching state, the VBR connection is being deleted. You can query the VBR connection but cannot perform other operations.
  • If a VBR connection cannot be found, the VBR connection is deleted.

Prerequisites

Before you delete a VBR connection for an Enterprise Edition transit router, make sure that the following requirements are met:

  • No associated forwarding correlation is established between the VBR connection and the route tables of the Enterprise Edition transit router. For more information about how to delete an associated forwarding correlation, see DissociateTransitRouterAttachmentFromRouteTable.
  • No route learning correlation is established between the VBR connection and the route tables of the Enterprise Edition transit router. For more information about how to delete a route learning correlation, see DisableTransitRouterRouteTablePropagation.
  • The route tables of the Enterprise Edition transit router do not contain a custom route entry whose next hop is the network instance connection. For more information about how to delete custom route entries, see DeleteTransitRouterRouteEntry.
  • The route tables of the Enterprise Edition transit router do not contain a route whose next hop is the VBR connection and that is generated from a prefix list. You can delete such routes by disassociating the route table from the prefix list. For more information, see DeleteTransitRouterPrefixListAssociation.

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 DeleteTransitRouterVbrAttachment

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

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 of each API request may be different.
TransitRouterAttachmentId String Yes tr-attach-9nlnjv7by7n7a****

The ID of the VBR connection.

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 VBR connection is deleted.
  • true: sends a request for precheck only. The VBR connection 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 3EDA94DE-0AE5-41FC-A91E-7170E408E0FD

The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?Action=DeleteTransitRouterVbrAttachment
&ClientToken=02fb3da4-130e-11e9-8e44-001****
&TransitRouterAttachmentId=tr-attach-9nlnjv7by7n7a****
&DryRun=false
&Common request parameters

Sample success responses

XML format 

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

<DeleteTransitRouterVbrAttachmentResponse> 
<RequestId>3EDA94DE-0AE5-41FC-A91E-7170E408E0FD</RequestId>
</DeleteTransitRouterVbrAttachmentResponse>

JSON format 

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

{
  "RequestId" : "3EDA94DE-0AE5-41FC-A91E-7170E408E0FD"
}

Error codes

HttpCode Error codes Error message Description
400 OperationFailed.RouteTableAssociationExist Operation failed because TransitRouterRouteTable exists The error message returned because you cannot perform the operation when an associated forwarding correlation is configured.
400 OperationFailed.RouteEntryExist Operation failed because the TransitRouterAttachment exists in RouteTable. The error message returned because you cannot perform the operation when the specified inter-region connection is specified as the next hop of one or more routes in the route table.

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