Deletes a virtual border router (VBR).
Operation description
Before you call this operation, take note of the following limits:
- Before you delete a VBR, you must delete all router interfaces of the VBR.
- You can delete only a VBR in the unconfirmed, active, or terminated state.
- The owner of an Express Connect circuit can delete a VBR that belongs to another account only if the VBR is in the unconfirmed state.
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 Resources
is 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 |
---|---|---|---|---|
vpc:DeleteVirtualBorderRouter | delete | *VirtualBorderRouter acs:vpc:{#regionId}:{#accountId}:virtualborderrouter/{#VirtualBorderRouterId} |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | Yes | The region ID of the VBR. You can call the DescribeRegions operation to query the most recent region list. | cn-shanghai |
VbrId | string | Yes | The ID of the VBR. | vbr-bp12mw1f8k3jgygk9**** |
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. The token can contain only ASCII characters and cannot exceed 64 characters in length. | 02fb3da4-130e-11e9-8e44-0016e04115b |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "0ED8D006-F706-4D23-88ED-E11ED28DCAC0"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | InvalidOperation.RouterInterfaceNotDeleted | The specified VirutalBorderRouter still has routerInterface. | The VBR is associated with a router interface. |
400 | InvalidOperation.OperationNotAllowedInState | The specified VirutalBorderRouter is in invalid state. | The specified VBR is in an invalid state. Check the status of the VBR. |
400 | InvalidStatus.NotAllowed | The virtual border has been associated by physicalConnection. | The VBR is associated with an Express Connect circuit. |
400 | DependencyViolation.RouterInterfaceReferedByRouteEntry | The specified VirutalBorderRouter is refered by routeEntry. | The VBR is already used. |
400 | DependencyViolation.BgpGroup | bgp group exists, cannot delete vbr. | The VBR is associated with a BGP group and cannot be deleted. |
400 | DependencyViolation.Nqa | nqa exists, cannot delete vbr. | You cannot delete the VBR because nqa exists. |
400 | DependencyViolation.BgpNetwork | bgp network exists, cannot delete vbr. | You cannot delete the VBR because the VBR has advertised BGP CIDR blocks. |
400 | OperationUnsupported.VBRAttachedCen | Operation failed because the VBR is attached to CEN. | - |
403 | Forbidden.OperationDeleteNotAllowedByUser | The caller is not allowed to delete the specified VirtualBorderRouter. | The caller is not allowed to delete the specified VirtualBorderRouter. |
403 | Forbidden.MultiVlanRi | Multiple vlan router interfaces are found. | Multiple VLAN router interfaces exist. |
403 | Forbidden.NoRiFound | No vlan router interfaces are found. | No VLAN router interface is available. |
404 | InvalidRegionId.NotFound | The RegionId provided does not exist in our records. | The RegionId parameter is set to an invalid value. Specify a valid value and try again. |
404 | InvalidVbrId.NotFound | The specified VirutalBorderRouter does not exist in our records. | The VBR does not exist. Check the VBR ID. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-05-08 | API Description Update. The Error code has changed | View Change Details |