NetEngine AR600 AR6000 Series QoS Feature

NetEngine AR600，AR6000
Series QoS Feature
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Preface
 Quality of Service (QoS)
As the IP technology and network develops, the IP network

already changes from a single data network to a multi-service
network that integrates data, voice, video, and image services.
The AR needs to use the QoS technology to provide differentiated
services.
 QoS is the ability to provide a specified level of service, which can
be measured in delay, delay jitter, bandwidth, and packet
dropping probability during network communication.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 1

Objective
 Upon completion of this course, you will be able to:
 Understand the QoS principle.
 Understand the applicable scenarios of QoS.
 Learn about QoS fault location methods.

Contents
1. Principle and Implementation of QoS
2. Applicable Scenarios and Configuration Methods of QoS
3. QoS Troubleshooting

Contents

1.1 Service Models
1.2 Priority Mapping
1.3 QoS Policy
1.4 Traffic Policing
1.5 Traffic Shaping
1.6 Congestion Management
1.7 Congestion Avoidance
1.8 HQoS

1.1 Service Models
 Best Effort model
 IntServ model
 DiffServ model (used by the AR)

1.2 Priority Mapping
 Principle
 When packets enter the AR, the AR maps precedence fields of

the packets to local priorities based on the priority mapping table
or ACL rules.
 When packets leave the AR, the AR maps local priorities to

precedence fields of the packets or re-marks packet priorities so
that downstream devices can provide differentiated QoS based on
precedence fields of the packets.

1.2 Priority Mapping-QoS Priority
802.1p: A 3-bit priority field contained

in a VLAN tag represents the 802.1p
priority. The value ranges from 0 to 7.
Precedence: Bits 0 to 2 in the ToS

field represent the precedence field.
The value ranges from 0 to 7.
DSCP: Bits 0 to 5 are used to

distinguish DSCP priorities. The
value ranges from 0 to 63.
0 20 23 24 31
EXP: A 3-bit priority field represents
标签 EXP S TTL 32比特
the priority of MPLS packets. The
value ranges from 0 to 7.
2层头部 MPLS头部 IP头部数据

1.2 Priority Mapping-Priority Trusting Mode
 Trusting priorities of interfaces (By default, the priority

of an interface is trusted. The default priority of an
interface is 0.)
 Trusting DSCP priorities
 Trusting 802.1p priorities
 Trusting EXP priorities
 override

1.2 Priority Mapping-Mapping Table
 The AR supports the mappings between DSCP priorities and local priorities,
between DSCP priorities and 802.1p priorities, and between DSCP priorities
and EXP priorities. The mappings between DSCP priorities remain
unchanged.
 The AR supports the mappings between 802.1p priorities and local priorities,
between 802.1p priorities and DSCP priorities, and between 802.1p priorities
and EXP priorities. The mappings between 802.1p priorities remain
unchanged.
 The AR supports the mappings between EXP priorities and local priorities,
between EXP priorities and DSCP priorities, and between EXP priorities and
802.1p priorities. The mappings between EXP priorities remain unchanged.

1.3 QoS Policy
 A QoS policy provides a group of modular command line

configuration modes to integrate ACL-based QoS configuration
commands. It contains the following elements: traffic classifier,
traffic behavior, and traffic policy.
 Traffic classifier: defines matching rules to classify packets.
 Traffic behavior: is a set of actions taken for packets.
 Traffic policy: is a QoS policy in which traffic classifiers are bound

to traffic behaviors.

1.3 QoS Policy-Traffic Classifier
 A traffic classifier defines a group of matching rules to classify

packets.
 The traffic classifier identifies packets of a certain type by using

matching rules, and is the prerequisite and basis for providing
differentiated services.
 The relationship between rules in a traffic classifier can be AND or

OR. The default value is OR.

1.3 QoS Policy-Traffic Behavior
 A traffic behavior is a set of actions taken on packets. To provide

differentiated services, perform complex traffic classification. Complex
traffic classification takes effect only when it is associated with a traffic
control action or a resource allocation action.
 The AR supports the following traffic actions based on complex traffic

