Docs

Transit Router

Traffic qos marking policy

DissociateTransitRouterTrafficQosMarkingPolicyFromAttachment - Dissociating a traffic marking policy from an attachment

Call the DissociateTransitRouterTrafficQosMarkingPolicyFromAttachment API to dissociate a traffic marking policy from a Transit Router (TR) attachment.

Precautions

Traffic marking may be impacted by disabling a traffic marking policy. If the bandwidth allocated to the scheduling queue matched by the traffic marking is insufficient for actual business requirements, 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.

Go to debug

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 value: DissociateTransitRouterTrafficQosMarkingPolicyFromAttachment

The interface name. The current API name is DissociateTransitRouterTrafficQosMarkingPolicyFromAttachment.

Version String required Example value: 2020-04-01

The interface version. The current API version is 2020-04-01.

TransitRouterAttachmentId String required Example value: tr-attach-13n2l4c****

The attachment ID.

Currently, only inter-region attachments are supported. You can call DescribeTransitRouterPeerAttachments to obtain the ID of the inter-region attachment.

TransitRouterTrafficQosMarkingPolicyId String required Example: tr-tmp-hy13n2l4c6c0v****

ID of the traffic marking policy. You can call the DescribeTransitRouterTrafficQosMarkingPolicies API to obtain the ID of the traffic marking policy.

Response parameters

This API does not have specific response parameters. For more information, see Response structure.

Request examples

GET /?Action=DissociateTransitRouterTrafficQosMarkingPolicyFromAttachment&Version=2020-04-01&TransitRouterAttachmentId=tr-attach-13n2l4c****&TransitRouterTrafficQosMarkingPolicyId=tr-tmp-hy13n2l4c6c0v**** HTTP/1.1​
Host: transitrouter.cn-beijing.volcengineapi.com​
X-Date: 20250731T090352Z​
Authorization: HMAC-SHA256 Credential=Adfks******wekfwe/20250731/cn-beijing/transitrouter/request, SignedHeaders=host;x-date, Signature=47a7d934ff7b37c03938******cd7b8278a40a1057690c401e92246a0e41085f​

Response examples

{​
    "ResponseMetadata": {​
        "RequestId": "20250731170355061051246044F51A0C",​
        "Action": "DissociateTransitRouterTrafficQosMarkingPolicyFromAttachment",​
        "Version": "2020-04-01",​
        "Service": "transitrouter",​
        "Region": "cn-beijing"​
    },​
    "Result": {}​
}​

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	Explanation
400	InvalidTransitRouter.InvalidStatus	The specified Transit Router is not in the correct status for the request.	The specified Transit Router (TR) is in a status that cannot respond to the request.
400	InvalidTransitRouterAttachment.InvalidStatus	The specified Transit Router Attachment is not in the correct status for the request.	The specified network instance attachment is in a status that cannot respond to the request.
403	Forbidden.NoPermissionToOperate	You are not authorized to operate the specified resource.	No permission to manage the specified resource.
404	InvalidTransitRouterAttachment.NotFound	The specified Transit Router attachment does not exist.	The specified network instance attachment does not exist.
404	InvalidTransitRouterAttachment.TrafficQosMarkingPolicyNotAssociated	The specified Transit Router attachment has not been associated with the traffic qos marking policy, and the dissociate operation is invalid.	This traffic marking policy is not configured to the specified network instance attachment. Therefore, disassociation is invalid.
404	InvalidTransitRouterTrafficQosMarkingPolicy.NotFound	The specified Transit Router traffic qos marking policy does not exist.	The specified traffic marking policy does not exist.

Last updated: 2025.12.29 19:25:30