ModifyBgpGroupAttribute - API Reference| Alibaba Cloud Documentation Center

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	Yes	ModifyBgpGroupAttribute	The operation that you want to perform. Set the value to ModifyBgpGroupAttribute.
RegionId	String	Yes	cn-shanghai	The ID of the region to which the BGP group belongs. You can call the DescribeRegions operation to query the most recent region list.
BgpGroupId	String	Yes	bgpg-wz9f62v4fbg2g****	The ID of the BGP group.
Name	String	No	test	The name of the BGP group. 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 and cannot start with `http://` or `https://`.
Description	String	No	BGP	The description of the BGP group. The description must be 2 to 256 characters in length. The description must start with a letter but cannot start with `http://` or `https://`.
LocalAsn	Long	No	45104	The autonomous system (AS) number of the device on the Alibaba Cloud side.
PeerAsn	Long	No	1****	The AS number of the on-premises device.
AuthKey	String	No	!PWZ2****	The authentication key of the BGP group.
IsFakeAsn	Boolean	No	true	Specifies whether to use a fake AS number. Valid values: false (default): no true: yes Note A running BGP router typically belongs to only one AS. If you want to replace the current AS with a new one (for example, the current AS needs to be migrated or merged with another one) and you cannot modify BGP configurations, you can specify a fake AS number to establish connections to the on-premises device. This ensures that your services are not interrupted.
ClientToken	String	No	123e4567-e89b-12d3-a456-426655440000	The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must make sure that it is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length. Note If you do not set this parameter, the system automatically uses RequestId as ClientToken. RequestId may be different for each API request.

Response parameters


Parameter	Type	Example	Description
RequestId	String	8C3C6D7C-A1CE-4FD8-BC57-DC493A55F76F	The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?Action=ModifyBgpGroupAttribute
&RegionId=cn-shanghai
&BgpGroupId=bgpg-wz9f62v4fbg2g****
&Name=test
&Description=BGP
&LocalAsn=45104
&PeerAsn=1111
&AuthKey=!PWZ2wsq
&IsFakeAsn=true
&ClientToken=123e4567-e89b-12d3-a456-426655440000
&Common request parameters

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<ModifyBgpGroupAttributeResponse>
    <RequestId>8C3C6D7C-A1CE-4FD8-BC57-DC493A55F76F</RequestId>
</ModifyBgpGroupAttributeResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

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

Error codes


HttpCode	Error code	Error message	Description
400	QuotaExceeded.Bgp	bgp peer count per vbr quota exceed.	The error message returned because the number of BGP groups in the virtual border router (VBR) has reached the upper limit.
400	QuotaExceeded.Nqa	nqa count per vbr quota exceed.	The error message returned because the Network Quality Analyzer (NQA) number has reached the upper limit.
400	QuotaExceeded.BgpNetwork	bgp network count per vbr quota exceed.	The error message returned because the number of BGP networks in the VBR has reached the upper limit.
400	InvalidPeerIpAddress	multi pconn peer ip can not be null.	The error message returned because the IP addresses of multiple Express Connect circuits cannot be empty.
400	InvalidVbrNetwork	vbr netowrk not exists	The error message returned because the specified VBR does not exist. Check whether the parameter is set to a valid value.
400	InvalidBgpGroup	bgp group not exists	The error message returned because the BGP group does not exist.
400	InvalidBgpName.Malformed	Specified Bgp Group name is not valid.	The error message returned because the name of the BGP group is invalid.
400	InvalidBgpDiscription.Malformed	Specified Bgp Group description is not valid.	The error message returned because the description of the BGP group is invalid.
400	InvalidBgpAuthkey.Malformed	Specified Bgp Group authkey is not valid.	The error message returned because the authentication key of the BGP group is invalid.
400	InvalidIP.Malformed	Ip malformed.	The error message returned because the format of the IP address is invalid.
400	InvalidPeerAsn.Malformed	invalid peer asn cannot equals aliyun asn:45104	The error message returned because the AS number cannot be the same as the AS number on the Alibaba Cloud side.
400	InvalidParams.NotFound	instance not found	The error message returned because the specified instance does not exist.
400	InvalidParams.NotFound	vpc instance not found	The error message returned because the specified virtual private cloud (VPC) does not exist. Check whether the specified VPC ID is valid.
400	InvalidParams.AlreadyExists	bgp network already exists	The error message returned because the BGP network already exists.
400	InvalidStatus.CannotOperate	invalid status cannot operate	The error message returned because you cannot perform the operation when the specified resource is in the current state.
400	OperationFailed.PconnTrafficNotEnable	The operation is failed because of PconnTrafficNotEnable.	The error message returned because outbound traffic is disabled.
404	InvalidRegionId.NotFound	Specified value of "regionId" is not supported.	The error message returned because RegionId is set to an invalid value. Check whether the service is available in the specified region.

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