Configuring an SR-MPLS TE Group to Implement Differentiated Services

After packet priority mapping is configured on the ingress node of an SR-MPLS TE tunnel, the internal priority obtained through mapping is the CoS of the packets. For details, see Configuring Priority Mapping in CloudEngine 12800 and 12800E Series Switches QoS Configuration Guide.

By default, the device maps the priority of original packets to the internal priority based on the mapping defined in the default domain.

1. Configure a traffic classifier.

   1. Run system-view

      The system view is displayed.

   2. Run traffic classifier classifier-name [ type { and | or } ]

      A traffic classifier is created and the traffic classifier view is displayed, or the view of an existing traffic classifier is displayed.

      and is the logical operator between rules in a traffic classifier, which means that:

      • If a traffic classifier contains ACL rules, packets match the traffic classifier only if they match one ACL rule and all the non-ACL rules.

      • If a traffic classifier does not contain any ACL rules, packets match the traffic classifier only if they match all the rules in the classifier.

      The logical operator or means that packets match a traffic classifier if they match one or more rules in the classifier.

      By default, the relationship between rules in a traffic classifier is or.

   3. Run if-match acl { acl-number | acl-name }

      An ACL is used to define a traffic classification rule, traffic classification is performed based on the IP 5-tuple information carried in packets.

      • If an ACL is used to define a traffic classification rule, configure the ACL first. In the ACL, you must specify the destination IP address of packets matching the ACL, and the mask length of the specified destination IP address must be greater than or equal to that of the destination network segment route.
      • If an ACL in a traffic classifier defines multiple rules, a packet matches the ACL as long as it matches one of the rules, regardless of whether the relationship between rules in the traffic classifier is AND or OR.

   4. Run commit

      The configuration is committed.

   5. Run quit

      Exit from the traffic classifier view.

2. Configure traffic behavior.

   1. Run traffic behavior behavior-name

      A traffic behavior is created and the traffic behavior view is displayed, or the existing traffic behavior view is displayed.

   2. Run remark local-precedence { local-precedence-name | local-precedence-value } [ green | yellow | red ]

      Packets matching the traffic classifier are re-marked with an internal precedence.

   3. Run commit

      The configuration is committed.

   4. Run quit

      Exit from the traffic behavior view.

3. Configure a traffic policy.

   1. Run traffic policy policy-name

      A traffic policy is created and the traffic policy view is displayed, or the view of an existing traffic policy is displayed.

   2. Run classifier classifier-name behavior behavior-name [ precedence precedence-value ]

      A traffic behavior is bound to a traffic classifier in the traffic policy.

   3. Run commit

      The configuration is committed.

   4. Run quit

      Exit from the traffic policy view.

4. Apply the traffic policy.

   • For details about the configuration guidelines of applying traffic policies in different views on the CE12800, see Licensing Requirements and Limitations for MQC (CE12800).

   • For details about the configuration guidelines of applying traffic policies in different views on the CE12800E, see Licensing Requirements and Limitations for MQC (CE12800E).

   • For the CE12800 and the CE12800E equipped with FD-X series cards, run the display traffic-policy pre-state { global [ slot slot-id ] | interface { interface-type interface-number } | vlan vlan-id | bridge-domain bd-id } policy-name { inbound | outbound } command before committing the configuration to check the information about resources occupied by the traffic policy to be applied and determine whether the traffic policy can be successfully applied based on the information.

   • If a traffic policy needs to be applied to multiple VLANs and interfaces or multiple traffic classifiers for matching packets from different source IP addresses need to be bound to the same traffic policy, you are advised to add these VLANs, source IP addresses, and interfaces to the same QoS group and apply the traffic policy to the QoS group.

   1. Run interface interface-type interface-number[.subinterface-number ]

      The interface view or layer 3 sub-interface view is displayed.

   2. Run traffic-policy policy-name inbound

      A traffic policy is applied to the interface in the inbound direction.

   3. Run commit

      The configuration is committed.