Deletes a transit router.
Operation description
DeleteTransitRouter is an asynchronous operation. After you send a request, the request ID is returned but the operation is still being performed in the system background. You can call ListTransitRouters to query the status of a transit router.
- If a transit router is in the Deleting state, the transit router is being deleted. In this case, you can query the transit router but cannot perform other operations.
- If a transit router cannot be found, the transit router is deleted.
Prerequisites
Before you delete a transit router, make sure that the following prerequisites are met:
-
No network instance connections are created on the transit router.
- For more information about how to delete a virtual private cloud (VPC) connection, see DeleteTransitRouterVpcAttachment .
- For more information about how to delete a virtual border router (VBR) connection, see DeleteTransitRouterVbrAttachment .
- For more information about how to delete a Cloud Connect Network (CCN) connection, see DetachCenChildInstance .
- For more information about how to delete a VPN connection, see DeleteTransitRouterVpnAttachment .
- For more information about how to delete an inter-region connection, see DeleteTransitRouterPeerAttachment .
-
No custom route tables are created on the transit router. For more information about how to delete a custom route table, see DeleteTransitRouterRouteTable .
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| cen:DeleteTransitRouter | delete | *TransitRouter acs:cen:*:{#accountId}:centransitrouter/{#centransitrouterId} |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| ClientToken | string | No | 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.
| 02fb3da4-130e-11e9-8e44-001**** |
| DryRun | boolean | No | Specifies whether only to precheck the request. Check items include permissions and the status of the transit router. Valid values:
| false |
| TransitRouterId | string | Yes | The ID of the transit router. | tr-uf654ttymmljlvh2x**** |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "6DE3EE92-39C8-4BBD-A3AD-F568D74741BB"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | OperationFailed.DeleteTransitRouter | Operation failed because TransitRouterRouteTable or TransitRouterRouteEntry or BandwidthTransitRegion exists. | The error message returned because this operation is not supported when a custom route or a custom route table exists, or bandwidth multiplexing is enabled. Delete the custom route table and route, disable bandwidth multiplexing, and then try again. |
| 400 | IncorrectStatus.TransitRouterInstance | The status of TransitRouter is incorrect. | The error message returned because the transit router is in an invalid state. |
| 400 | OperationFailed.CCNAttached | Can not delete transit router because CCN still attached. | The error message returned because the transit router cannot be deleted when it is connected to a CCN instance. |
| 400 | OperationFailed.BandwidthLimitExist | Operation is invalid because a bandwidth limit exist. | Please delete all cross region bandwidth limits associated with current TR and try again. |
| 400 | IncorrectStatus.CenInstance | The status of CenInstance is incorrect. | The error message returned because the status of the CEN instance to which the transit router is connected does not support this operation. Wait until the CEN instance is in a stable state. |
| 400 | OperationFailed.TrafficMarkingPolicyExist | Operation is invalid because traffic marking policy exists. | The error message returned because the transit router is associated with a traffic marking policy. Disassociate the transit router from the traffic marking policy before you delete the transit router. |
| 400 | OperationFailed.MulticastDomainExist | Operation is invalid because multicast domain exists. | The error message returned because the transit router is associated with a multicast domain. Disassociate the transit router from the multicast domain before you delete the transit router. |
| 400 | OperationFailed.PrefixListExist | Operation is invalid because prefix list exists. | The error message returned because this operation is not supported when a prefix list exists. Delete the prefix list and try again. |
| 400 | OperationFailed.TrafficQosPolicyExist | Operation is invalid because traffic qos policy exists. | The error message returned because this operation is not supported when a QoS policy exists. Delete the QoS policy and try again. |
| 400 | OperationFailed.CloudRouteExist | Operation is invalid because cloud route exists. | - |
| 400 | OperationFailed.FlowLogExistOrNisOpened | Operation failed because FlowLog exists or Nis opened. | The error message returned because this operation is not supported when a flow log exists or the NIS service is activated. |
| 400 | OperationFailed.AggregationRouteExist | Operation failed because TransitRouterRouteAggregation exists. | Operation failed because TransitRouterRouteAggregation exists. |
| 400 | InvalidOperation.BondVbrExist | The operation failed due to BondVbr exists. | The operation failed because the BondVbr exists. |
| 400 | InvalidTransitRouterInstance.NotFound | The Transit Router instance is not found. | The Transit Router instance is not found. |
| 400 | OperationFailed.FlowLogExist | Flow log configurations exist. Delete the flow log configurations and retry the operation. | Flow log configurations exist. Delete the flow log configurations and retry the operation. |
| 400 | InvalidParameter | Invalid parameter. | The error message returned because the parameter is set to an invalid value. |
| 400 | Unauthorized | The AccessKeyId is unauthorized. | The error message returned because you do not have the permissions to perform this operation. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2024-10-21 | The Error code has changed | View Change Details |
| 2024-09-18 | The Error code has changed | View Change Details |
| 2024-07-10 | The Error code has changed | View Change Details |
| 2024-05-22 | The Error code has changed | View Change Details |
| 2022-12-22 | The Error code has changed | View Change Details |