All Products
Search
Document Center

Cloud Enterprise Network:SetCenInterRegionBandwidthLimit

Last Updated:Jul 05, 2024

Configures, modifies, or deletes the bandwidth of inter-region connections for a Basic Edition transit router.

Operation description

Prerequisites

The Cloud Enterprise Network (CEN) instance is associated with a bandwidth plan. For more information, see the CreateCenBandwidthPackage and AssociateCenBandwidthPackage topics.

You can call the SetCenInterRegionBandwidthLimit operation to configure, modify, or remove the maximum bandwidth value of an inter-region connection.

  • If you set BandwidthLimit to a value other than 0, the maximum bandwidth value of the inter-region connection is set or changed to the specified value.
  • If you set BandwidthLimit to 0, no bandwidth resource is allocated to the inter-region connection.

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
CenIdstringYes

The ID of the CEN instance.

cen-7qthudw0ll6jmx****
LocalRegionIdstringYes

The ID of the local region.

You can call the DescribeChildInstanceRegions operation to query regions where you can attach network instances to a CEN instance.

cn-hangzhou
OppositeRegionIdstringYes

The ID of the peer region.

us-west-1
BandwidthLimitlongYes

The maximum bandwidth value of the inter-region connection. Unit: Mbit/s.

8
BandwidthTypestringNo

The bandwidth allocation method. Valid values:

BandwidthPackage: allocates bandwidth from a bandwidth plan.

BandwidthPackage

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The ID of the request.

530BC816-F575-412A-AAB2-435125D26328

Examples

Sample success responses

JSONformat

{
  "RequestId": "530BC816-F575-412A-AAB2-435125D26328"
}

Error codes

HTTP status codeError codeError messageDescription
400MissingParam.CbnBandwidthPackageIdThere are more than one suitable cen bandwidth packageThe error message returned because the CbnBandwidthPackageId parameter is not set.
400AttrMismatching.CbnBandwidthPackageId%s-
400OperationFailed.InvalidOperationThe operation is failed because the operation is not support.-
400OperationUnsupported.AttachmentThe cross region connection contains an existing bandwidth. The operation is not supported.The error message returned because bandwidth multiplexing is enabled for the inter-region connection.
400InvalidOperation.UnsupportChargeTypeThe charge type is not supported by this operation.The error message returned because the specified billing method does not support this operation.
400OperationUnsupported.TrafficQosPolicyExistOperation unsupported because traffic qos policy exists.The error message returned because the specified QoS policy already exists.
400OperationUnsupported.BandwidthTypeThe specified BandwidthType does not support the operation.The error message returned because this operation is not supported by the specified bandwidth type.
400IllegalParam.BandwidthTypeBandwidthType is illegal.The error message returned because the specified bandwidth plan type is invalid.
400IllegalParam.BandwidthBandwidth is illegal.The error message returned because the specified bandwidth plan ID is invalid.
400ParamExclusive.BandwidthTypeAndCenBandwidthPackageIdDataTransfer and CenBandwidthPackageId is mutually exclusive.When the value of bandwidthType is DataTransfer, the CenBandwidthPackageId field cannot be set.
400IdentityRegistrationStatusNotSupportReal name registration of enterprises required.Real name registration of enterprises required.
400InvalidParameterInvalid parameter.The error message returned because the parameter is set to an invalid value.
400UnauthorizedThe AccessKeyId is unauthorized.The error message returned because you do not have the permissions to perform this operation.

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

Change history

Change timeSummary of changesOperation
2024-05-17The Error code has changed. The request parameters of the API has changedView Change Details
2023-09-08The Error code has changedView Change Details