Panggil operasi DeleteTransitRouterPeerAttachment untuk menghapus koneksi antar-wilayah dari router transit edisi perusahaan.
Deskripsi operasi
Operasi DeleteTransitRouterPeerAttachment bersifat asinkron. Setelah Anda mengirim permintaan, sistem akan mengembalikan RequestId, tetapi koneksi antar-wilayah tidak langsung dihapus. Sistem akan menghapus koneksi tersebut di latar belakang. Anda dapat memanggil operasi ListTransitRouterPeerAttachments untuk memeriksa status koneksi antar-wilayah.
Jika koneksi antar-wilayah berada dalam status Detaching, koneksi tersebut sedang dalam proses penghapusan. Dalam status ini, Anda hanya dapat memeriksa koneksi tersebut dan tidak dapat melakukan operasi lainnya.
Jika koneksi antar-wilayah yang ditentukan tidak ditemukan, berarti koneksi tersebut telah dihapus.
Pastikan Anda menentukan nilai parameter yang valid saat memanggil operasi DeleteTransitRouterPeerAttachment. Jika nilai parameter yang ditentukan tidak valid, sistem akan mengembalikan RequestId tetapi tidak menghapus koneksi antar-wilayah.
Coba sekarang
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
cen:DeleteTransitRouterPeerAttachment |
delete |
*TransitRouterPeerAttachment
|
None | None |
Parameter permintaan
|
Parameter |
Type |
Required |
Description |
Example |
| ClientToken |
string |
No |
Token klien yang digunakan untuk memastikan idempotensi permintaan. Buat token dari klien Anda untuk memastikan bahwa token tersebut unik di antara permintaan yang berbeda. Parameter ClientToken hanya boleh berisi karakter ASCII. Catatan
Jika Anda tidak menentukan parameter ini, sistem akan menggunakan RequestId dari permintaan sebagai ClientToken. RequestId setiap permintaan berbeda-beda. |
02fb3da4-130e-11e9-8e44-001**** |
| TransitRouterAttachmentId |
string |
Yes |
ID koneksi antar-wilayah. |
tr-attach-gyjhtx9sjsxhm6**** |
| DryRun |
boolean |
No |
Menentukan apakah akan melakukan dry run. Dry run memeriksa izin dan status instans. Nilai yang valid:
|
false |
| Force |
boolean |
No |
Menentukan apakah akan menghapus koneksi antar-wilayah secara paksa. Nilai yang valid:
|
false |
Elemen respons
|
Element |
Type |
Description |
Example |
|
object |
|||
| RequestId |
string |
ID permintaan. |
A01FEDD7-7D69-4EB3-996D-CF79F6F885CA |
Contoh
Respons sukses
JSONformat
{
"RequestId": "A01FEDD7-7D69-4EB3-996D-CF79F6F885CA"
}
Kode kesalahan
|
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. |
Lihat Error Codes untuk daftar lengkap.
Catatan rilis
Lihat Release Notes untuk daftar lengkap.