Disassociates a Virtual Border Router (VBR) from a physical connection.
Debug
Use OpenAPI Explorer to perform debug operations and generate SDK code examples.
Request parameters
| Parameter | Type | Required? | Example value | Description |
|---|---|---|---|---|
| Action | String | Yes | UnassociatePhysicalConnectionFromVirtualBorderRouter | The name of this action. Value: UnassociatePhysicalConnectionFromVirtualBorderRouter |
| PhysicalConnectionId | String | Yes | pc-bp1qrb3044eqixog**** | The ID of the physical connection. |
| RegionId | String | Yes | cn-hangzhou | The region ID of the physical connection. |
| VbrId | String | Yes | vbr-bp16ksp61j7e0tkn***** | The VLAN ID of the VBR. Value range: 1 to 2999.
Note This parameter can only be specified by the owner of the physical connection. The VLAN IDs of two VBRs associated with the same physical connection must be different.
|
| ClientToken | String | No | longtel001 | Optional. The leased line code provided by the service provider for the physical connection.
Note This parameter can only be specified by the owner of the physical connection.
|
Response parameters
| Parameter | Type | Example value | Description |
|---|---|---|---|
| RequestId | String | 980960B0-2969-40BF-8542-EBB34FD358AB | The request ID. |
Examples
Request example
http(s)://[Endpoint]/? Action=UnassociatePhysicalConnectionFromVirtualBorderRouter
&PhysicalConnectionId=pc-bp1qrb3044eqixog****
&RegionId=cn-hangzhou
&VbrId=vbr-bp16ksp61j7e0tkn*****
&<CommonParameters>
Response examples
XML format
<UnassociatePhysicalConnectionFromVirtualBorderRouterResponse>
<RequestId>980960B0-2969-40BF-8542-EBB34FD358AB</RequestId>
</UnassociatePhysicalConnectionFromVirtualBorderRouterResponse>JSON format
{
"RequestId":"980960B0-2969-40BF-8542-EBB34FD358AB"
}Errors
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 404 | InvalidVbrId.NotFound | The specified VirutalBorderRouter does not exist in our records. | The specified VBR does not exist. |
| 404 | InvalidVbrId.NotFound | The specified VirutalBorderRouter or PhysicalConnection does not exist in our records. | The specified VBR or physical connection does not exist. |
| 400 | PARAMETER_MUST_NOT_NULL | The specified physical connection id or vbrId must not be null. | The VbrId parameter and the PhysicalConnectionId parameter must be specified. |
| 400 | PHYSICAL_NOT_ASSOCIATE_TO_VBR | The specified PhysicalConnection have not associate to the vbr. | No VBR is created for the specified physical connection. |
| 400 | ROUTER_INTERFACE_REFERED_BY_ROUTEENTRY | The specified VlanInterface has been used by routeEntry. | The specified VLAN interface is already used in a route entry. |
| 400 | InvalidStatus.NotAllowed | Invalid virtual border router status. | The status of the VBR does not permit this operation. |
| 400 | PHYSICAL_NOT_ALLOW_ASSOCIATE_VBR | The specified operation not allow. | The operation failed because the physical connection is associated with VBRs. |
For a list of error codes, visit the API Error Center.