You need to enable JavaScript to run this app.
Transit Router

Transit Router

Copy page
Download PDF
Traffic qos queue policy
CreateTransitRouterTrafficQosQueueEntry - Adding a traffic queue
Copy page
Download PDF
CreateTransitRouterTrafficQosQueueEntry - Adding a traffic queue
Call the CreateTransitRouterTrafficQosQueueEntry API to add queues to a traffic queue policy.​
Instructions​
A traffic queue policy consists of 1 default queue and additionally supports up to 64 custom queues.​​
Precautions​
​​If the allocated bandwidth is insufficient for actual business requirements after adding a queue, normal service forwarding may be impacted.​​
Debug​
API Explorer
You can initiate calls online through API Explorer without paying attention to the signature generation process and quickly obtain the call results.
​
Request parameters​
The following only details request parameters specific to this API and key common parameters. For more information, see Common parameters.​
Action String required Example: CreateTransitRouterTrafficQosQueueEntry​
The interface name. The current API name is CreateTransitRouterTrafficQosQueueEntry.​
​
Version String required Example: 2020-04-01​
The interface version. The current API version is 2020-04-01.​
​
TransitRouterTrafficQosQueuePolicyId String required Example: tr-tqp-hy13n2l4c6c0v****​
ID of the traffic queue policy. You can call the DescribeTransitRouterTrafficQosQueuePolicies API to obtain the traffic queue policy ID.​
​
Dscps.N Integer required Example: 1​
​​The DSCP value that the queue should match.​ Value range: 0-63.​
  • N represents the serial number of the DSCP value, ranging from 1 to 64.​
  • Separate multiple DSCP values with ampersands (&).​
​
BandwidthPercent Integer optional Example: 10​
The percentage of cross-region bandwidth available for the queue. Value range: 0-100.​
If the value is 0, traffic that successfully matches the queue will be discarded.​
​
TransitRouterTrafficQosQueueEntryName String required Example: tqe-02​
The queue name.​
  • Must start with a letter, number, or Chinese character. May include letters, numbers, Chinese characters, and the following symbols: periods (.), underscores (_), and hyphens (-).​
  • Must be 1 to 128 characters.​
  • If you do not provide this parameter or leave it unset, it defaults to empty.​
​
Description String optional Example: This traffic qos queue entry is used for test.​
The description of the queue.​
  • Must start with a letter, number, or Chinese character. May include letters, numbers, Chinese characters, and the following symbols: commas (,), periods (.), underscores (_), spaces ( ), equal signs (=), hyphens (-), Chinese commas ( , ), and Chinese periods ( 。 ).​
  • Must be 0 to 255 characters.​
  • If you do not provide this parameter or leave it unset, it defaults to an empty string.​
​
ClientToken String optional Example: 123e4567-e89b-12d3-a456-42665544****​
The Client Token that is used to ensure the request idempotency.​
  • This parameter value is auto-generated by the client. Ensure uniqueness across requests, preventing duplicate actions caused by multiple client retries during API timeouts or server internal errors.​
  • Must not exceed 64 ASCII characters.​
  • If you do not set this parameter, the idempotency check is not performed.​
​
Priority String optional Example: High​
The priority of the traffic queue.​
  • Normal: Normal priority.​
  • High: High priority.​
