Creates a virtual border router (VBR) connection from an Enterprise Edition transit router.

Description

You can use the following methods to create a VBR connection from an Enterprise Edition transit router:

  • If an Enterprise Edition transit router is already created in the region where you want to create a VBR connection, specify VbrId and TransitRouterId.
  • If no Enterprise Edition transit router is created in the region where you want to create a VBR connection, specify VbrId, CenId, and RegionId. When you create a VBR connection, the system automatically creates an Enterprise Edition transit router in the specified region.

Limits

Enterprise Edition transit routers are supported only in specific regions. You can create a VBR connection only in these regions. For more information about the regions and zones that support Enterprise Edition transit routers, see Transit routers.

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 No CreateTransitRouterVbrAttachment

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

VbrId String Yes vbr-bp1svadp4lq38janc****

The ID of the VBR.

ClientToken String No 02fb3da4-130e-11e9-8e44-001****

The client token that is used to ensure the idempotence of the request.

You can use the client to generate a token, 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.

CenId String No cen-j3jzhw1zpau2km****

The ID of the Cloud Enterprise Network (CEN) instance.

TransitRouterId String No tr-bp1su1ytdxtataupl****

The ID of the Enterprise Edition transit router.

RegionId String No cn-hangzhou

The region ID of the VBR.

You can call the DescribeRegions operation to query region IDs.

TransitRouterAttachmentName String No testname

The name of the VBR connection.

The name must be 2 to 128 characters in length and can contain digits, underscores (_), and hyphens (-). It must start with a letter.

TransitRouterAttachmentDescription String No testdesc

The description of the VBR connection.

The description must be 2 to 256 characters in length. The description must start with a letter but cannot start with http:// or https://.

VbrOwnerId Long No 1688111111111111

The UID of the account to which the VBR belongs.

AutoPublishRouteEnabled Boolean No false

Specifies whether to enable the Enterprise Edition transit router to automatically advertise routes to the VBR. Valid values:

  • false: disables automatic route advertisement. This is the default value.
  • true: enables automatic route advertisement.
DryRun Boolean No false

Specifies whether to only precheck the request. Check items include permissions and the status of the specified instances. Valid values:

  • false (default): sends a normal request. If the request passes the precheck, the VBR connection is created.
  • true: sends a request for precheck only. No VBR connection is created after the request passes the precheck. If you select this option, the system checks whether the required parameters are set, and whether the request syntax is valid. If the request fails to pass the precheck, the system returns an error. If the request passes the precheck, the system returns the ID of the request.

Response parameters

Parameter Type Example Description
RequestId String C087A369-82B9-43EF-91F4-4B63A9C6E6B6

The ID of the request.

TransitRouterAttachmentId String tr-attach-ia340z7xis7t5s****

The ID of the VBR connection.

Examples

Sample requests

http(s)://[Endpoint]/?Action=CreateTransitRouterVbrAttachment
&VbrId=vbr-bp1svadp4lq38janc****
&<Common request parameters>

Sample success responses

XML format

<CreateTransitRouterVbrAttachmentResponse> 
  <TransitRouterAttachmentId>tr-attach-ia340z7xis7t5s****</TransitRouterAttachmentId>
  <RequestId>C087A369-82B9-43EF-91F4-4B63A9C6E6B6</RequestId>
</CreateTransitRouterVbrAttachmentResponse>

JSON format

{
  "TransitRouterAttachmentId": "tr-attach-ia340z7xis7t5s****",
  "RequestId": "C087A369-82B9-43EF-91F4-4B63A9C6E6B6"
}

Error codes

HttpCode Error code Error message Description
400 NoPermission.AliyunServiceRolePolicyForCEN You are not authorized to create the service linked role. Role Name: AliyunServiceRolePolicyForCEN. Service Name: cen.aliyuncs.com. Make sure that the user has been granted the ram:CreateServiceLinkedRole permission. The error message returned because you are unauthorized to create the service-linked role AliyunServiceRolePolicyForCEN for the service ServiceName:cen.aliyuncs.com. You must acquire the ram:CreateServiceLinkedRole permission before you can perform the operation.
400 OperationUnsupported.TransitRouterRegionId The specified TransitRouterRegion does not support the operation. The error message returned because the specified region does not support the operation.
400 InvalidCenId.NotFound CenId is not found. The error message returned because the specified CEN instance does not exist.

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