All Products
Search
Document Center

Virtual Private Cloud:CreateVbrHa

Last Updated:Mar 04, 2024

Creates a virtual border router (VBR) failover group.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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.
OperationAccess levelResource typeCondition keyAssociated operation
vpc:CreateVbrHaWrite
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
DescriptionstringNo

The description of the VBR failover group.

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

VBRHa
NamestringNo

The name of the VBR failover group.

VBRHa
ClientTokenstringNo

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.
CBCE910E-D396-4944-8****
DryRunbooleanNo

Specifies whether to perform only a dry run, without performing the actual request. Valid values: Valid Values:

  • true: performs only a dry run. The system checks the request for potential issues, including missing parameter values, incorrect request syntax, and instance status. If the request fails the dry run, an error message is returned. If the request passes the dry run, DRYRUN.SUCCESS is returned.
  • false (default): performs a dry run and performs the actual request. If the request passes the dry run, the operation is performed.
false
VbrIdstringYes

The ID of the VBR.

vbr-bp1jcg5cmxjbl9xgc****
PeerVbrIdstringYes

The ID of the other VBR in the VBR failover group.

vbr-bp12mw1f8k3jgygk9****
RegionIdstringYes

The ID of the region in which the VBR is deployed.

cn-hangzhou

Response parameters

ParameterTypeDescriptionExample
object
VbrHaIdstring

The ID of the VBR failover group.

vbrha-sa1sxheuxtd98****
RequestIdstring

The request ID.

4EC47282-1B74-4534-BD0E-403F3EE64CAF

Examples

Sample success responses

JSONformat

{
  "VbrHaId": "vbrha-sa1sxheuxtd98****",
  "RequestId": "4EC47282-1B74-4534-BD0E-403F3EE64CAF"
}

Error codes

HTTP status codeError codeError message
400OperationFailed.VbrCenNotConsistentThe VBR and the peer VBR are attached to different CENs.
400OperationFailed.VbrAliUidNotConsistentThe VBR and the peer VBR belong to different AliUids.
400OperationFailed.VbrAccessDeviceSameThe VBR and the peer VBR are in the same device.
400OperationFailed.VbrBandWidthExceedThe VBR bandwidth exceeds the limit.
400OperationFailed.VbrInUsedByOtherHaThe VBR is used by another VBR HA.
400OperationFailed.VbrBgpPeerNotEnableBfdThe VBR BGP has not enabled BFD.
400OperationFailed.VbrCenNotRelationThe VBR is not attached to any CEN.
404ResourceNotFound.VbrThe VBR resource is not found.

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

Change history

Change timeSummary of changesOperation
2023-09-11API Description Update. The Error code has changedsee changesets
Change itemChange content
API DescriptionAPI Description Update.
Error CodesThe Error code has changed.
    delete Error Codes: 400
    delete Error Codes: 404