UnassociatePhysicalConnectionFromVirtualBorderRouter - Express Connect

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.

Debug

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:UnassociatePhysicalConnectionFromVirtualBorderRouter	update	PhysicalConnection acs:vpc:{#regionId}:{#accountId}:physicalconnection/{#PhysicalConnectionId} VirtualBorderRouter acs:vpc:{#regionId}:{#accountId}:virtualborderrouter/{#VirtualBorderRouterId}	none	none

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The region ID of the Express Connect circuit. You can call the DescribeRegions operation to query the most recent region list.	cn-hangzhou
VbrId	string	Yes	The ID of the VBR that you want to disassociate from the Express Connect circuit.	vbr-bp16ksp61j7e0tkn*****
PhysicalConnectionId	string	Yes	The ID of the Express Connect circuit.	pc-bp1qrb3044eqixog****
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 token can contain only ASCII characters. Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.	123e4567-e89b-12d3-a456-426655440000

Response parameters

Parameter	Type	Description	Example
	object	The request ID.
RequestId	string	The request ID.	980960B0-2969-40BF-8542-EBB34FD358AB

Examples

Sample success responses

JSONformat

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

Error codes

HTTP status code	Error code	Error message	Description
400	PARAMETER_MUST_NOT_NULL	The specified physical connection id or vbrId must not be null.	VbrId and PhysicalConnectionId are not specified.
400	PHYSICAL_NOT_ASSOCIATE_TO_VBR	The specified PhysicalConnection have not associate to the vbr.	No VBR is created for the Express Connect circuit.
400	ROUTER_INTERFACE_REFERED_BY_ROUTEENTRY	The specified VlanInterface has been used by routeEntry.	The VLAN interface is being used by a route entry.
400	InvalidStatus.NotAllowed	Invalid virtual border router status.	The current VBR status does not support this operation.
400	PHYSICAL_NOT_ALLOW_ASSOCIATE_VBR	The specified operation not allow.	The Express Connect circuit is associated with a VBR and the operation cannot be performed.
400	Forbidden.OperationNotAllowed	The caller must be PhysicalConnection or VirtualBorderRouter's owner.	-
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.
404	InvalidVbrId.NotFound	The specified VirutalBorderRouter or PhysicalConnection does not exist in our records.	The VBR or the Express Connect circuit does not exist.

For a list of error codes, visit the Service error codes.