All Products
Search
Document Center

Cloud Enterprise Network:UpdateTrafficMarkingPolicyAttribute

Last Updated:Jan 19, 2024

Modifies the name and description of a traffic marking policy.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

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.
OperationAccess levelResource typeCondition keyAssociated operation
cen:UpdateTrafficMarkingPolicyAttributeWrite
  • CenInstance
    acs:cen:*:{#accountId}:ceninstance/{#CenId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
ClientTokenstringNo

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****
DryRunbooleanNo

Specifies whether to perform a dry run. Valid values:

  • true: preforms a dry run. The system checks the required parameters, request syntax, and limits. If the request fails the dry run, an error message is returned. If the request passes the dry run, the DryRunOperation error code is returned.
  • false (default): performs a dry run and sends the request.
false
TrafficMarkingPolicyIdstringYes

The ID of the traffic marking policy.

tm-u9nxup5kww5po8****
TrafficMarkingPolicyNamestringNo

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
TrafficMarkingPolicyDescriptionstringNo

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
AddTrafficMatchRulesobject []No

The traffic classification rules to be added to the traffic marking policy.

MatchDscpintegerNo

The differentiated services code point (DSCP) value that is used to match packets. Valid values: 0 to 63.

The traffic classification rule matches the packets that contain the specified DSCP value. If you do not set this parameter, 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 at a time. You can specify a DSCP value for each traffic classification rule.

1
DstCidrstringNo

The destination CIDR block that is used to match packets.

The traffic classification rule matches the packets whose destination IP addresses fall within the specified destination CIDR block. If you do not set this parameter, packets are considered a match regardless of the destination IP address.

You can create up to 50 traffic classification rules at a time. You can specify a destination CIDR block for each traffic classification rule.

172.30.0.0/24
TrafficMatchRuleDescriptionstringNo

The description of the traffic classification rule.

You can create up to 50 traffic classification rules at a time. You can specify a description for each traffic classification rule.

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.

test1
ProtocolstringNo

The protocol that is used to match packets.

Valid values: HTTP, HTTPS, TCP, UDP, SSH, and Telnet. For more information, log on to the Cloud Enterprise Network (CEN) console.

You can create up to 50 traffic classification rules at a time. You can specify a protocol for each traffic classification rule.

UDP
DstPortRangearrayNo

The destination port range that is used to match packets. Valid values: -1 and 1 to 65535.

The traffic classification rule matches the packets whose destination ports fall within the destination port range. If you do not set this parameter, packets are considered a match regardless of the destination port.

You can specify at most two ports. Take note of the following rules:

  • If you enter only one port number such as 1, the system matches the packets whose destination port is port 1.
  • If you enter two port numbers such as 1 and 200, the system matches the packets whose destination ports fall between 1 and 200.
  • If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, packets are considered a match regardless of the destination port.

You can create up to 50 traffic classification rules at a time. You can specify a destination port range for each traffic classification rule.

integerNo

The destination port range that is used to match packets. Valid values: -1 and 1 to 65535.

The traffic classification rule matches the packets whose destination ports fall within the destination port range. If you do not set this parameter, packets are considered a match regardless of the destination port.

You can specify at most two ports. Take note of the following rules:

  • If you enter only one port number such as 1, the system matches the packets whose destination port is port 1.
  • If you enter two port numbers such as 1 and 200, the system matches the packets whose destination ports fall between 1 and 200.
  • If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, packets are considered a match regardless of the destination port.

You can create up to 50 traffic classification rules at a time. You can specify a destination port range for each traffic classification rule.

77
SrcCidrstringNo

The source CIDR block that is used to match packets.

The traffic classification rule matches the packets whose source IP addresses fall within the specified source CIDR block. If you do not set this parameter, packets are considered a match regardless of the source IP address.

You can create up to 50 traffic classification rules at a time. You can specify a source CIDR block for each traffic classification rule.

10.128.32.0/19
SrcPortRangearrayNo

The source port range that is used to match packets. Valid values: -1 and 1 to 65535.

The traffic classification rule matches the packets whose source ports fall within the source port range. If you do not set this parameter, packets are considered a match regardless of the source port.

You can specify at most two ports. Take note of the following rules:

  • If you enter only one port number such as 1, the system matches the packets whose source port is 1.
  • If you enter two port numbers such as 1 and 200, the system matches the packets whose source ports fall between 1 and 200.
  • If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, packets are considered a match regardless of the source port.

You can create up to 50 traffic classification rules at a time. You can specify a source port range for each traffic classification rule.

integerNo

The source port range that is used to match packets. Valid values: -1 and 1 to 65535.

The traffic classification rule matches the packets whose source ports fall within the source port range. If you do not set this parameter, packets are considered a match regardless of the source port.

You can specify at most two ports. Take note of the following rules:

  • If you enter only one port number such as 1, the system matches the packets whose source port is 1.
  • If you enter two port numbers such as 1 and 200, the system matches the packets whose source ports fall between 1 and 200.
  • If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, packets are considered a match regardless of the source port.

You can create up to 50 traffic classification rules at a time. You can specify a source port range for each traffic classification rule.

22
TrafficMatchRuleNamestringNo

The name of the traffic classification rule.

You can create up to 50 traffic classification rules at a time. You can specify a name for each traffic classification rule.

The name must be 2 to 128 characters in length, and can contain letters, digits, underscores (_), and hyphens (-). It must start with a letter.

Guangzhou Testing
DeleteTrafficMatchRulesobject []No

The traffic classification rules to be deleted from the traffic marking policy.

MatchDscpintegerNo

The DSCP value that is used to match packets.

3
DstCidrstringNo

The destination CIDR block that is used to match data packets.

192.168.200.3/32
TrafficMatchRuleDescriptionstringNo

The description of the traffic classification rule.

Hangzhou-to-Qingdao CAT
ProtocolstringNo

The protocol that is used to match packets.

Valid values: HTTP, HTTPS, TCP, UDP, SSH, and Telnet. For more information, log on to the Cloud Enterprise Network (CEN) console.

TCP
DstPortRangearrayNo

The destination port range that is used to match packets. Valid values: -1 and 1 to 65535.

integerNo

The destination port range that is used to match packets. Valid values: -1 and 1 to 65535.

-1
SrcCidrstringNo

The source CIDR block that is used to match packets.

10.72.0.0/16
SrcPortRangearrayNo

The source port range that is used to match packets. Valid values: -1 and 1 to 65535.

integerNo

The source port range that is used to match packets. Valid values: -1 and 1 to 65535.

23
TrafficMatchRuleNamestringNo

The name of the traffic classification rule.

test

Response parameters

ParameterTypeDescriptionExample
object

The response.

RequestIdstring

The ID of the request.

60BB11B2-7BF4-54DC-BCC9-F706E1EB02AC

Examples

Sample success responses

JSONformat

{
  "RequestId": "60BB11B2-7BF4-54DC-BCC9-F706E1EB02AC"
}

Error codes

HTTP status codeError codeError messageDescription
400InvalidTrafficMarkingPolicyId.NotFoundTrafficMarkingPolicyId is not found.The error message returned because the specified traffic marking policy ID (TrafficMarkingPolicyId) does not exist.
400IncorrectStatus.TrafficMarkingPolicyThe 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.
400Duplicated.AddTrafficMatchRulesThe parameter AddTrafficMatchRules are duplicated. -
400Duplicated.DeleteTrafficMatchRuleseThe parameter DeleteTrafficMatchRules are duplicated. -
400InstanceExist.AddTrafficMatchRulesThe instance already exists.The error message returned because the specified instance already exists.
400Duplicated.AddTrafficMatchRulesAndDeleteTrafficMatchRulesThe 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.
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.
404InvalidDeleteTrafficMatchRules.NotFoundThe 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 timeSummary of changesOperation
2023-09-08The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
    delete Error Codes: 404
2023-01-09The Error code has changed. The request parameters of the API has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
    delete Error Codes: 404
Input ParametersThe request parameters of the API has changed.
    Added Input Parameters: AddTrafficMatchRules
    Added Input Parameters: DeleteTrafficMatchRules
2021-11-26Add Operationsee changesets