All Products
Search
Document Center

Virtual Private Cloud:ModifyBgpGroupAttribute

Last Updated:Jul 11, 2024

Modifies the configuration of a Border Gateway Protocol (BGP) group.

Debugging

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

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringYes

The region ID of the BGP group.

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

cn-shanghai
BgpGroupIdstringYes

The BGP group ID.

bgpg-wz9f62v4fbg2g****
NamestringNo

The BGP group name.

The name must be 2 to 128 characters in length, and can contain digits, periods (.), underscores (_), and hyphens (-). The name must start with a letter but cannot start with http:// or https://.

test
DescriptionstringNo

The BGP group description.

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

BGP
LocalAsnlongNo

The custom autonomous system number (ASN) of the BGP on the Alibaba Cloud side. Valid values:

  • 45104
  • 64512~65534
  • 4200000000~4294967294
Note 65025 is reserved by Alibaba Cloud. Alibaba Cloud uses 45104 as the local ASN by default. Custom local ASNs may cause loops in multi-line scenarios. Proceed with caution.
45104
PeerAsnlongNo

The ASN of the gateway device in the data center.

1****
AuthKeystringNo

The authentication key of the BGP group.

!PWZ2****
IsFakeAsnbooleanNo

Specifies whether to use a fake AS number. Valid values:

  • false (default)
  • true
Note A router that runs BGP typically belongs to only one AS. If you need to replace an AS with a new one, but you cannot immediately modify BGP configurations due to business requirements, you can specify a fake AS number to establish a connection with the local end. This ensures service continuity in scenarios such as AS migration or AS merging.
false
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 client 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.
123e4567-e89b-12d3-a456-426655440000
RouteQuotaintegerNo

The maximum number of routes supported by a BGP peer. Default value: 110.

110
ClearAuthKeybooleanNo

Specifies whether to clear the secret key. Valid values:

  • true
  • false (default)
false

Response parameters

ParameterTypeDescriptionExample
object

The request ID.

RequestIdstring

The request ID.

8C3C6D7C-A1CE-4FD8-BC57-DC493A55F76F

Examples

Sample success responses

JSONformat

{
  "RequestId": "8C3C6D7C-A1CE-4FD8-BC57-DC493A55F76F"
}

Error codes

HTTP status codeError codeError messageDescription
400QuotaExceeded.Bgpbgp peer count per vbr quota exceed.The number of BGP peers in the VBR has reached the upper limit.
400QuotaExceeded.Nqanqa count per vbr quota exceed.The number of Network Quality Analyzers (NQAs) has reached the upper limit that is supported by the VBR.
400QuotaExceeded.BgpNetworkbgp network count per vbr quota exceed.The number of BGP networks in the VBR has reached the upper limit.
400InvalidPeerIpAddressmulti pconn peer ip can not be null.The IP addresses of multiple Express Connect circuits cannot be empty.
400InvalidVbrNetworkvbr netowrk not existsThe VBR does not exist. Check the VBR ID.
400InvalidBgpGroupbgp group not existsThe BGP group does not exist.
400InvalidBgpName.MalformedSpecified Bgp Group name is not valid.The name of the BGP group is invalid.
400InvalidBgpDiscription.MalformedSpecified Bgp Group description is not valid.The description of the BGP group is invalid.
400InvalidBgpAuthkey.MalformedSpecified Bgp Group authkey is not valid.The authentication key of the BGP group is invalid.
400InvalidIP.MalformedIp malformed.The format of the IP address is invalid.
400InvalidPeerAsn.Malformedinvalid peer asn cannot equals aliyun asn:45104The AS number cannot be the same as the AS number on the Alibaba Cloud side.
400InvalidParams.NotNull%s-
400InvalidBgpGroup.LocalAsnInvalidThe specified BgpGroup LocalAsn is invalid, only support 64512 to 65534 or 4200000000 to 4294967294, and cannot be 65025.-
400InvalidParams.NotFoundinstance not foundThe specified instance does not exist.
400InvalidParams.NotFoundvpc instance not foundThe VPC does not exist. Check whether the specified VPC is valid.
400InvalidParams.AlreadyExistsbgp network already existsThe BGP network already exists.
400InvalidStatus.CannotOperateinvalid status cannot operateYou cannot perform the operation when the specified resource is in the current state.
400InvalidParams.PeerIpAddressMustPointOutvbr has 0 or more than 1 subif ,point out peerIpAddress.You must set the PeerIpAddress parameter.
400InvalidParams.PeerIpAddressInUsepeer ip address in use ,cannot create bgp peer.The peer IP address is being used. Therefore, you cannot use it to create a BGP peer.
400InvalidStatus.CannotOperateInstance is not in stable status,please wait and try again.-
400IllegalParam.PeerAsn%s-
400IllegalParam.LocalAsn%s-
400OperationFailed.PconnTrafficNotEnableThe operation is failed because of PconnTrafficNotEnable.Billing for outbound data transfer is disabled.
400OperationUnsupportOperation is unsupport, not in vbr support custom local asn white list.The operation is not supported.
400OperationFailed.ClearAuthKeyForbiddenThe specific auth key is not empty.The specified key is not empty and cannot be cleared.
400IllegalParam.RouteLimitThe operation is failed because of bgp group max route entry num quota exceed.The number of routes that can be received by each BGP peer in the BGP group exceeds the upper limit.
400OperationDenied.VbrAttachEcrInMiddleStatusThe operation is not allowed because of VBR attach or detach ECR in middle status.The current operation cannot be performed because the VBR is in the process of loading or unloading the leased line gateway. Please wait a moment and try again.
400OperationUnsupported.VBRAttachedECRVBR already attached to ECR, please delete it from ECR.The VBR has been bound to ECR. Delete the VBR from ECR and try again.
404InvalidRegionId.NotFoundSpecified value of "regionId" is not supported.RegionId is set to an invalid value. Check whether the service is available in the specified region and try again.

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

Change history

Change timeSummary of changesOperation
2024-06-19The Error code has changedView Change Details
2024-06-13API Description Update. The Error code has changedView Change Details