classification: permit/deny, re-marking, redirection, traffic policing, traffic
shaping, flow mirroring, traffic statistics, and queue scheduling. The traffic
actions except for deny can be used together.

1.3 QoS Policy-Traffic Policy
 A traffic policy is a QoS policy configured by binding traffic

classifiers to traffic behaviors.
 On the AR, a traffic policy can be applied to LAN-side interfaces,

WAN-side interfaces, or WAN-side sub-interfaces.
 A traffic policy can be applied to only one direction on an LPU, but

a traffic policy can be applied to different directions on different
LPUs.

1.4 Traffic Policing-Overview
Traffic policing discards excess traffic in order to limit the traffic within
a specified range and to protect network resources as well as the
carriers‘ interests. The AR uses CAR to perform traffic policing.
Packets to be sent Place tokens in the token bucket at the specified rate
from this interface
Continue to send packets
Classification
Token bucket
Discard packets

1.4 Traffic Policing-CAR Principle
 Meter: measures the network traffic using the token bucket mechanism and sends
the measurement result to the marker.
 Maker: colors packets based on the measurement result received from the meter.
Packets are colored green, yellow, or red.
 Action: performs actions based on packet coloring results received from the marker,
including:
pass: forwards the packets meeting the measurement result.
pass + remark: changes the internal priority of a packet and then forwards it.
discard: discards the packets that do not meet the measurement result.
By default, green and yellow packets are forwarded, whereas red packets are discarded.

1.4 Traffic Policing-Effect

1.5 Traffic Shaping-Overview
 When the rate of an interface on a downstream device is

slower than that of an interface on an upstream device or
burst traffic occurs, traffic congestion may occur on the
downstream device interface. Traffic shaping can be
configured on the interface of an upstream device so that
outgoing traffic is sent at even rates and congestion is
avoided.
 The AR supports level-3 traffic shaping.

1.5 Traffic Shaping-Process

1.5 Differences Between Traffic Shaping and
Traffic Policing

1.6 Congestion Management - Overview
 If a network transmitting both delay-sensitive and delay-insensitive

services is congested intermittently, congestion management is
required.
 The AR provides the following congestion management

techniques:
 LAN interface: PQ, DRR, PQ+DRR, WRR, and PQ+WRR
 WAN interface: PQ, WFQ, and PQ+WFQ

1.6 Congestion Management-PQ
 If PQ scheduling is used, packets in queues with lower priorities are

processed only after all the packets in queues with higher priority are
processed. By default, PQ scheduling is implemented for all queues.

1.6 Congestion Management-WRR
 Weighted Round Robin (WRR) ensures that packets in all the queues are
scheduled in turn. WRR schedules packets in queues based on the weight of
each queue. If the weight is set according to the number of packets, WRR is
used. If the weight is set according to the number of bytes of packets, Deficit
Round Robin (DRR) is used.
1.6 Congestion Management-WFQ
 Fair Queuing (FQ) ensures that network resources are allocated evenly to
optimize the delay and jitter of all flows. Compared with FQ, Weighted FQ
(WFQ) uses priorities to schedule packets.

1.7 Congestion Avoidance-Overview
 Congestion avoidance is a flow control mechanism. A system

configured with congestion avoidance monitors network resource
usage such as queues and memory buffers. When congestion
occurs or aggravates, the system discards packets.
 The AR provides the following congestion avoidance techniques:

tail drop and Weighted Random Early Detection (WRED).

1.7 Congestion Avoidance - Tail Drop
Tail drop: When the queue length is greater than the upper drop threshold,
excess packets (buffered at the queue tail) are discarded.
This policy may cause global TCP synchronization. As a result, TCP

connections cannot be set up. The three colors represent three TCP
connections. When packets from multiple TCP connections are discarded,
these TCP connections enter the congestion avoidance and slow start state.
Traffic reduces, and then reaches the peak. The volume of traffic varies greatly.
.

