Modifies the name, description, and traffic classification rules of a traffic marking policy.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
cen:UpdateTrafficMarkingPolicyAttribute | Write |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
ClientToken | string | No | 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. | 123e4567-e89b-12d3-a456-426**** |
DryRun | boolean | No | Specifies whether to perform a dry run. Valid values:
| false |
TrafficMarkingPolicyId | string | Yes | The ID of the traffic marking policy. | tm-u9nxup5kww5po8**** |
TrafficMarkingPolicyName | string | No | The new name of the traffic marking policy. The name must be 2 to 128 characters in length, and can contain letters, digits, underscores (_), and hyphens (-). It must start with a letter. | nametest |
TrafficMarkingPolicyDescription | string | No | The new description of the traffic marking policy. The description must be 2 to 128 characters in length, and can contain letters, digits, underscores (_), and hyphens (-). The description must start with a letter. | desctest |
AddTrafficMatchRules | object [] | No | The traffic classification rules to be added to the traffic marking policy. | |
MatchDscp | integer | No | The Differentiated Service Code Point (DSCP) value that is used to match packets. Valid values: 0 to 63. Requests that carry the specified DSCP value are considered a match. If you do not specify a DSCP value, packets are considered a match regardless of the DSCP value. Note
The DSCP value that you specify for this parameter is the DSCP value that packets carry before they are transmitted over the inter-region connection.
You can create up to 50 traffic classification rules in each call. You can specify a DSCP value for each traffic classification rule. | 1 |
DstCidr | string | No | The destination CIDR block that is used to match packets. Packets whose destination IP addresses fall into the specified destination CIDR block are considered a match. If you do not specify a destination CIDR block, packets are considered a match regardless of the destination IP address. You can create up to 50 traffic classification rules in each call. You can specify a destination CIDR block for each traffic classification rule. | 172.30.0.0/24 |
TrafficMatchRuleDescription | string | No | The description of the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a description for each traffic classification rule. This parameter is optional. If you enter a description, it must be 1 to 256 characters in length, and cannot start with http:// or https://. | test1 |
Protocol | string | No | The protocol that is used to match packets. Traffic classification rules support the following protocols: HTTP, HTTPS, TCP, UDP, SSH, and Telnet. For more information, log on to the CEN console. Some protocols use a fixed port. Click to view the protocols and ports.
You can create up to 50 traffic classification rules in each call. You can specify a protocol for each traffic classification rule. | UDP |
DstPortRange | array | No | The destination port range that is used to match packets. Valid values: -1 and 1 to 65535. Packets whose destination ports fall into the specified destination port range are considered a match. If you do not specify a destination port range, packets are considered a match regardless of the destination port. You can enter up to two port numbers. Take note of the following rules:
You can create up to 50 traffic classification rules in each call. You can specify a destination port range for each traffic classification rule. | |
integer | No | The destination port range that is used to match packets. Valid values: -1 and 1 to 65535. Packets whose destination ports fall within the specified destination port range are considered a match. If you do not specify a destination port range, packets are considered a match regardless of the destination port. You can enter up to two port numbers. Take note of the following rules:
You can create up to 50 traffic classification rules in each call. You can specify a destination port range for each traffic classification rule. | 77 | |
SrcCidr | string | No | The source CIDR block that is used to match packets. Packets whose source IP addresses fall into the specified source CIDR block are considered a match. If you do not specify a source CIDR block, packets are considered a match regardless of the source IP address. You can create up to 50 traffic classification rules in each call. You can specify a source CIDR block for each traffic classification rule. | 10.128.32.0/19 |
SrcPortRange | array | No | The source port range that is used to match packets. Valid values: -1 and 1 to 65535. Packets whose source ports fall into the specified source port range are considered a match. If you do not specify a source port range, packets are considered a match regardless of the source port. You can enter up to two port numbers. Take note of the following rules:
You can create up to 50 traffic classification rules in each call. You can specify a source port range for each traffic classification rule. | |
integer | No | The source port range that is used to match packets. Valid values: -1 and 1 to 65535. Packets whose source ports fall into the specified source port range are considered a match. If you do not specify a source port range, packets are considered a match regardless of the source port. You can enter up to two port numbers. Take note of the following rules:
You can create up to 50 traffic classification rules in each call. You can specify a source port range for each traffic classification rule. | 22 | |
TrafficMatchRuleName | string | No | The name of the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a name for each traffic classification rule. The name can be empty or 1 to 128 characters in length, and cannot start with http:// or https://. | Guangzhou Testing |
DeleteTrafficMatchRules | object [] | No | The traffic classification rules to be deleted from the traffic marking policy. Note
Specify detailed information about the traffic classification rule, such as the source CIDR block, destination CIDR block, source port, destination port, and DSCP value. If you do not specify sufficient information, the system may fail to match the traffic classification rule that you want to delete.
| |
MatchDscp | integer | No | The DSCP value that is used to match packets. | 3 |
DstCidr | string | No | The destination CIDR block that is used to match packets. | 192.168.200.3/32 |
TrafficMatchRuleDescription | string | No | The description of the traffic classification rule. This parameter is optional. If you enter a description, it must be 1 to 256 characters in length, and cannot start with http:// or https://. | Hangzhou-to-Qingdao CAT |
Protocol | string | No | The protocol that is used to match packets. You can call the ListTrafficMarkingPolicies operation to query the details about a traffic classification rule. | TCP |
DstPortRange | array | No | The destination port range that is used to match packets. | |
integer | No | The destination port range that is used to match packets. | -1 | |
SrcCidr | string | No | The source CIDR block that is used to match packets. | 10.72.0.0/16 |
SrcPortRange | array | No | The source port range that is used to match packets. | |
integer | No | The source port range that is used to match packets. | 23 | |
TrafficMatchRuleName | string | No | The name of the traffic classification rule. The name can be empty or 1 to 128 characters in length, and cannot start with http:// or https://. | test |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "60BB11B2-7BF4-54DC-BCC9-F706E1EB02AC"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | InvalidTrafficMarkingPolicyId.NotFound | TrafficMarkingPolicyId is not found. | The error message returned because the specified traffic marking policy ID (TrafficMarkingPolicyId) does not exist. |
400 | IncorrectStatus.TrafficMarkingPolicy | The status of TrafficMarkingPolicy is incorrect. | The error message returned because the status of the traffic marking policy does not support this operation. Try again later. |
400 | Duplicated.AddTrafficMatchRules | The parameter AddTrafficMatchRules are duplicated. | - |
400 | Duplicated.DeleteTrafficMatchRulese | The parameter DeleteTrafficMatchRules are duplicated. | - |
400 | InstanceExist.AddTrafficMatchRules | The instance already exists. | The error message returned because the specified instance already exists. |
400 | Duplicated.AddTrafficMatchRulesAndDeleteTrafficMatchRules | The same rule in AddTrafficMatchRules and DeleteTrafficMatchRules is not supported.. | The error message returned because the AddTrafficMatchRules and DeleteTrafficMatchRules cannot specify the same route. Delete duplicate routes and try again. |
400 | InvalidParameter | Invalid parameter. | The error message returned because the parameter is set to an invalid value. |
400 | Unauthorized | The AccessKeyId is unauthorized. | The error message returned because you do not have the permissions to perform this operation. |
404 | InvalidDeleteTrafficMatchRules.NotFound | The specified DeleteTrafficMatchRules are not found. | The error message returned because the value of the DeleteTrafficMatchRules parameter does not exist. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2024-03-15 | The Error code has changed | see changesets | ||||||||||||
| ||||||||||||||
2023-09-08 | The Error code has changed | see changesets | ||||||||||||
| ||||||||||||||
2023-01-09 | The Error code has changed. The request parameters of the API has changed | see changesets | ||||||||||||
| ||||||||||||||
2021-11-26 | Add Operation | see changesets |