​
​
​
Response parameters​
The following only details response parameters specific to this API. For more information, see Response parameters.​
TransitRouterTrafficQosQueueEntryId String Example: tr-tqe-1i5i8khf9m58gae5kcx6****​
Traffic queue ID.​
​
​
​
Request examples​
​
GET /?Action=CreateTransitRouterTrafficQosQueueEntry&Version=2020-04-01&TransitRouterTrafficQosQueuePolicyId=tr-tqp-hy13n2l4c6c0v****&Dscps.1=1&BandwidthPercent=10&TransitRouterTrafficQosQueueEntryName=tqe-02 HTTP/1.1​
Host: transitrouter.cn-beijing.volcengineapi.com​
X-Date: 20250815T040532Z​
Authorization: HMAC-SHA256 Credential=Adfks******wekfwe/20250815/cn-beijing/transitrouter/request, SignedHeaders=host;x-date, Signature=47a7d934ff7b37c03938******cd7b8278a40a1057690c401e92246a0e41085f​
​
Response examples​
​
{​
"ResponseMetadata": {​
"RequestId": "20250815120534155194148038FB8C6D",​
"Action": "CreateTransitRouterTrafficQosQueueEntry",​
"Version": "2020-04-01",​
"Service": "transitrouter",​
"Region": "cn-beijing"​
},​
"Result": {​
"TransitRouterTrafficQosQueueEntryId": "tr-tqe-1i5i8khf9m58gae5kcx6****"​
}​
}​
​
Error codes​
The table below describes the error codes for this API that are associated with business logic. For more information, see Common error codes.​
​
Status code​
Error codes​
Error message​
Description​
400​
IdempotentParameterMismatch​
Arguments on this idempotent request are inconsistent with arguments used in previous request(s).​
The parameters of this idempotent request are inconsistent with those used in the previous request.​
400​
InvalidDescription.Malformed​
The specified description is malformed.​
The format of specified description is invalid. Correct the description format and retry.​
400​
InvalidDescription.TooLong​
The specified description is malformed. Ensure the maximum length of description is 255.​
The format of specified description is invalid. A description must not exceed 255 characters.​
400​
InvalidName.Malformed​
The specified name is malformed.​
The format of the specified name is invalid. Correct the name format and retry.​
400​
InvalidName.TooLong​
The specified name is malformed. Ensure the maximum length of name is 128.​
The format of specified name is invalid. A name must not exceed 128 characters.​
400​
InvalidParameter.ClientTokenMalformed​
The specified parameter ClientToken is malformed.​
The format of specified ClientToken is invalid. It must not exceed 64 ASCII characters.​
400​
InvalidTransitRouter.InvalidBusinessStatus​
The request is denied because the specified Transit Router is shut down due to arrears.​
The specified Transit Router (TR) is suspended due to overdue payments. Action unsupported.​
400​
InvalidTransitRouter.InvalidStatus​
The specified Transit Router is not in the correct status for the request.​
The specified TR is in a status that cannot respond to the request.​
400​
InvalidTransitRouterTrafficQosQueueEntry.BandwidthPercentExceed​
The specified bandwidth percentage of the traffic qos queue entry exceeds the available remaining bandwidth percentage.​
The specified queue bandwidth percentage exceeds the remaining allocable bandwidth percentage.​
400​
InvalidTransitRouterTrafficQosQueueEntry.BandwidthPercentNotSupport​
The specified bandwidth percent of the Transit Router traffic qos queue entry is invalid. Only normal priority traffic qos queues support configuring bandwidth percent.​
The specified queue bandwidth percentage is invalid. You can only configure bandwidth percentage for normal-priority queues.​
400​
InvalidTransitRouterTrafficQosQueueEntry.InvalidBandwidthPercent​
The specified bandwidth percent of the Transit Router traffic qos queue entry is invalid. Bandwidth percent only support 0~100.​
The specified queue bandwidth percentage is invalid. It must be an integer between 0 and 100.​
400​
InvalidTransitRouterTrafficQosQueueEntry.InvalidDscp​
The specified dscp of the Transit Router traffic qos queue entry is invalid. Dscp only support 0~63.​
The DSCP of the specified traffic queue is invalid. It must be an integer between 0 and 63.​
400​
InvalidTransitRouterTrafficQosQueueEntry.PriorityExist​
The specified Transit Router traffic qos queue policy already has a high priority traffic qos queue.​
The specified traffic queue policy already contains high-priority queues. Duplicate action is not supported.​
400​
InvalidTransitRouterTrafficQosQueueEntry.PriorityInvalid​
The specified priority of the Transit Router traffic qos queue entry is invalid, only Normal and High are supported.​
The specified queue priority is invalid. Only Normal and High are supported.​
400​
QuotaExceeded.TransitRouterTrafficQosQueueEntry​
You've reached the limit on the number of traffic qos queue entries that you can create on one traffic qos queue policy.​
You have reached the maximum number of traffic queues for a single traffic queue policy.​
404​
InvalidTransitRouterTrafficQosQueuePolicy.NotFound​
The specified Transit Router traffic qos queue policy does not exist.​
The specified traffic queue policy does not exist.​
409​
InvalidTransitRouterTrafficQosQueueEntry.DscpConflict​
The specified dscp of the Transit Router traffic qos queue entry conflicts with another entry.​
The DSCP of the specified traffic queue conflicts with that of another queue.​
412​
IdempotentProcessing​
The request uses the same client token as a previous one that is still in process.​
The idempotent request is in progress.​
​
​
Last updated: 2026.03.11 11:24:56