1.7 Congestion Avoidance- WRED
To avoid global TCP synchronization, Random Early Detection (RED) is used. The RED
mechanism randomly discards packets so that the transmission speed of multiple TCP
connections is not reduced simultaneously. In this manner, global TCP synchronization is
prevented. The rate of TCP traffic and network traffic become stable.
The AR provides WRED. WRED discards packets in queues based on DSCP priorities or
IP priorities. You can independently set the upper drop threshold, lower drop threshold, and
drop probability for different types of packets. When the number of packets reaches the
lower drop threshold, the AR starts to discard packets. When the number of packets
reaches the upper drop threshold, the AR discards all the packets. A higher threshold
indicates a high drop probability. The greatest drop probability cannot exceed the upper
drop threshold percentage. WRED discards packets in queues based on the drop
probability, preventing a certain degree of congestion.

1.8 HQoS
 Hierarchical QoS (HQoS) implements hierarchical scheduling

based on queues and differentiates services and users. It provides
QoS guarantee and saves network operation and maintenance
costs.

1.8 HQoS Queues

1.8 HQoS Mechanism
 HQoS schedulers: level-3 schedulers: level-3 flow queue (FQ)

scheduler, level-2 subscriber queue (SQ) scheduler, and level-1
port queue scheduler.
 HQoS shapers: level-3 shapers: level-3 FQ shaper, level-2 SQ

shaper, and level-1 port queue shaper.
 HQoS droppers:
 Port queue: tail drop
 Subscriber queue: tail drop
 Flow queue: tail drop and WRED

Contents

Contents

2.1 Example for Configuring Priority Mapping
2.2 Example for Configuring a QoS Policy
2.3 Example for Configuring traffic Policing
2.4 Example for Configuring Traffic Shaping
2.5 Example for Configuring Congestion Management and

Congestion Avoidance
2.6 Example for Configuring HQoS

2.1 Example for Configuring Priority Mapping -
Networking
 Voice, video, and data services on the LAN side are assigned different 802.1p
priorities.
 RouterB needs to provide differentiated services based on DSCP priorities.
 RouterA re-marks 802.1p priorities with DSCP priorities.

2.1 Example for Configuring Priority Mapping -
Configuration
# Configure Eth2/0/0 and Eth2/0/1 to trust 802.1p priorities in

packets.
[RouterA-Ethernet2/0/0] trust 8021p override
[RouterA-Ethernet2/0/1] trust 8021p override
# Configure priority mapping.

[RouterA] qos map-table dot1p-dscp
[RouterA-maptbl-dot1p-dscp] input 2 output 14

2.2 Example for Configuring a QOS Policy -
Networking
 The re-marking action is configured to re-mark 802.1p priorities with

DSCP priorities so that RouterA provides differentiated services based on
DSCP priorities in the packets.

2.2 Example for Configuring a QOS Policy -
Configuration
# Create and configure traffic classifiers c1, c2, and c3 on RouterA to classify packets based on
802.1p priorities.
[RouterA-classifier-c1] if-match 8021p 2
# Create and configure traffic behaviors b1, b2, and b3 on RouterA to re-mark 802.1p priorities of
packets.
[RouterA-behavior-b1] remark dscp 15
# Create a traffic policy p1 on RouterA, bind the configured traffic behaviors and traffic classifiers
to the traffic policy, and apply the traffic policy to Eth2/0/0 and Eth2/0/1 in the inbound direction.
[RouterA-trafficpolicy-p1] classifier c1 behavior b1
[RouterA-Ethernet2/0/0] traffic-policy p1 inbound

2.3 Example for Configuring Traffic Policing
- Networking
 Voice, video, and data services on the LAN side belong to different VLANs.
 RouterA performs flow-based traffic policing for different service packets.
 RouterA needs to limit the total traffic of a single enterprise user within a
proper range.

2.3 Example for Configuring Traffic Policing
- Configuration
# Configure traffic classifiers c1, c2, and c3 on RouterA to classify different service flows from the
enterprise based on the VLAN ID.
[RouterA-classifier-c1] if-match vlan-id 10
# Configure traffic behaviors b1, b2, and b3 on RouterA to perform traffic policing for different
service packets from the enterprise.
[RouterA-behavior-b1] car cir 256 cbs 48128 pbs 80128 green pass yellow pass red discard
[RouterA-behavior-b1] statistic enable
[RouterA-behavior-b2] car cir 4000 cbs 752000 pbs 1252000
[RouterA-behavior-b3] car cir 2000 cbs 376000 pbs 626000
# Create a traffic policy p1 on RouterA, bind the traffic policy to the traffic classifiers and the traffic
behaviors, and apply the traffic policy to the inbound direction of Eth2/0/0.
# Configure interface-based traffic policing in the inbound direction of Eth2/0/0 on RouterA in the
inbound direction to limit traffic of a single enterprise user within the proper range.
[RouterA-Ethernet2/0/0] qos car inbound cir 10000

