Associates a virtual border router (VBR) with a specified Express Connect circuit.
Debugging
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:AssociatePhysicalConnectionToVirtualBorderRouter | update |
|
| 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. | vbr-bp186tnz6rijyhj****** |
PhysicalConnectionId | string | Yes | The ID of the Express Connect circuit. | pc-bp1qrb3044eqixog**** |
VlanId | string | Yes | The VLAN ID of the VBR. Valid values: 0 to 2999. Note
Only the Express Connect circuit owner can specify this parameter. Two VBRs associated with the same Express Connect circuit cannot use the same VLAN ID.
| 123 |
CircuitCode | string | No | The circuit code of the Express Connect circuit. The circuit code is provided by the connectivity provider. Note
Only the Express Connect circuit owner can specify this parameter.
| longtel001 |
LocalGatewayIp | string | No | The IP address of the gateway device on the Alibaba Cloud side. | 192.168.XX.XX |
PeerGatewayIp | string | No | The IP address of the gateway device on the user side.
| 192.168.XX.XX |
PeeringSubnetMask | string | No | The subnet mask of the IP addresses of the VBR and the gateway device in the data center. The two IP addresses must fall within the same subnet. | 255.255.255.0 |
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 and cannot exceed 64 characters in length. 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 |
LocalIpv6GatewayIp | string | No | The IPv6 address of the gateway device on the Alibaba Cloud side. | 2001:XXXX:3c4d:0015:0000:0000:0000:1a2b |
PeerIpv6GatewayIp | string | No | The IPv6 address of the gateway device in the data center.
| 2001:XXXX:4:4:4:4:4:4 |
PeeringIpv6SubnetMask | string | No | The subnet mask of the IPv6 addresses of the gateway devices on the user side and Alibaba Cloud side. The two IPv6 addresses must fall within the same subnet. | 2408:4004:cc:400::/56 |
EnableIpv6 | string | No | Specifies whether to enable IPv6. Valid values:
| false |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "980960B0-2969-40BF-8542-EBB34FD358AB"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | InvalidOperation.RouterInterfaceNotDeleted | The specified VirutalBorderRouter still has routerInterface. | The VBR is associated with a router interface. |
400 | InvalidOperation.OperationNotAllowedInState | The specified VirutalBorderRouter is in invalid state. | The specified VBR is in an invalid state. Check the status of the VBR. |
400 | InvalidStatus.NotAllowed | Invalid virtual border router status. | The current VBR status does not support this operation. |
400 | InvalidPhysicalConnectionId.NotFound | The specified PhysicalConnectionId is not found. | The specified Express Connect circuit ID does not exist. |
400 | InvalidVlanId.Used | The specified VlanId has been used. | The VLAN ID is in use. |
400 | MissingParameter | The input parameter 'PhysicalConnectionId' that is mandatory for processing this request is not supplied. | PhysicalConnectionId is not specified. |
400 | InvalidPhysicalConnectionId.NotEnabled | The specified PhysicalConnectionId is not in Enabled state. | The Express Connect circuit is in an invalid state. Check the Express Connect circuit and try again. |
400 | MissingParameter | The input parameter 'VlanId' that is mandatory for processing this request is not supplied. | VlanId is not specified. |
400 | InvalidVlanId.Malformed | The specified VlanId is not valid. | VlanId is set to an invalid value. |
400 | InvalidCircuitCode.Malformed | The specified CircuitCode is not valid. | CircuitCode is set to an invalid value. |
400 | MissingParameter | The input parameter 'LocalGatewayIp' that is mandatory for processing this request is not supplied. | LocalGatewayIp is not specified. |
400 | InvalidLocalGatewayIp.Malformed | The specified LocalGatewayIp is not valid. | The IP address of the local gateway is invalid. |
400 | MissingParameter | The input parameter 'PeerGatewayIp' that is mandatory for processing this request is not supplied. | PeerGatewayIp is not specified. |
400 | InvalidPeerGatewayIp.Malformed | The specified PeerGatewayIp is not valid. | PeerGatewayIp is set to an invalid value. |
400 | MissingParameter | The input parameter 'PeeringSubnetMask' that is mandatory for processing this request is not supplied. | PeeringSubnetMask is not specified. |
400 | InvalidPeeringSubnetMask.Malformed | The specified PeeringSubnetMask is not valid. | PeeringSubnetMask is set to an invalid value. |
400 | InvalidName.Malformed | The specified ?Name? is not valid. | The error message returned because the name format is invalid. |
400 | InvalidDescription.Malformed | The specifid ?Description? is not valid. | The error message returned because the specified resource description is invalid. The description must be 2 to 256 characters in length and cannot start with http:// or https://. |
400 | QuotaExceeded.vbrPerpConn | Virtual boarder router per PhysicalConnection quota exceed. | The number of VBRs of each Express Connect circuit has reached the upper limit. Reduce the number of VBRs and try again. |
400 | EXCEED_ASSOCIATE_MAX_NUM | assocaite virtual boarder num too many. | The number of associated VBRs has reached the upper limit. |
400 | InvalidIP.Malformed | Ip malformed. | The format of the IP address is invalid. |
400 | MissingParameter | LocalGatewayIp, peerGatewayIp and peeringSubnetMask must not be null. | The following parameters are required but not set: LocalGatewayIp, peerGatewayIp, and peeringSubnetMask. |
400 | InvalidIp.NotSameSubnet | Local gateway ip and peer gateway ip are not in the same subnet. | The IP addresses of the local gateway and the peer gateway do not fall within the same subnet. |
400 | InvalidStatus.StatusNotEnabled | The physical connection status is invalid. | The status of the Express Connect circuit does not support this operation. Check the status of the Express Connect circuit. |
400 | InvalidParams.AlreadyExists | physical connection has already associated with vbr. | - |
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. | - |
400 | Forbidden.NotSameAccessDevice | Vbr and physicalConnection are not on the same accessDevice. | The VBR and Express Connect circuit do not belong to the same device. |
400 | Duplicated.LocalGatewayIp | Vbr has conflict local gateway ip. | - |
400 | OperationFailed.VlanIdInUse | Operation failed because vlanId is in use. | The VLAN ID is already used. |
400 | OperationFailed.PconnTrafficNotEnable | The operation is failed because of PconnTrafficNotEnable. | Billing for outbound data transfer is disabled. |
400 | DuplicatedParam.LocalGatewayIp | Duplicated LocalGatewayIp values. | The local IP address already exists. |
400 | DuplicatedParam.PeerGatewayIp | Duplicated PeerGatewayIp values. | The peer IP address already exists. |
400 | DuplicatedParam.LocalIpv6GatewayIp | Duplicated LocalIpv6GatewayIp values. | The local IP address already exists. |
400 | DuplicatedParam.PeerIpv6GatewayIp | Duplicated PeerIpv6GatewayIp values. | The peer IP address already exists. |
400 | EcPconnVbrMustContainsAll | In the single VBR with multiple Pconn scene, all Pconn must be associated with the same Qos. | In a single VBR and multiple Pconn scenarios, all Pconn must be bound to a QoS policy. |
400 | IllegalParam.LocalGatewayIpAndMask | The LocalGatewayIpAndMask value is invalid. | The error message returned because the IP address of the local gateway and the subnet mask are invalid. Specify a valid IP address and subnet mask and try again. |
403 | Forbidden.OperationNotAllowedByUser | The caller is not allowed to delete the specified VirtualBorderRouter. | You are not allowed to delete the VBR. |
403 | Forbidden.MultiVlanRi | Multiple vlan router interfaces are found. | Multiple VLAN router interfaces exist. |
403 | Forbidden.NoRiFound | No vlan router interfaces are found. | No VLAN router interface is available. |
403 | Forbidden.LocalGatewayIpNotAllowedByCaller | The caller is not allowed to specify the LocalGatewayIp parameter. | You are not allowed to specify LocalGatewayIp. |
403 | Forbidden.PeerGatewayIpNotAllowedByCaller | The caller is not allowed to specify the PeerGatewayIp parameter. | You do not have permissions to set the PeerGatewayIp parameter. |
403 | Forbidden.PeeringSubnetMaskNotAllowedByCaller | The caller is not allowed to specify the PeeringSubnetMask parameter. | You are not allowed to specify PeeringSubnetMask. |
403 | Forbidden.NameNotAllowedByCaller | The caller is not allowed to specify the Name parameter. | You do not have the permissions to set the Name parameter. |
403 | Forbidden.DescriptionNotAllowedByCaller | The caller is not allowed to specify the Description parameter. | You are not allowed to set Description. |
404 | InvalidInstanceId.NotFound | The specified Instance does not exist in the specified region. | The instance does not exist in the region. |
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 | InvalidRegionId.NotFound | The specified RegionId is not found. | The specified region ID is invalid. Check whether the service is available in the specified region. |
404 | InvalidVbrOwnerId.NotFound | The specified VbrOwnerId is not valid. | VbrOwnerId is set to an invalid value. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-06-28 | The Error code has changed | View Change Details |
2024-02-01 | API Description Update. The Error code has changed | View Change Details |
2023-04-10 | The Error code has changed | View Change Details |