Calls the DeleteTransitRouterPeerAttachment operation to delete an inter-region connection from an Enterprise Edition transit router.
Operation description
The DeleteTransitRouterPeerAttachment operation is asynchronous. After you send a request, the system returns a RequestId but the inter-region connection is not immediately deleted. The deletion task continues to run in the background. You can call the ListTransitRouterPeerAttachments operation to query the status of the inter-region connection.
If the inter-region connection is in the Detaching state, the inter-region connection is being deleted. In this state, you can only query the inter-region connection but cannot perform other operations on it.
If the specified inter-region connection cannot be found, the inter-region connection is deleted.
When calling the DeleteTransitRouterPeerAttachment operation, make sure that the parameter values you specify are correct. If you specify incorrect parameter values, the system still returns a RequestId but does not delete the inter-region connection from the Enterprise Edition transit router.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
cen:DeleteTransitRouterPeerAttachment |
delete |
*TransitRouterPeerAttachment
|
None | 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 token, but you must make sure that the token is unique among different requests. The client token can contain only ASCII characters. Note
If you do not specify this parameter, the system automatically uses the RequestId of the API request as the ClientToken. The RequestId may be different for each API request. |
02fb3da4-130e-11e9-8e44-001**** |
| TransitRouterAttachmentId |
string |
Yes |
The ID of the inter-region connection. |
tr-attach-gyjhtx9sjsxhm6**** |
| DryRun |
boolean |
No |
Specifies whether to perform a dry run for this deletion request, including permission and instance status checks. Valid values:
|
false |
| Force |
boolean |
No |
Specifies whether to force delete the inter-region connection. Valid values:
|
false |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
|||
| RequestId |
string |
The request ID. |
A01FEDD7-7D69-4EB3-996D-CF79F6F885CA |
Examples
Success response
JSON format
{
"RequestId": "A01FEDD7-7D69-4EB3-996D-CF79F6F885CA"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | OperationFailed.RouteTablePropagationExist | Operation failed because You are not allowed to delete TransitAttachment with TransitRouter RouteTable Associated. | The error message returned because the transit route attachment (TransitAttachment) is associated with a route table. Disassociate the attachment from the route table and try again. |
| 400 | OperationFailed.RouteEntryExist | Operation failed because the TransitRouterAttachment exists in RouteTable. | |
| 400 | OperationFailed.RouteTableAssociationExist | Operation failed because TransitRouterRouteTable exists | The error message returned because you cannot perform the operation when the connection is associated with a route table. |
| 400 | OperationFailed.TrafficQosExist | Operation failed because TrafficQos exists | The error message returned because a QoS policy exists. Delete the QoS policy and try again. |
| 400 | InvalidValue.PrefixlistCidr | Invalid cidr exist in the specified prefixlist. | The error message returned because the specified prefix list contains an invalid CIDR block. |
| 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.NotSupportForceDelete | Not support force delete attachment. | The error message returned because the specified resource cannot be forcefully deleted. |
| 400 | InvalidTransitRouterAttachmentId.NotFound | TransitRouterAttachmentId is not found. | The error message returned because the ID of the network instance does not exist. |
| 400 | OperationUnsupported.TransitRouterType | The operation is not supported because of the wrong transitRouter type. | The error message returned because this operation is not supported by the specified type of transit router. |
| 400 | OperationFailed.MulticastGroupExist | Operation is failed because attachment exists in multicast groups. | The error message returned because the specified attachment is in a multicast group. Remove the attachment from the multicast group and try again. |
| 400 | OperationUnsupported.TransitRouterAttachment | The specified TransitRouterAttachment has configured TransitRegion. Please remove the configuration first. | The error message returned because bandwidth multiplexing is enabled. Disable bandwidth multiplexing and try again. |
| 400 | OperationFailed.PrefixListExist | Operation failed because PrefixList exists. | The error message returned because a prefix list exists. |
| 400 | OperationFailed.InterRegionCloudRouteEntryExist | Operation failed because inter region cloud route associated with specified attachment exist. | Inter region cloud route associated with specified attachment exist. |
| 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. |
| 400 | InvalidParameter.TransitRouterAttachmentId | The specified parameter TransitRouterAttachmentId is invalid. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.