Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
Operation description
By invoking the CreateVpconnFromVbr operation, a partner can transform the routing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant's services.
Before you execute the transform procedure:
The partner must notify the tenant about the service upgrade in advance and ensure that the tenant has enabled outbound traffic billing. For information about how to enable outbound traffic billing, see Enable outbound traffic billing.
After the transform procedure is complete:
A shared port is added to the tenant's account. The tenant must invoke the ConfirmPhysicalConnection operation to accept the shared port.
After the tenant accepts the shared port, the partner must invoke the AttachVbrToVpconn operation to associate the VBR instance with the tenant's shared Express Connect circuits instance.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
vpc:CreateVpconnFromVbr |
create |
*VirtualBorderRouter
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| OrderMode |
string |
No |
The payer of the shared Express Connect circuits. Valid values:
Valid values:
|
PayByVirtualPhysicalConnectionOwner |
| VbrId |
string |
Yes |
The instance ID of the cross-account VBR. |
vbr-bp136flp1mf8mlq6r**** |
| Token |
string |
No |
The client token that is used to ensure the idempotence of the request. The client token must be unique among different requests. The maximum length is 64 ASCII characters. |
CBCE910E-D396-4944-8**** |
| DryRun |
boolean |
No |
Specifies whether to perform a dry run. Valid values:
|
false |
| RegionId |
string |
Yes |
The region ID of the shared Express Connect circuits. You can invoke the DescribeRegions operation to query the region ID. |
cn-hangzhou |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response parameters. |
||
| RequestId |
string |
The request ID. |
5356F028-0F5C-56FC-8574-897D24379041 |
| VirtualPhysicalConnection |
string |
The instance ID of the shared Express Connect circuits. |
pc-bp1mrgfbtmc9brre7**** |
Examples
Success response
JSON format
{
"RequestId": "5356F028-0F5C-56FC-8574-897D24379041",
"VirtualPhysicalConnection": "pc-bp1mrgfbtmc9brre7****"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | OperationFailed.TargetUserPconnTrafficNotEnable | The operation failed because of TargetUserPconnTrafficNotEnable. | The operation failed because the user does not have outbound traffic enabled. |
| 400 | ResourceNotEnough.Bandwidth | The specified resource of Bandwidth is not enough. | The specified resource of Bandwidth is insufficient. |
| 400 | OperationFailed.VbrBindedPconn | The operation is failed because of VbrBindedPconn. | A hosted connection is created for the VBR. |
| 400 | IllegalParam.Bandwidth | The param of Bandwidth [%s] is illegal. | The specified bandwidth value is invalid. |
| 400 | IncorrectStatus.VbrId | The status of %s is incorrect. | The status of the VBR is invalid. |
| 400 | ResourceNotFound.PhysicalConnectionId | PhysicalConnection is not found. | PhysicalConnectionId is set to an invalid value. |
| 400 | OperationFailed.VPconnCreated | The operation is failed because of VPconnCreated. | You cannot create an Express Connect circuit. |
| 400 | OperationFailed.BandwidthOrVlanIdEmpty | The operation is failed because of BandwidthOrVlanIdEmpty. | |
| 400 | ResourceNotFound.VirtualBorderRouter | The specified resource of %s is not found. | Virtual Border Router does not exist |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.