- Networking
 The CIR value of the interface is 8000 kbit/s.

 The CIR value of voice services is 256 kbit/s and the CBS value is 6400 bytes.
 The CIR value of video services is 4000 kbit/s and the CBS value is 100000 bytes.
 The CIR value of video services is 2000 kbit/s and the CBS value is 50000 bytes.

- Configuration
# Configure Eth2/0/0 to trust 802.1p priorities in packets.
[RouterA-Ethernet2/0/0] trust 8021p
# Configure interface-based traffic shaping on RouterA and set the CIR value to 8000 kbit/s.
[RouterA-Ethernet3/0/0] qos gts cir 8000 cbs 200000
# Create a queue profile qp1 on RouterA, set the scheduling mode to WFQ for queues 0 to 5 and to
PQ for queue 6 and queue 7, set CIR values of queue 6, queue 5, and queue 2 to 256 kbit/s, 2000
kbit/s, and 4000 kbit/s, and set CBS values of queue 6, queue 5, and queue 2 to 6400 bytes, 50000
bytes, and 100000 bytes.
[RouterA] qos queue-profile qp1
[RouterA-qos-queue-profile-qp1] schedule pq 6 to 7 wfq 0 to 5
[RouterA-qos-queue-profile-qp1] queue 6 gts cir 256 cbs 6400
# Apply the queue profile qp1 to Eth3/0/0 on RouterA.

[RouterA-Ethernet3/0/0] qos queue-profile qp1

2.5 Example for Configuring Congestion
Management and Congestion Avoidance -
Networking
Service DSCP Queue Scheduling Drop Method

Voice 46 5 PQ Tail drop
Video 38 4 WFQ WRED:
Lower drop threshold (%): 60
Upper drop threshold (%): 80
Drop probability (%): 20
Data 28 3 WFQ WRED:
Lower drop threshold (%): 50
WRED:
26 Lower drop threshold (%): 40

2.5 Example for Configuring Congestion
Management and Congestion Avoidance -
Configuration
# Create drop profiles data and video on RouterA.
[RouterA] drop-profile data
[RouterA-drop-profile-data] wred dscp
[RouterA-drop-profile-data] dscp 28 low-limit 50 high-limit 70 discard-percentage 30
[RouterA-drop-profile-data] dscp 26 low-limit 40 high-limit 60 discard-percentage 40
[RouterA] drop-profile video
[RouterA-drop-profile-video] wred dscp
[RouterA-drop-profile-video] dscp 38 low-limit 60 high-limit 80 discard-percentage 20
# Create a queue profile queue-profile1 on RouterA and set the scheduling mode and drop mode
for each queue.
[RouterA] qos queue-profile queue-profile1
[RouterA-qos-queue-profile-queue-profile1] schedule pq 5 wfq 4 to 3
[RouterA-qos-queue-profile-queue-profile1] queue 4 drop-profile video
[RouterA-qos-queue-profile-queue-profile1] queue 3 drop-profile data
# Apply the queue profile to Eth3/0/0 of RouterA.

RouterA-Ethernet3/0/0] qos queue-profile queue-profile1

2.6 Example for Configuring HQoS-Networking

2.6 HQoS Policy - Configuration 1
# Create traffic classifiers data, video, and voice on the router to classify different service flows
from the enterprise based on DSCP priorities.
[Router-classifier-data] if-match dscp af11
[Router-classifier-video] if-match dscp af21
[Router-classifier-voice] if-match dscp ef
# Create drop profiles data and video on the router.
[Router] drop-profile data
[Router-drop-profile-data] wred dscp
[Router-drop-profile-data] dscp 10 low-limit 70 high-limit 85 discard-percentage 60
[Router] drop-profile video
[Router-drop-profile-video] wred dscp
[Router-drop-profile-video] dscp 18 low-limit 80 high-limit 95 discard-percentage 60

