Disassociates a virtual border router (VBR) from an Express Connect circuit.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
RegionId String Yes cn-hangzhou

The region ID of the Express Connect circuit.

You can call the DescribeRegions operation to query the most recent region list.

VbrId String Yes vbr-bp16ksp61j7e0tkn*****

The ID of the VBR that you want to disassociate from the Express Connect circuit.

PhysicalConnectionId String Yes pc-bp1qrb3044eqixog****

The ID of the Express Connect circuit.

Action String Yes UnassociatePhysicalConnectionFromVirtualBorderRouter

The operation that you want to perform. Set the value to UnassociatePhysicalConnectionFromVirtualBorderRouter.

ClientToken String No 123e4567-e89b-12d3-a456-426655440000

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 ensure that the value is unique among all requests. The token can contain only ASCII characters.

Note If you do not specify this parameter, the system uses RequestId as ClientToken. RequestId may be different for each API request.

Response parameters

Parameter Type Example Description
RequestId String 980960B0-2969-40BF-8542-EBB34FD358AB

The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?RegionId=cn-hangzhou
&VbrId=vbr-bp16ksp61j7e0tkn*****
&PhysicalConnectionId=pc-bp1qrb3044eqixog****
&Action=UnassociatePhysicalConnectionFromVirtualBorderRouter
&ClientToken=123e4567-e89b-12d3-a456-426655440000
&Common request parameters

Sample success responses

XML format 

HTTP/1.1 200 OK
Content-Type:application/xml

<UnassociatePhysicalConnectionFromVirtualBorderRouterResponse>
    <RequestId>980960B0-2969-40BF-8542-EBB34FD358AB</RequestId>
</UnassociatePhysicalConnectionFromVirtualBorderRouterResponse>

JSON format 

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId" : "980960B0-2969-40BF-8542-EBB34FD358AB"
}

Error codes

HttpCode Error code Error message Description
400 PARAMETER_MUST_NOT_NULL The specified physical connection id or vbrId must not be null. The error message returned because the VbrId and PhysicalConnectionId parameters are not set.
400 PHYSICAL_NOT_ASSOCIATE_TO_VBR The specified PhysicalConnection have not associate to the vbr. The error message returned because no VBR is created for the Express Connect circuit.
400 ROUTER_INTERFACE_REFERED_BY_ROUTEENTRY The specified VlanInterface has been used by routeEntry. The error message returned because the VLAN interface is being used by a route entry.
400 InvalidStatus.NotAllowed Invalid virtual border router status. The error message returned because the status of the VBR does not support this operation.
400 PHYSICAL_NOT_ALLOW_ASSOCIATE_VBR The specified operation not allow. The error message returned because the Express Connect circuit is associated with a VBR and the operation cannot be performed.
404 InvalidVbrId.NotFound The specified VirutalBorderRouter does not exist in our records. The error message returned because the specified VBR does not exist. Check whether the VbrId parameter is set to a valid value.
404 InvalidVbrId.NotFound The specified VirutalBorderRouter or PhysicalConnection does not exist in our records. The error message returned because the VBR or the Express Connect circuit does not exist.

For a list of error codes, visit the API Error Center.