Pushes an Express Connect circuit to another account by adding a shared port for the account.

Description

If an Express Connect partner has created a virtual border router (VBR) for a tenant before, the Express Connect partner can push the Express Connect circuit that is associated with the VBR to the tenant account by adding a shared port for the tenant account. The service of the tenant is not interrupted in this process.

Preparations:

Before the Express Connect partner performs the operation, the Express Connect partner must notify the tenant and request the tenant to enable outbound data transfer billing. For more information, see Enable outbound data transfer billing.

What to do next:

1. After the Express Connect partner performs the operation, a shared port is added for the tenant account. The tenant must call the ConfirmPhysicalConnection operation to accept the shared port.

2. Then, the Express Connect partner must call the AttachVbrToVpconn operation to associate the VBR with the newly added shared port that belongs to the tenant account.

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
Action String Yes CreateVpconnFromVbr

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

OrderMode String No PayByVirtualPhysicalConnectionOwner

Specifies the party that must pay for the shared Express Connect circuit. Valid values:

  • PayByPhysicalConnectionOwner: If you set the value to PayByPhysicalConnectionOwner, the Express Connect partner must pay for the shared Express Connect circuit.
  • PayByVirtualPhysicalConnectionOwner: If you set the value to PayByVirtualPhysicalConnectionOwner, the tenant must pay for the shared Express Connect circuit.
VbrId String Yes vbr-bp136flp1mf8mlq6r****

The ID of the associated VBR.

Token String No CBCE910E-D396-4944-8****

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 it is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length.

DryRun Boolean No false

Specifies whether to only precheck the request. Valid values:

  • true: checks the API request. If the request passes the precheck, the operation is not performed. Check items include the request format, instance status, and whether the required parameters are specified. If the request fails the precheck, the system returns an error. If the request passes the precheck, the system returns the ID of the request.
  • false (default): sends the API request. If the request passes the precheck, the operation is performed.
RegionId String Yes cn-hangzhou

The region ID of the shared Express Connect circuit.

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

Response parameters

Parameter Type Example Description
RequestId String 5356F028-0F5C-56FC-8574-897D24379041

The ID of the request.

VirtualPhysicalConnection String pc-bp1mrgfbtmc9brre7****

The ID of the shared Express Connect circuit.

Examples

Sample requests

http(s)://[Endpoint]/?Action=CreateVpconnFromVbr
&OrderMode=PayByVirtualPhysicalConnectionOwner
&VbrId=vbr-bp136flp1mf8mlq6r****
&DryRun=false
&RegionId=cn-hangzhou
&<Common request parameters>

Sample success responses

XML format 

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

<CreateVpconnFromVbrResponse>
    <RequestId>5356F028-0F5C-56FC-8574-897D24379041</RequestId>
    <VirtualPhysicalConnection>pc-bp1mrgfbtmc9brre7****</VirtualPhysicalConnection>
</CreateVpconnFromVbrResponse>

JSON format 

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

{
  "RequestId" : "5356F028-0F5C-56FC-8574-897D24379041",
  "VirtualPhysicalConnection" : "pc-bp1mrgfbtmc9brre7****"
}

Error codes

HttpCode Error code Error message Description
400 OperationFailed.TargetUserPconnTrafficNotEnable The operation failed because of TargetUserPconnTrafficNotEnable. The error message returned because outbound data transfer billing is disabled.
400 IllegalParam.Bandwidth The param of Bandwidth [%s] is illegal. The error message returned because the specified bandwidth limit is invalid.
400 IncorrectStatus.VbrId The status of %s is incorrect. The error message returned because you cannot perform the operation when the VBR is in the current state.
400 ResourceNotFound.PhysicalConnectionId PhysicalConnection is not found. The error message returned because PhysicalConnectionId is invalid.

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