# Create traffic behaviors data, video, and voice on the router to configure congestion
management and congestion avoidance for different service flows of the enterprise.
[Router] traffic behavior data
[Router-behavior-data] queue af bandwidth pct 35
[Router-behavior-data] drop-profile data
[Router] traffic behavior video
[Router-behavior-video] queue af bandwidth pct 60
[Router-behavior-video] drop-profile video
[Router] traffic behavior voice
[Router-behavior-voice] queue ef bandwidth pct 5

# Define sub traffic policies for VPNA and VPNB on the router.
[Router] traffic policy vpna-sub
[Router-trafficpolicy-vpna-sub] classifier voice behavior voice
[Router-trafficpolicy-vpna-sub] classifier video behavior video
[Router-trafficpolicy-vpna-sub] classifier data behavior data
[Router] traffic policy vpnb-sub
[Router-trafficpolicy-vpnb-sub] classifier voice behavior voice
[Router-trafficpolicy-vpnb-sub] classifier video behavior video
[Router-trafficpolicy-vpnb-sub] classifier data behavior data

# Configure traffic classifiers vpna and vpnb on the router to classify different service flows from
the enterprise based on the VLAN ID.
[Router] traffic classifier vpna
[Router-classifier-vpna] if-match vlan-id 100
[Router] traffic classifier vpnb
[Router-classifier-vpnb] if-match vlan-id 200
# Create traffic behaviors vpna and vpnb on the router to shape packets from different VLANs and
bind them to sub traffic policies.
[Router] traffic behavior vpna
[Router-behavior-vpna] gts cir 20000
[Router-behavior-vpna] traffic-policy vpna-sub
[Router] traffic behavior vpnb
[Router-behavior-vpnb] gts cir 3000
[Router-behavior-vpnb] traffic-policy vpnb-sub

# Configure a traffic policy on the router.
[Router] traffic policy enterprise
[Router-trafficpolicy-enterprise] classifier vpna behavior vpna
[Router-trafficpolicy-enterprise] classifier vpnb behavior vpnb
# Apply the traffic policy on Eth3/0/0 of the router in the outbound direction.
[Router-Ethernet3/0/0] traffic-policy enterprise outbound

Contents

Contents
4.1 Priority Mapping Troubleshooting
4.2 QoS Policy Troubleshooting
4.3 Traffic Policing Troubleshooting
4.4 Traffic Shaping Troubleshooting
4.5 Congestion Management Troubleshooting
4.6 Congestion Avoidance Troubleshooting

4.1 Priority Mapping - Packets Enter
Incorrect Queues
 Packets enter incorrect queues in the following scenarios:
 Packets with different priorities enter the same queue.
 Packets with different priorities enter incorrect queues.
 Packets with the same priority enter an incorrect queue.
 Packets with the same priority enter different queues.
 This fault is commonly caused by one of the following:
 The type of the priority trusted by the inbound interface is incorrect.
 Priority mapping in the priority mapping table is incorrect.
 There are configurations affecting the queues that packets enter on the AR.

4.1 Priority Mapping - Packets Enter
Incorrect Queues

4.1 Priority Mapping - Priority Mapping
Results Are Incorrect
 Packets do not carry the priority trusted by the inbound interface.
 The parameter override is not configured in the trust command on the
inbound interface.
 Priority mapping in the priority mapping table is incorrect.
 There are configurations affecting priority mapping on the inbound interface.
 There are configurations affecting priority mapping on the outbound interface.

4.1 Priority Mapping - Priority Mapping
Results Are Incorrect

This fault is commonly caused by one of the following:

 The traffic policy fails to be applied. The causes are as follows:
 The system does not support rules or actions in the traffic policy.
 In the traffic policy, the rules or actions or rules and actions conflict.
 The number of traffic policies exceeds the specifications.
 The traffic policy conflicts with another applied traffic policy.
 The packets do not match the traffic policy. The causes are as follows:
 The traffic policy fails to be applied to an interface.
 The traffic policy is applied to an incorrect direction.
 The packets do not match rules of the traffic classifier in the traffic policy.
 The traffic behavior associated with the traffic classifier in the traffic policy is
configured incorrectly.

Traffic policy
fails to take
effect
Is traffic
policy applied Locate the fault Is fault rectified?
successfully?
Yes No
Configure a
Do packets
correct traffic
match the rule? Is fault rectified?
classification
rule
Yes No Yes
Is traffic Configure a
behavior set correct traffic Is fault rectified?
correctly? behavior
Yes No
Seek
technical End
support

 Interface-based traffic policing results are incorrect in the following

scenarios:
 Traffic policing does not take effect.
 Traffic policing results are incorrect.
 The qos car command is not used on the interface.
 Traffic policing is applied to an incorrect direction or CAR parameter values are
incorrect.
 Flow-based traffic policing and the qos car command are used in the same
direction and the CIR value for flow-based traffic policing is smaller than that
for interface-based traffic policing.


 Queue-based traffic shaping results are incorrect. This fault is commonly

caused by one of the following:
 Traffic shaping parameters are set incorrectly.
 The CIR value for interface-based traffic shaping is smaller than the sum of
CIR values for traffic shaping in queues on the interface. As a result, the
bandwidth required by queues cannot be ensured.
 Packets do not enter queues configured with traffic shaping because the
configuration is incorrect. For example, priority mapping is incorrect.
 Each queue uses the combined scheduling mode and excess packets enter
Priority Queuing (PQ) queues. As a result, other queues cannot obtain
sufficient bandwidth.


 Congestion management fails to take effect. This fault is commonly

caused by one of the following:
 Traffic shaping is not configured on the outbound interface.
 Congestion management is not configured on the outbound interface.
 Scheduling parameters are set incorrectly.
 Packets enter incorrect queues.


 Congestion avoidance fails to take effect. This fault is commonly caused

by one of the following:
 Congestion avoidance is not configured on the outbound interface.
 WRED parameters are set incorrectly.
 Packets enter incorrect queues.


Thank You
www.huawei.com

NetEngine AR600 AR6000 Series QoS Feature

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetEngine AR600 AR6000 Series QoS Feature

Uploaded by

Copyright:

Available Formats

NetEngine AR600，AR6000

Series QoS Feature

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

 Quality of Service (QoS)

As the IP technology and network develops, the IP network

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 1

 Upon completion of this course, you will be able to:

 Understand the QoS principle.

 Understand the applicable scenarios of QoS.

 Learn about QoS fault location methods.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

1. Principle and Implementation of QoS

2. Applicable Scenarios and Configuration Methods of QoS

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

1. Principle and Implementation of QoS

1.2 Priority Mapping

1.3 QoS Policy

1.4 Traffic Policing

1.5 Traffic Shaping

1.6 Congestion Management

1.7 Congestion Avoidance

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

 Best Effort model

 DiffServ model (used by the AR)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

 When packets enter the AR, the AR maps precedence fields of

 When packets leave the AR, the AR maps local priorities to

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

802.1p: A 3-bit priority field contained

Precedence: Bits 0 to 2 in the ToS

DSCP: Bits 0 to 5 are used to

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

 Trusting priorities of interfaces (By default, the priority

 Trusting DSCP priorities

 Trusting 802.1p priorities

 Trusting EXP priorities

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

 A QoS policy provides a group of modular command line

 Traffic classifier: defines matching rules to classify packets.

 Traffic behavior: is a set of actions taken for packets.

 Traffic policy: is a QoS policy in which traffic classifiers are bound

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

 A traffic classifier defines a group of matching rules to classify

 The traffic classifier identifies packets of a certain type by using

 The relationship between rules in a traffic classifier can be AND or

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

 A traffic behavior is a set of actions taken on packets. To provide

 The AR supports the following traffic actions based on complex traffic

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

 A traffic policy is a QoS policy configured by binding traffic

 On the AR, a traffic policy can be applied to LAN-side interfaces,

 A traffic policy can be applied to only one direction on an LPU, but

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

Continue to send packets

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

 When the rate of an interface on a downstream device is

 The AR supports level-3 traffic shaping.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19