The integrated service (IntServ) model is a multiple-service model that can accommodate diverse QoS requirements. This service model provides the most granularly differentiated QoS by identifying and guaranteeing definite QoS for each data flow.

In the IntServ model, an application must request service from the network before it sends data. IntServ signals the service request with the RSVP. All nodes receiving the request reserve resources as requested and maintain state information for the application flow.

The IntServ model demands high storage and processing capabilities because it requires all nodes along the transmission path to maintain resource state information for each flow. This model is suitable for small-sized or edge networks. However, it is not suitable for large-sized networks, for example, the core layer of the Internet, where billions of flows are present.

DiffServ model

The differentiated service (DiffServ) model is a multiple-service model that can meet diverse QoS requirements. It is easy to implement and extend. DiffServ does not signal the network to reserve resources before sending data, as IntServ does.

QoS techniques in a network

The QoS techniques include the following features:

· Traffic classification.

· Traffic policing.

· Traffic shaping.

· Rate limit.

· Congestion management.

· Congestion avoidance.

The following section briefly introduces these QoS techniques.

All QoS techniques in this document are based on the DiffServ model.

Figure 1 Position of the QoS techniques in a network

‌

As shown in Figure 1, traffic classification, traffic shaping, traffic policing, congestion management, and congestion avoidance mainly implement the following functions:

· Traffic classification—Uses match criteria to assign packets with the same characteristics to a traffic class. Based on traffic classes, you can provide differentiated services.

· Traffic policing—Polices flows and imposes penalties to prevent aggressive use of network resources. You can apply traffic policing to both incoming and outgoing traffic of a port.

· Traffic shaping—Adapts the output rate of traffic to the network resources available on the downstream device to eliminate packet drops. Traffic shaping usually applies to the outgoing traffic of a port.

· Congestion management—Provides a resource scheduling policy to determine the packet forwarding sequence when congestion occurs. Congestion management usually applies to the outgoing traffic of a port.

· Congestion avoidance—Monitors the network resource usage. It is usually applied to the outgoing traffic of a port. When congestion worsens, congestion avoidance reduces the queue length by dropping packets.

QoS processing flow in a device

Figure 2 briefly describes how the QoS module processes traffic.

1. Traffic classifier identifies and classifies traffic for subsequent QoS actions.

2. The QoS module takes various QoS actions on classified traffic as configured, depending on the traffic processing phase and network status. For example, you can configure the QoS module to perform the following operations:

¡ Traffic policing for incoming traffic.

¡ Traffic shaping for outgoing traffic.

¡ Congestion avoidance before congestion occurs.

¡ Congestion management when congestion occurs.

Figure 2 QoS processing flow

‌

QoS configuration approaches

You can configure QoS by using the MQC approach or non-MQC approach.

In the modular QoS configuration (MQC) approach, you configure QoS service parameters by using QoS policies. A QoS policy defines QoS actions to take on different classes of traffic and can be applied to an object (such as an interface) to control traffic.

In the non-MQC approach, you configure QoS service parameters without using a QoS policy. For example, you can use the rate limit feature to set a rate limit on an interface without using a QoS policy.

Some features support both approaches, but some support only one.

Configuring a QoS policy

About QoS policies

A QoS policy has the following components:

· Traffic class—Defines criteria to match packets.

· Traffic behavior—Defines QoS actions to take on matching packets.

By associating a traffic class with a traffic behavior, a QoS policy can perform the QoS actions on matching packets.

A QoS policy can have multiple class-behavior associations.

QoS policy tasks at a glance

To configure a QoS policy, perform the following tasks:

1. Defining a traffic class

2. Defining a traffic behavior

3. Defining a QoS policy

4. (Optional.) Configuring policy nesting

5. Applying the QoS policy

¡ Applying the QoS policy to an interface

¡ Applying the QoS policy to a PVC

¡ Applying the QoS policy to a PW

¡ Applying the QoS policy globally

¡ Applying the QoS policy to a control plane

¡ Applying the QoS policy in control-plane management view

¡ Applying the QoS policy to a user profile

6. (Optional.) Setting the QoS policy-based traffic rate statistics collection period for an interface

Defining a traffic class

1. Enter system view.

system-view

2. Create a traffic class and enter traffic class view.

traffic classifier classifier-name [ operator { and | or } ]

3. Configure a match criterion.

if-match [ not ] match-criteria

By default, no match criterion is configured.

For more information, see the if-match command in ACL and QoS Command Reference.

Defining a traffic behavior

1. Enter system view.

system-view

2. Create a traffic behavior and enter traffic behavior view.

traffic behavior behavior-name

3. Configure an action in the traffic behavior.

By default, no action is configured for a traffic behavior.

For more information about configuring an action, see the subsequent chapters for traffic policing, traffic filtering, priority marking, class-based accounting, and so on.

Defining a QoS policy

1. Enter system view.

system-view

2. Create a QoS policy and enter QoS policy view.

qos policy policy-name

3. Associate a traffic class with a traffic behavior to create a class-behavior association in the QoS policy.

classifier classifier-name behavior behavior-name [ mode { dcbx | qppb-manipulation } | insert-before before-classifier-name ] *

By default, a traffic class is not associated with a traffic behavior.

Repeat this step to create more class-behavior associations.

Parameter	Description
dcbx	Specifies that a class-behavior association applies only to DCBX. For more information about DCBX, see Layer 2—LAN Switching Configuration Guide.
qppb-manipulation	Specifies that a class-behavior association applies only to matching the apply qos-local-id command configuration in a BGP routing policy. For more information, see Layer 3—IP Routing Configuration Guide. Support for the mode qppb-manipulation keyword depends on the device model.

‌

Configuring policy nesting

About this task

A QoS policy configuration can contain a parent policy and a child policy.

Policy nesting allows you to create a child policy in the view of a traffic behavior of the parent policy.

You can nest a QoS policy in a traffic behavior to reclassify the traffic class associated with the behavior. Then the system performs the actions defined in the QoS policy on the reclassified traffic. The QoS policy nested in the traffic behavior is called the child policy. The QoS policy that nests the behavior is called the parent policy.

Restrictions and guidelines

When you configure policy nesting, follow these restrictions and guidelines:

· If class-based queuing (CBQ) is configured in a child policy, make sure the following requirements are met:

¡ GTS is configured in the parent policy.

¡ The CIR specified in GTS is greater than or equal to CBQ bandwidth.

· If the CIR in GTS is specified as a percentage for a parent policy, configure the CBQ bandwidth as a percentage for the child policy.

· If the CIR in GTS is specified in kbps for a parent policy, configure the CBQ bandwidth as a percentage or in kbps for the child policy.

· GTS cannot be configured in the child policy.

Prerequisites

Before configuring policy nesting, define a child policy (see "Defining a QoS policy").

Procedure

1. Enter system view.

system-view

2. Define a traffic class for the parent policy.

a. Create a traffic class for the parent policy and enter traffic class view.

traffic classifier classifier-name [ operator { and | or } ]

b. Configure a match criterion.

if-match [ not ] match-criteria

By default, no match criterion is configured.

For more information about configuring match criteria, see ACL and QoS Command Reference.

c. Return to system view.

quit

3. Nest the child QoS policy in the traffic behavior of the parent policy.

a. Create a traffic behavior for the parent policy and enter traffic behavior view.

traffic behavior behavior-name

b. Nest the child QoS policy.

traffic-policy policy-name

By default, policy nesting is not configured.

c. Return to system view.

quit

4. Create the parent policy and enter parent policy view.

qos policy policy-name

5. Associate the class with the behavior in the parent policy.

classifier classifier-name behavior behavior-name

By default, a class is not associated with a behavior.

Applying the QoS policy

Application destinations

You can apply a QoS policy to the following destinations:

· Interface—The QoS policy takes effect on the traffic sent or received on the interface.

· PVC—The QoS policy takes effect on the traffic sent or received on the PVC. For information about PVCs, see Layer 2—WAN Access Configuration Guide.

· PW—The QoS policy takes effect on the traffic of a PW. For information about PWs, see MPLS Configuration Guide.

· Control plane—The QoS policy takes effect on the traffic received on the control plane.

· Management interface control plane—The QoS policy takes effect on the traffic sent from the management interface to the control plane.

· User profile—The QoS policy takes effect on the traffic sent or received by the online users of the user profile.

Restrictions and guidelines for applying a QoS policy

You can modify traffic classes, traffic behaviors, and class-behavior associations in a QoS policy even after it is applied (except that it is applied to a user profile). If a traffic class uses an ACL for traffic classification, you can delete or modify the ACL.

Applying the QoS policy to an interface

Restrictions and guidelines

A QoS policy configured with a preorder-value is executed before a QoS policy that is not configured with a preorder-value.

For multiple QoS policies with the same action type applied to the same direction of an interface, the behavior in the QoS policy applied with the preorder preorder-value option is executed

The QoS policy applied to the outgoing traffic on an interface does not regulate local packets. Local packets refer to critical protocol packets sent by the local system for operation maintenance. The most common local packets include link maintenance, RIP, LDP, and SSH packets.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Apply the QoS policy to the interface.

qos apply policy policy-name { inbound | outbound } [ preorder preorder-value ]

By default, no QoS policy is applied to an interface.

Applying the QoS policy to a PVC

Restrictions and guidelines

A QoS policy can be applied to multiple PVCs. However, only one QoS policy can be applied to one direction (inbound or outbound) of a PVC.

The QoS policy applied to the outgoing traffic on a PVC does not regulate local packets. Local packets refer to critical protocol packets sent by the local system for operation maintenance. The most common local packets include link maintenance, routing, LDP, RSVP, and SSH packets.

Procedure

1. Enter system view.

system-view

2. Execute the following commands in sequence to enter PVC view:

interface atm interface-number

pvc vpi/vci

3. Apply the QoS policy to the PVC.

qos apply policy policy-name { inbound | outbound }

By default, no QoS policy is applied to a PVC.

Applying the QoS policy to a PW

Restrictions and guidelines

You can apply a QoS policy to one or more PWs only in the outbound direction.

Procedure

1. Enter system view.

system-view

2. Enter PW view.

¡ Execute the following commands in sequence to enter cross-connect PW view:

xconnect-group group-name

connection connection-name

peer ip-address pw-id pw-id [ in-label label-value out-label label-value ] [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

¡ Execute the following commands in sequence to enter VSI LDP PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling ldp

peer ip-address [ pw-id pw-id ] [ hub | no-split-horizon ] [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

¡ Execute the following commands in sequence to enter VSI static PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling static

peer ip-address [ pw-id pw-id ] [ in-label label-value out-label label-value [ hub | no-split-horizon | pw-class class-name | tunnel-policy tunnel-policy-name ] * ]

3. Apply the QoS policy to the PW.

qos apply policy policy-name outbound

By default, no QoS policy is applied to a PW.

Applying the QoS policy globally

About this task

You can apply a QoS policy globally to the inbound or outbound direction of all ports.

Restrictions and guidelines

When you apply a QoS policy globally, the QoS policy is applied on all interface cards. If the hardware resources of an interface card are insufficient, applying a QoS policy globally might fail on the interface card. The system does not automatically roll back the QoS policy configuration already applied to other interface cards. To ensure consistency, you must use the undo qos apply policy global command to manually remove the QoS policy configuration applied to them.

Procedure

1. Enter system view.

system-view

2. Apply the QoS policy globally.

qos apply policy policy-name global { inbound | outbound } [ preorder preorder-value ]

By default, no QoS policy is applied globally.

Applying the QoS policy to a control plane

About this task

A device provides the user plane and the control plane.

· User plane—The units at the user plane are responsible for receiving, transmitting, and switching (forwarding) packets, such as various dedicated forwarding chips. They deliver super processing speeds and throughput.

· Control plane—The units at the control plane are processing units running most routing and switching protocols. They are responsible for protocol packet resolution and calculation, such as CPUs. Compared with user plane units, the control plane units allow for great packet processing flexibility but have lower throughput.

When the user plane receives packets that it cannot recognize or process, it transmits them to the control plane. If the transmission rate exceeds the processing capability of the control plane, the control plane will be busy handling undesired packets. As a result, the control plane will fail to handle legitimate packets correctly or timely. As a result, protocol performance is affected.

To address this problem, apply a QoS policy to the control plane to take QoS actions, such as traffic filtering or traffic policing, on inbound traffic. This ensures that the control plane can correctly receive, transmit, and process packets.

A predefined control plane QoS policy uses the protocol type or protocol group type to identify the type of packets sent to the control plane. You can use protocol types or protocol group types in if-match commands in traffic class view for traffic classification. Then you can reconfigure traffic behaviors for these traffic classes as required. You can use the display qos policy control-plane pre-defined command to display predefined control plane QoS policies.

Procedure

1. Enter system view.

system-view

2. Enter control plane view.

In standalone mode:

control-plane slot slot-number

In IRF mode:

control-plane chassis chassis-number slot slot-number

3. Apply the QoS policy to the control plane.

qos apply policy policy-name inbound

By default, no QoS policy is applied to a control plane.

Applying the QoS policy in control-plane management view

About this task

If the rate of packets from the management interface to the control plane exceeds the processing capability, the control plane will fail to handle the packets correctly or timely. As a result, protocol performance is affected.

This feature allows you to rate limit the packets sent from the management interface to the control plane. This ensures that the control plane can correctly receive, transmit, and process packets from the management interface.

By default, a predefined QoS policy is applied in control-plane management view. To display the predefined QoS policy, use the display qos policy control-plane management pre-defined command. The predefined QoS policy uses the protocol type or protocol group type to identify the type of packets sent from the management interface to the control plane. You can use protocol types or protocol group types in if-match commands in traffic class view for traffic classification. Then, you can reconfigure traffic behaviors for these traffic classes as required.

Procedure

1. Enter system view.

system-view

2. Enter control-plane management view.

control-plane management

3. Apply the QoS policy.

qos apply policy policy-name inbound

By default, no QoS policy is applied in control-plane management view.

Applying the QoS policy to a user profile

About this task

Restrictions and guidelines

You can apply a QoS policy to multiple user profiles. In one direction of each user profile, only one policy can be applied. To modify a QoS policy already applied to a direction, first remove the applied QoS policy.

Procedure

1. Enter system view.

system-view

2. Enter user profile view.

user-profile profile-name

3. Apply the QoS policy to the user profile.

qos apply policy policy-name { inbound | outbound }

By default, no QoS policy is applied to a user profile.

Parameter	Description
inbound	Applies a QoS policy to the traffic received by the device from the user profile.
outbound	Applies a QoS policy to the traffic sent by the device to the user profile.

Setting the QoS policy-based traffic rate statistics collection period for an interface

About this task

You can enable collection of per-class traffic statistics over a period of time, including the average forwarding rate and drop rate. For example, if you set the statistics collection period to n minutes, the system performs the following operations:

· Collects traffic statistics for the most recent n minutes.

· Refreshes the statistics every n/5 minutes.

You can use the display qos policy interface command to view the collected traffic rate statistics.

Restrictions and guidelines

When you set the QoS policy-based traffic rate statistics collection period, follow these restrictions and guidelines:

· A subinterface uses the statistics collection period configured on the main interface.

· A PVC uses the statistics collection period configured on the ATM main interface.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Set the traffic rate statistics collection period for the interface.

qos flow-interval interval

The default setting is 5 minutes.

Display and maintenance commands for QoS policies

Execute display commands in any view and reset commands in user view.

Task	Command
Display QoS policy configuration.	In standalone mode: display qos policy { system-defined \| user-defined } [ policy-name [ classifier classifier-name ] ] [ slot slot-number ] In IRF mode: display qos policy { system-defined \| user-defined } [ policy-name [ classifier classifier-name ] ] [ chassis chassis-number slot slot-number ]
Display QoS policies applied to hub-spoke tunnels on a tunnel interface.	display qos policy advpn tunnel number [ ipv4-address \| ipv6-address ] [ outbound ]
Display information about QoS policies applied to the control plane.	In standalone mode: display qos policy control-plane slot slot-number In IRF mode: display qos policy control-plane chassis chassis-number slot slot-number
Display information about QoS policies applied in control-plane management view.	display qos policy control-plane management
Display information about the predefined QoS policy applied in control-plane management view.	display qos policy control-plane management pre-defined
Display information about the predefined QoS policy applied to the control plane.	In standalone mode: display qos policy control-plane pre-defined [ slot slot-number ] In IRF mode: display qos policy control-plane pre-defined [ chassis chassis-number slot slot-number ]
Display information about QoS policies applied globally.	In standalone mode: display qos policy global [ slot slot-number ] [ inbound \| outbound ] In IRF mode: display qos policy global [ chassis chassis-number slot slot-number ] [ inbound \| outbound ]
Display information about QoS policies applied to interfaces.	In standalone mode: display qos policy interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ] [ slot slot-number [ cpu cpu-number ] ] [ inbound \| outbound ] In IRF mode: display qos policy interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ] [ chassis chassis-number slot slot-number ] [ inbound \| outbound ]
Display information about QoS policies applied to PWs.	display qos policy l2vpn-pw [ peer ip-address pw-id pw-id ] [ outbound ]
Display information about QoS policies applied to user profiles.	In standalone mode: display qos policy user-profile [ name profile-name ] [ user-id user-id ] [ slot slot-number ] [ inbound \| outbound ] In IRF mode: display qos policy user-profile [ name profile-name ] [ user-id user-id ] [ chassis chassis-number slot slot-number ] [ inbound \| outbound ]
Display QoS and ACL resource usage.	In standalone mode: display qos-acl resource [ slot slot-number ] In IRF mode: display qos-acl resource [ chassis chassis-number slot slot-number ]
Display traffic behavior configuration.	In standalone mode: display traffic behavior { system-defined \| user-defined } [ behavior-name ] [ slot slot-number ] In IRF mode: display traffic behavior { system-defined \| user-defined } [ behavior-name ] [ chassis chassis-number slot slot-number ]
Display traffic class configuration.	In standalone mode: display traffic classifier { system-defined \| user-defined } [ classifier-name ] [ slot slot-number ] In IRF mode: display traffic classifier { system-defined \| user-defined } [ classifier-name ] [ chassis chassis-number slot slot-number ]
Clear the statistics for the QoS policy applied to the control plane.	In standalone mode: reset qos policy control-plane slot slot-number In IRF mode: reset qos policy control-plane chassis chassis-number slot slot-number
Clear the statistics for QoS policies applied to hub-spoke tunnels on a tunnel interface.	reset qos policy advpn tunnel number [ ipv4-address \| ipv6-address ] [ outbound ]
Clear the statistics for the QoS policy applied in control-plane management view.	reset qos policy control-plane management
Clear the statistics for a QoS policy applied globally.	reset qos policy global [ inbound \| outbound ]

Configuring priority mapping

About priority mapping

When a packet arrives, a device assigns a set of QoS priority parameters to the packet based on either of the following:

· A priority field carried in the packet.

· The port priority of the incoming port.

This process is called priority mapping. During this process, the device can modify the priority of the packet according to the priority mapping rules. The set of QoS priority parameters decides the scheduling priority and forwarding priority of the packet.

Priority mapping is implemented with priority maps and involves the following priorities:

· 802.11e priority.

· 802.1p priority.

· DSCP.

· EXP.

· IP precedence.

· Local precedence.

· Drop priority.

About priorities

Priorities include the following types: priorities carried in packets, and priorities locally assigned for scheduling only.

Packet-carried priorities include 802.1p priority, DSCP precedence, IP precedence, and EXP. These priorities have global significance and affect the forwarding priority of packets across the network. For more information about these priorities, see "Appendix C Introduction to packet precedence."

Locally assigned priorities only have local significance. They are assigned by the device only for scheduling. These priorities include the local precedence, drop priority, and user priority, as follows:

· Local precedence—Used for queuing. A local precedence value corresponds to an output queue. A packet with higher local precedence is assigned to a higher priority output queue to be preferentially scheduled.

· Drop priority—Used for making packet drop decisions. Packets with the highest drop priority are dropped preferentially.

· User priority—Precedence that the device automatically extracts from a priority field of the packet according to its forwarding path. It is a parameter for determining the scheduling priority and forwarding priority of the packet. The user priority represents the following items:

¡ The 802.1p priority for Layer 2 packets.

¡ The IP precedence for Layer 3 packets.

¡ The EXP for MPLS packets.

Priority maps

The device provides various types of priority maps. By looking through a priority map, the device decides which priority value to assign to a packet for subsequent packet processing.

The default priority maps (as shown in Appendix B Default priority maps) are available for priority mapping. They are adequate in most cases. If a default priority map cannot meet your requirements, you can modify the priority map as required.

Priority mapping configuration methods

You can configure priority mapping by using any of the following methods:

· Configuring priority trust mode—In this method, you can configure a port to look up a trusted priority type (802.1p, for example) in incoming packets in the priority maps. Then, the system maps the trusted priority to the target priority types and values.

· Changing port priority—If no packet priority is trusted, the port priority of the incoming port is used. By changing the port priority of a port, you change the priority of the incoming packets on the port.

· Configuring a QoS policy containing the priority mapping (called primap) action with the primap command.

Priority mapping process

On receiving an Ethernet packet on a port, the switch marks the scheduling priorities (local precedence and drop precedence) for the Ethernet packet. This procedure is done according to the priority trust mode of the receiving port and the 802.1Q tagging status of the packet, as shown in Figure 3.

Figure 3 Priority mapping process for an Ethernet packet

The switch marks a received MPLS packet with a scheduling priority based on the priority trust mode and the packet EXP value, as shown in Figure 4.

Figure 4 Priority mapping process for an MPLS packet

For information about priority marking, see "Configuring priority marking."

Priority mapping tasks at a glance

To configure priority mapping, perform the following tasks:

1. (Optional.) Configuring a priority map

2. Configuring a priority mapping method:

¡ Configuring a port to trust packet priority for priority mapping

¡ Changing the port priority of an interface

Configuring a priority map

1. Enter system view.

system-view

2. Enter priority map view.

qos map-table { dot1p-lp | dscp-lp | lp-dot1p }

3. Configure mappings for the priority map.

import import-value-list export export-value

By default, the default priority maps are used. For more information, see "Appendix B Default priority maps."

If you execute this command multiple times, the most recent configuration takes effect.

Configuring a port to trust packet priority for priority mapping

About this task

You can configure the device to trust a particular priority field carried in packets for priority mapping on ports or globally. When you configure the trusted packet priority type on an interface, use the following available keywords:

· dot1p—Uses the 802.1p priority of received packets for mapping.

· dscp—Uses the DSCP precedence of received IP packets for mapping.

· none—Trusts no priority.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Configure the trusted packet priority type.

qos trust { dot1p | dscp | none } [ override ]

By default, an interface does not trust any packet priority and uses the port priority as the 802.1p priority for mapping.

4. Return to system view.

quit

Changing the port priority of an interface

About this task

If an interface does not trust any packet priority, the device uses its port priority to look for priority parameters for the incoming packets. By changing port priority, you can prioritize traffic received on different interfaces.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Set the port priority of the interface.

qos priority [ dot1p | dp | dscp | exp | lp ] priority-value

The default setting is 2 for lp and 0 for dp. Other priority types do not have default settings.

Display and maintenance commands for priority mapping

Execute display commands in any view.

Task	Command
Display priority map configuration.	display qos map-table [ dot1p-lp \| dscp-lp \| lp-dot1p ]
Display the trusted packet priority type on a port.	display qos trust interface [ interface-type interface-number ]

Priority mapping configuration examples

Example: Configuring a priority trust mode

Network configuration

As shown in Figure 5:

· The 802.1p priority of traffic from Device A to Device C is 3.

· The 802.1p priority of traffic from Device B to Device C is 1.

Configure Device C to preferentially process packets from Device A to the server when GigabitEthernet 2/0/3 of Device C is congested.

Figure 5 Network diagram

‌

Procedure

(Method 1) Configure Device C to trust packet priority

# Configure GigabitEthernet 2/0/1 and GigabitEthernet 2/0/2 to trust the 802.1p priority for priority mapping.

<DeviceC> system-view

[DeviceC] interface gigabitethernet 2/0/1

[DeviceC-GigabitEthernet2/0/1] qos trust dot1p

[DeviceC-GigabitEthernet2/0/1] quit

[DeviceC] interface gigabitethernet 2/0/2

[DeviceC-GigabitEthernet2/0/2] qos trust dot1p

[DeviceC-GigabitEthernet2/0/2] quit

(Method 2) Configure Device C to trust port priority

# Assign port priority to GigabitEthernet 2/0/1 and GigabitEthernet 2/0/2. Make sure the following requirements are met:

· The priority of GigabitEthernet 2/0/1 is higher than that of GigabitEthernet 2/0/2.

· No trusted packet priority type is configured on GigabitEthernet 2/0/1 or GigabitEthernet 2/0/2.

<DeviceC> system-view

[DeviceC] interface gigabitethernet 2/0/1

[DeviceC-GigabitEthernet2/0/1] qos priority 3

[DeviceC-GigabitEthernet2/0/1] quit

[DeviceC] interface gigabitethernet 2/0/2

[DeviceC-GigabitEthernet2/0/2] qos priority 1

[DeviceC-GigabitEthernet2/0/2] quit

Example: Configuring priority mapping tables and priority marking

Network configuration

As shown in Figure 6:

· The Marketing department connects to GigabitEthernet 2/0/1 of Device, which sets the 802.1p priority of traffic from the Marketing department to 3.

· The R&D department connects to GigabitEthernet 2/0/2 of Device, which sets the 802.1p priority of traffic from the R&D department to 4.

· The Management department connects to GigabitEthernet 2/0/3 of Device, which sets the 802.1p priority of traffic from the Management department to 5.

Configure port priority, 802.1p-to-local mapping table, and priority marking to implement the plan as described in Table 1.

Table 1 Configuration plan

Traffic destination	Traffic priority order	Queuing plan
Traffic destination	Traffic priority order	Traffic source	Output queue	Queue priority
Public servers	R&D department > Management department > Marketing department	R&D department	6	High
		Management department	4	Medium
		Marketing department	2	Low
Internet	Management department > Marketing department > R&D department	R&D department	2	Low
		Management department	6	High
		Marketing department	4	Medium

Figure 6 Network diagram

‌

Procedure

1. Configure trusting port priority:

# Set the port priority of GigabitEthernet 2/0/1 to 3.

<Device> system-view

[Device] interface gigabitethernet 2/0/1

[Device-GigabitEthernet2/0/1] qos priority 3

[Device-GigabitEthernet2/0/1] quit

# Set the port priority of GigabitEthernet 2/0/2 to 4.

[Device] interface gigabitethernet 2/0/2

[Device-GigabitEthernet2/0/2] qos priority 4

[Device-GigabitEthernet2/0/2] quit

# Set the port priority of GigabitEthernet 2/0/3 to 5.

[Device] interface gigabitethernet 2/0/3

[Device-GigabitEthernet2/0/3] qos priority 5

[Device-GigabitEthernet2/0/3] quit

2. Configure the 802.1p-to-local mapping table to map 802.1p priority values 3, 4, and 5 to local precedence values 2, 6, and 4.

This guarantees the R&D department, Management department, and Marketing department decreased priorities to access the public servers.

[Device] qos map-table dot1p-lp

[Device-maptbl-dot1p-lp] import 3 export 2

[Device-maptbl-dot1p-lp] import 4 export 6

[Device-maptbl-dot1p-lp] import 5 export 4

[Device-maptbl-dot1p-lp] quit

3. Configure priority marking to mark the packets from Management department, Marketing department, and R&D department to the Internet with 802.1p priority values 4, 5, and 3.

This guarantees the Management department, Marketing department, and R&D department decreased priorities to access the Internet.

# Create ACL 3000, and configure a rule to match HTTP packets.

[Device] acl advanced 3000

[Device-acl-adv-3000] rule permit tcp destination-port eq 80

[Device-acl-adv-3000] quit

# Create a traffic class named http, and use ACL 3000 as a match criterion.

[Device] traffic classifier http

[Device-classifier-http] if-match acl 3000

[Device-classifier-http] quit

# Create a traffic behavior named admin, and configure a marking action for the Management department.

[Device] traffic behavior admin

[Device-behavior-admin] remark dot1p 4

[Device-behavior-admin] quit

# Create a QoS policy named admin, and associate traffic class http with traffic behavior admin in QoS policy admin.

[Device] qos policy admin

[Device-qospolicy-admin] classifier http behavior admin

[Device-qospolicy-admin] quit

# Apply QoS policy admin to the inbound direction of GigabitEthernet 2/0/3.

[Device] interface gigabitethernet 2/0/3

[Device-GigabitEthernet2/0/3] qos apply policy admin inbound

# Create a traffic behavior named market, and configure a marking action for the Marketing department.

[Device] traffic behavior market

[Device-behavior-market] remark dot1p 5

[Device-behavior-market] quit

# Create a QoS policy named market, and associate traffic class http with traffic behavior market in QoS policy market.

[Device] qos policy market

[Device-qospolicy-market] classifier http behavior market

[Device-qospolicy-market] quit

# Apply QoS policy market to the inbound direction of GigabitEthernet 2/0/1.

[Device] interface gigabitethernet 2/0/1

[Device-GigabitEthernet2/0/1] qos apply policy market inbound

# Create a traffic behavior named rd, and configure a marking action for the R&D department.

[Device] traffic behavior rd

[Device-behavior-rd] remark dot1p 3

[Device-behavior-rd] quit

# Create a QoS policy named rd, and associate traffic class http with traffic behavior rd in QoS policy rd.

[Device] qos policy rd

[Device-qospolicy-rd] classifier http behavior rd

[Device-qospolicy-rd] quit

# Apply QoS policy rd to the inbound direction of GigabitEthernet 2/0/2.

[Device] interface gigabitethernet 2/0/2

[Device-GigabitEthernet2/0/2] qos apply policy rd inbound

Configuring traffic policing, GTS, and rate limit

About traffic policing, GTS, and rate limit

Traffic limit helps assign network resources (including bandwidth) and increase network performance. For example, you can configure a flow to use only the resources committed to it in a certain time range. This avoids network congestion caused by burst traffic.

Traffic policing, Generic Traffic Shaping (GTS), and rate limit control the traffic rate and resource usage according to traffic specifications. You can use token buckets for evaluating traffic specifications.

Traffic evaluation and token buckets

Token bucket features

A token bucket is analogous to a container that holds a certain number of tokens. Each token represents a certain forwarding capacity. The system puts tokens into the bucket at a constant rate. When the token bucket is full, the extra tokens cause the token bucket to overflow.

Evaluating traffic with the token bucket

A token bucket mechanism evaluates traffic by looking at the number of tokens in the bucket. If the number of tokens in the bucket is enough for forwarding the packets:

· The traffic conforms to the specification (called conforming traffic).

· The corresponding tokens are taken away from the bucket.

Otherwise, the traffic does not conform to the specification (called excess traffic).

A token bucket has the following configurable parameters:

· Mean rate at which tokens are put into the bucket, which is the permitted average rate of traffic. It is usually set to the committed information rate (CIR).

· Burst size or the capacity of the token bucket. It is the maximum traffic size permitted in each burst. It is usually set to the committed burst size (CBS). The set burst size must be greater than the maximum packet size.

Each arriving packet is evaluated.

Complicated evaluation

You can set two token buckets, bucket C and bucket E, to evaluate traffic in a more complicated environment and achieve more policing flexibility. The following are main mechanisms used for complicated evaluation:

· Single rate two color—Uses one token bucket and the following parameters:

¡ CIR—Rate at which tokens are put into bucket C. It sets the average packet transmission or forwarding rate allowed by bucket C.

¡ CBS—Size of bucket C, which specifies the transient burst of traffic that bucket C can forward.

When a packet arrives, the following rules apply:

¡ If bucket C has enough tokens to forward the packet, the packet is colored green.

¡ Otherwise, the packet is colored red.

· Single rate three color—Uses two token buckets and the following parameters:

¡ CIR—Rate at which tokens are put into bucket C. It sets the average packet transmission or forwarding rate allowed by bucket C.

¡ CBS—Size of bucket C, which specifies the transient burst of traffic that bucket C can forward.

¡ EBS—Size of bucket E minus size of bucket C, which specifies the transient burst of traffic that bucket E can forward. The EBS cannot be 0. The size of E bucket is the sum of the CBS and EBS.

When a packet arrives, the following rules apply:

¡ If bucket C has enough tokens, the packet is colored green.

¡ If bucket C does not have enough tokens but bucket E has enough tokens, the packet is colored yellow.

¡ If neither bucket C nor bucket E has sufficient tokens, the packet is colored red.

· Two rate three color—Uses two token buckets and the following parameters:

¡ CIR—Rate at which tokens are put into bucket C. It sets the average packet transmission or forwarding rate allowed by bucket C.

¡ CBS—Size of bucket C, which specifies the transient burst of traffic that bucket C can forward.

¡ PIR—Rate at which tokens are put into bucket E, which specifies the average packet transmission or forwarding rate allowed by bucket E.

¡ EBS—Size of bucket E, which specifies the transient burst of traffic that bucket E can forward.

When a packet arrives, the following rules apply:

¡ If bucket C has enough tokens, the packet is colored green.

¡ If bucket C does not have enough tokens but bucket E has enough tokens, the packet is colored yellow.

¡ If neither bucket C nor bucket E has sufficient tokens, the packet is colored red.

Traffic policing

Traffic policing supports policing the inbound traffic and the outbound traffic.

A typical application of traffic policing is to supervise the specification of traffic entering a network and limit it within a reasonable range. Another application is to "discipline" the extra traffic to prevent aggressive use of network resources by an application. For example, you can limit bandwidth for HTTP packets to less than 50% of the total. If the traffic of a session exceeds the limit, traffic policing can drop the packets or reset the IP precedence of the packets. Figure 7 shows an example of policing outbound traffic on an interface.

Figure 7 Traffic policing

Traffic policing is widely used in policing traffic entering the ISP networks. It can classify the policed traffic and take predefined policing actions on each packet depending on the evaluation result:

· Forwarding the packet if the evaluation result is "conforming."

· Dropping the packet if the evaluation result is "excess."

· Forwarding the packet with its precedence re-marked if the evaluation result is "conforming."

· Delivering the packet to next-level traffic policing with its precedence re-marked if the evaluation result is "conforming."

· Entering the next-level policing (you can set multiple traffic policing levels, each focused on objects at different levels).

GTS

GTS supports shaping the outbound traffic. GTS limits the outbound traffic rate by buffering exceeding traffic. You can use GTS to adapt the traffic output rate on a device to the input traffic rate of its connected device to avoid packet loss.

The differences between traffic policing and GTS are as follows:

· Packets to be dropped with traffic policing are retained in a buffer or queue with GTS, as shown in Figure 8. When enough tokens are in the token bucket, the buffered packets are sent at an even rate.

· GTS can result in additional delay and traffic policing does not.

Figure 8 GTS

For example, in Figure 9, Device B performs traffic policing on packets from Device A and drops packets exceeding the limit. To avoid packet loss, you can perform GTS on the outgoing interface of Device A so that packets exceeding the limit are cached in Device A. Once resources are released, GTS takes out the cached packets and sends them out.

Figure 9 GTS application

‌

Rate limit

Rate limit controls the rate of inbound and outbound traffic. The outbound traffic is taken for example.

The rate limit of an interface or PW specifies the maximum rate for forwarding packets (excluding critical packets).

Rate limit also uses token buckets for traffic control. When rate limit is configured on an interface, a token bucket handles all packets to be sent through the interface for rate limiting. If enough tokens are in the token bucket, packets can be forwarded. Otherwise, packets are put into QoS queues for congestion management. In this way, the traffic passing the interface is controlled.

Figure 10 Rate limit implementation

The token bucket mechanism limits traffic rate when accommodating bursts. It allows bursty traffic to be transmitted if enough tokens are available. If tokens are scarce, packets cannot be transmitted until efficient tokens are generated in the token bucket. It restricts the traffic rate to the rate for generating tokens.

Rate limit controls the total rate of all packets on an interface. It is easier to use than traffic policing in controlling the total traffic rate.

Configuring traffic policing

Traffic policing configuration approaches

You can configure traffic policing by using the MQC approach or the non-MQC approach. If both approaches are used, the MQC configuration takes effect.

You can configure the following types of traffic policing by using the non-MQC approach:

· CAR-list-based traffic policing.

· ACL-based traffic policing.

· Traffic policing for all traffic.

· Traffic policing for a user profile.

If traffic policing is configured by using both the MQC approach and non-MQC approach, the configuration in MQC approach takes effect.

Configuring traffic policing by using the MQC approach

Restrictions and guidelines

The device supports the following application destinations for traffic policing:

· Interface.

· PVC.

· Control plane.

· Control-plane management view.

· User profile.

Procedure

1. Enter system view.

system-view

2. Define a traffic class.

a. Create a traffic class and enter traffic class view.

traffic classifier classifier-name [ operator { and | or } ]

b. Configure a match criterion.

if-match [ not ] match-criteria

By default, no match criterion is configured.

For more information about the if-match command, see ACL and QoS Command Reference.

c. Return to system view.

quit

3. Define a traffic behavior.

a. Create a traffic behavior and enter traffic behavior view.

traffic behavior behavior-name

b. Configure a traffic policing action.

¡ In absolute value:

car cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ green action | red action | yellow action ] *

car cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ green action | red action | yellow action ] *

¡ In percentage:

car cir percent cir-percent [ cbs cbs-time [ ebs ebs-time ] ] [ green action | red action | yellow action ] *

car cir percent cir-percent [ cbs cbs-time ] pir percent pir-percent [ ebs ebs-time ] [ green action | red action | yellow action ] *

By default, no traffic policing action is configured.

c. Return to system view.

quit

4. Define a QoS policy.

a. Create a QoS policy and enter QoS policy view.

qos policy policy-name

b. Associate the traffic class with the traffic behavior in the QoS policy.

classifier classifier-name behavior behavior-name

By default, a traffic class is not associated with a traffic behavior.

c. Return to system view.

quit

5. Apply the QoS policy.

For more information, see "Applying the QoS policy."

By default, no QoS policy is applied.

Configuring CAR-list-based traffic policing

1. Enter system view.

system-view

2. Configure a CAR list.

qos carl carl-index { dscp dscp-list | mac mac-address | mpls-exp mpls-exp-value | precedence precedence-value | { destination-ip-address | source-ip-address } { range start-ip-address to end-ip-address | subnet ip-address mask-length } [ per-address [ shared-bandwidth ] ] }

3. Enter interface view.

interface interface-type interface-number

4. Apply a CAR-list-based CAR policy to the interface.

¡ In absolute value:

qos car { inbound | outbound } carl carl-index cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ green action | red action | yellow action ] *

qos car { inbound | outbound } carl carl-index cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ green action | red action | yellow action ] *

¡ In percentage:

qos car { inbound | outbound } carl carl-index percent cir cir-percent [ cbs cbs-time [ ebs ebs-time ] ] [ green action | red action | yellow action ] *

qos car { inbound | outbound } carl carl-index percent cir cir-percent [ cbs cbs-time ] pir pir-percent [ ebs ebs-time ] [ green action | red action | yellow action ] *

By default, no CAR policy is applied to an interface.

Configuring ACL-based traffic policing

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Configure an ACL-based CAR policy on the interface.

¡ In absolute value:

qos car { inbound | outbound } acl [ ipv6 ] acl-number cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ green action | red action | yellow action ] *

qos car { inbound | outbound } acl [ ipv6 ] acl-number cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ green action | red action | yellow action ] *

By default, no CAR policy is configured on an interface.

Configuring traffic policing for all traffic

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Configure a CAR policy for all traffic on the interface.

¡ In absolute value:

qos car { inbound | outbound } any cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ green action | red action | yellow action ] *

qos car { inbound | outbound } any cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ green action | red action | yellow action ] *

By default, no CAR policy is configured on an interface.

Configuring traffic policing for a user profile

About this task

When a user profile is configured, you can perform traffic policing based on users. After a user passes authentication, the authentication server sends the name of the user profile associated with the user to the device. When any user of the user profile logs in, the authentication server automatically applies the CAR parameters configured for the user profile to the user. When the user logs off, the system automatically removes the CAR configuration without manual intervention.

Procedure

1. Enter system view.

system-view

2. Enter user profile view.

user-profile profile-name

3. Configure a CAR policy for the user profile.

qos car { inbound | outbound } any cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ]

qos car { inbound | outbound } any cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ]

By default, no CAR policy is configured for a user profile.

Configuring GTS

GTS configuration approaches

You can configure GTS by using either the MQC approach or non-MQC approach.

You can configure the following types of GTS by using the non-MQC approach:

· ACL-based GTS.

· GTS for all traffic.

If GTS is configured by using both the MQC approach and non-MQC approach, the configuration in MQC approach takes effect.

Configuring GTS by using the MQC approach

Restrictions and guidelines

The device supports the following application destinations for GTS:

· Interface.

· PVC.

· VLANs.

· Globally.

· Control plane.

· User profile.

Procedure

1. Enter system view.

system-view

2. Define a traffic class.

a. Create a traffic class and enter traffic class view.

traffic classifier classifier-name [ operator { and | or } ]

b. Configure a match criterion.

if-match [ not ] match-criteria

By default, no match criterion is configured.

For configurable match criteria, see the if-match command in ACL and QoS Command Reference.

c. Return to system view.

quit

3. Define a traffic behavior.

a. Create a traffic behavior and enter traffic behavior view.

traffic behavior behavior-name

b. Configure a GTS action.

- In absolute value:

gts cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ queue-length queue-length ]

- In percentage:

gts percent cir cir-percent [ cbs cbs-time [ ebs ebs-time ] ] [ queue-length queue-length ]

By default, no GTS action is configured.

c. Return to system view.

quit

4. Define a QoS policy.

a. Create a QoS policy and enter QoS policy view.

qos policy policy-name

b. Associate the class with the traffic behavior in the QoS policy.

classifier classifier-name behavior behavior-name

By default, a traffic class is not associated with a traffic behavior.

c. Return to system view.

quit

5. Apply the QoS policy.

For more information, see "Applying the QoS policy."

By default, no QoS policy is applied.

Configuring ACL-based GTS

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Configure ACL-based GTS on the interface.

¡ In absolute value:

qos gts acl [ ipv6 ] acl-number cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ queue-length queue-length ]

qos gts acl [ ipv6 ] acl-number cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ queue-length queue-length ]

By default, GTS is not configured on an interface.

Configuring GTS for all traffic

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Configure GTS on the interface.

qos gts any cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ queue-length queue-length ]

By default, GTS is not configured on an interface.

Configuring the rate limit

Configuring the rate limit for an interface

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Configure the rate limit for the interface.

¡ In absolute value:

qos lr outbound cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ]

By default, no rate limit is configured on an interface.

Configuring the rate limit for a PW

1. Enter system view.

system-view

2. Enter PW view.

¡ Execute the following commands in sequence to enter cross-connect PW view:

xconnect-group group-name

connection connection-name

peer ip-address pw-id pw-id [ in-label label-value out-label label-value ] [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

¡ Execute the following commands in sequence to enter VSI LDP PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling ldp

peer ip-address [ pw-id pw-id ] [ hub | no-split-horizon ] [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

¡ Execute the following commands in sequence to enter VSI static PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling static

peer ip-address [ pw-id pw-id ] [ in-label label-value out-label label-value [ hub | no-split-horizon | pw-class class-name | tunnel-policy tunnel-policy-name ] * ]

3. Configure the rate limit for the PW.

qos lr outbound cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ]

By default, no rate limit is configured for a PW.

Display and maintenance commands for traffic policing, GTS, and rate limit

Execute display commands in any view.

Task	Command
Display CAR configuration and statistics on an interface.	display qos car interface [ interface-type interface-number ]
Display CAR list information.	In standalone mode: display qos carl [ carl-index ] [ slot slot-number ] In IRF mode: display qos carl [ carl-index ] [ chassis chassis-number slot slot-number ]
Display GTS configuration and statistics for interfaces.	display qos gts interface [ interface-type interface-number ]
Display rate limit configuration and statistics.	display qos lr { interface [ interface-type interface-number ] \| l2vpn-pw [ peer ip-address pw-id pw-id ] }
Display QoS and ACL resource usage.	In standalone mode: display qos-acl resource [ slot slot-number ] In IRF mode: display qos-acl resource [ chassis chassis-number slot slot-number ]
Display traffic behavior configuration.	In standalone mode: display traffic behavior user-defined [ behavior-name ] [ slot slot-number ] In IRF mode: display traffic behavior user-defined [ behavior-name ] [ chassis chassis-number slot slot-number ]

‌

Traffic policing, GTS, and rate limit configuration examples

Example: Configuring traffic policing and GTS

Network requirements

As shown in Figure 11:

· The server, Host A, and Host B can access the Internet through Device A and Device B.

· The server, Host A, and GigabitEthernet 2/0/1 of Device A are in the same network segment.

· Host B and GigabitEthernet 2/0/2 of Device A are in the same network segment.

Perform traffic control for the packets that GigabitEthernet 2/0/1 of Device A receives from the server and Host A using the following guidelines:

· Limit the rate of packets from the server to 10240 kbps. When the traffic rate is below 10240 kbps, the traffic is forwarded. When the traffic rate exceeds 10240 kbps, the excess packets are marked with DSCP value 0 and then forwarded.

· Limit the rate of packets from Host A to 2560 kbps. When the traffic rate is below 2560 kbps, the traffic is forwarded. When the traffic rate exceeds 2560 kbps, the excess packets are dropped.

Perform traffic control on GigabitEthernet 2/0/1 and GigabitEthernet 2/0/2 of Device B using the following guidelines:

· Limit the incoming traffic rate on GigabitEthernet 2/0/1 to 20480 kbps, and the excess packets are dropped.

· Limit the outgoing traffic rate on GigabitEthernet 2/0/2 to 10240 kbps, and the excess packets are dropped.

Figure 11 Network diagram

‌

Procedure

1. Configure Device A:

# Configure ACL 2001 and ACL 2002 to permit the packets from the server and Host A, respectively.

[DeviceA] acl basic 2001

[DeviceA-acl-ipv4-basic-2001] rule permit source 1.1.1.1 0

[DeviceA-acl-ipv4-basic-2001] quit

[DeviceA] acl basic 2002

[DeviceA-acl-ipv4-basic-2002] rule permit source 1.1.1.2 0

[DeviceA-acl-ipv4-basic-2002] quit

# Create a traffic class named server, and use ACL 2001 as the match criterion.

[DeviceA] traffic classifier server

[DeviceA-classifier-server] if-match acl 2001

[DeviceA-classifier-server] quit

# Create a traffic class named host, and use ACL 2002 as the match criterion.

[DeviceA] traffic classifier host

[DeviceA-classifier-host] if-match acl 2002

[DeviceA-classifier-host] quit

# Create a traffic behavior named server, and configure a traffic policing action (CIR 10240 kbps).

[DeviceA] traffic behavior server

[DeviceA-behavior-server] car cir 10240 red remark-dscp-pass 0

[DeviceA-behavior-server] quit

# Create a traffic behavior named host, and configure a traffic policing action (CIR 2560 kbps).

[DeviceA] traffic behavior host

[DeviceA-behavior-host] car cir 2560

[DeviceA-behavior-host] quit

# Create a QoS policy named car, and associate traffic classes server and host with traffic behaviors server and host in QoS policy car, respectively.

[DeviceA] qos policy car

[DeviceA-qospolicy-car] classifier server behavior server

[DeviceA-qospolicy-car] classifier host behavior host

[DeviceA-qospolicy-car] quit

# Apply QoS policy car to the inbound direction of GigabitEthernet 2/0/1.

[DeviceA] interface gigabitethernet 2/0/1

[DeviceA-GigabitEthernet2/0/1] qos apply policy car inbound

2. Configure Device B:

# Create ACL 3001, and configure a rule to match HTTP packets.

<DeviceB> system-view

[DeviceB] acl advanced 3001

[DeviceB-acl-adv-3001] rule permit tcp destination-port eq 80

[DeviceB-acl-adv-3001] quit

# Create a traffic class named http, and use ACL 3001 as a match criterion.

[DeviceB] traffic classifier http

[DeviceB-classifier-http] if-match acl 3001

[DeviceB-classifier-http] quit

# Create a traffic class named class, and configure the traffic class to match all packets.

[DeviceB] traffic classifier class

[DeviceB-classifier-class] if-match any

[DeviceB-classifier-class] quit

# Create a traffic behavior named car_inbound, and configure a traffic policing action (CIR 20480 kbps).

[DeviceB] traffic behavior car_inbound

[DeviceB-behavior-car_inbound] car cir 20480

[DeviceB-behavior-car_inbound] quit

# Create a traffic behavior named car_outbound, and configure a traffic policing action (CIR 10240 kbps).

[DeviceB] traffic behavior car_outbound

[DeviceB-behavior-car_outbound] car cir 10240

[DeviceB-behavior-car_outbound] quit

# Create a QoS policy named car_inbound, and associate traffic class class with traffic behavior car_inbound in QoS policy car_inbound.

[DeviceB] qos policy car_inbound

[DeviceB-qospolicy-car_inbound] classifier class behavior car_inbound

[DeviceB-qospolicy-car_inbound] quit

# Create a QoS policy named car_outbound, and associate traffic class http with traffic behavior car_outbound in QoS policy car_outbound.

[DeviceB] qos policy car_outbound

[DeviceB-qospolicy-car_outbound] classifier http behavior car_outbound

[DeviceB-qospolicy-car_outbound] quit

# Apply QoS policy car_inbound to the inbound direction of GigabitEthernet 2/0/1.

[DeviceB] interface gigabitethernet 2/0/1

[DeviceB-GigabitEthernet2/0/1] qos apply policy car_inbound inbound

# Apply QoS policy car_outbound to the outbound direction of GigabitEthernet 2/0/2.

[DeviceB] interface gigabitethernet 2/0/2

[DeviceB-GigabitEthernet2/0/2] qos apply policy car_outbound outbound

Example: Configuring per-IP-address traffic policing

Network configuration

As shown in Figure 12, configure a CAR-list-based CAR policy on GigabitEthernet 2/0/2 to meet the following requirements:

· Limit the rate of incoming packets from each IP address in the range of 2.1.1.1 to 2.1.1.100 to 5 kbps.

· Allow all IP addresses in the range to share the remaining bandwidth.

Figure 12 Network diagram

‌

Procedure

# Configure per-IP-address rate limiting on GigabitEthernet 2/0/2 to meet the following requirements:

· Limit the rate of each host on the network segment 2.1.1.1 through 2.1.1.100.

· Allow all IP addresses in the network segment to share the remaining bandwidth.

<Device> system-view

[Device] qos carl 1 source-ip-address range 2.1.1.1 to 2.1.1.100 per-address shared-bandwidth

[Device] interface gigabitethernet 2/0/2

[Device-GigabitEthernet2/0/2] qos car inbound carl 1 cir 500 cbs 1875 ebs 0 green pass red discard

[Device-GigabitEthernet2/0/2] quit

Configuring congestion management

About congestion management

Cause, negative results, and countermeasure of congestion

Congestion occurs on a link or node when traffic size exceeds the processing capability of the link or node. It is typical of a statistical multiplexing network and can be caused by link failures, insufficient resources, and various other causes. Figure 13 shows common congestion scenarios.

Figure 13 Traffic congestion causes

Congestion can introduce the following negative results:

· Increased delay and jitter during packet transmission.

· Decreased network throughput and resource use efficiency.

· Network resource (memory, in particular) exhaustion and system breakdown.

Congestion is unavoidable in switched networks or multiuser application environments. To improve the service performance of your network, implement congestion management policies.

For example, congestion management defines a resource dispatching policy to prioritize packets for forwarding when congestion occurs.

Congestion management methods

Congestion management involves queue creating, traffic classification, packet enqueuing, and queue scheduling.

Queuing is a common congestion management technique. It classifies traffic into queues and picks out packets from each queue by using an algorithm. Various queuing algorithms are available, and each addresses a particular network traffic problem. Your choice of algorithm significantly affects bandwidth assignment, delay, and jitter.

The device supports the following queuing mechanisms:

· FIFO.

· PQ.

· CQ.

· WFQ.

· CBQ.

· RTPQ.

FIFO

Figure 14 FIFO queuing

As shown in Figure 14, the first in first out (FIFO) uses a single queue and does not classify traffic or schedule queues. FIFO delivers packets in their arrival order. The packet that arrives earlier is scheduled first. The only concern of FIFO is queue length, which affects delay and packet loss rate. On a device, resources are assigned to packets depending on their arrival order and load status of the device. The best-effort service model uses FIFO queuing.

FIFO does not address congestion problems. If only one FIFO output/input queue exists on a port, you cannot ensure timely delivery of mission-critical or delay-sensitive traffic or smooth traffic jitter. If malicious traffic occupies bandwidth aggressively, the problems increase. To control congestion and prioritize forwarding of critical traffic, use other queue scheduling mechanisms, where multiple queues can be configured. Within each queue, FIFO is still used.

PQ

Figure 15 Priority queuing (PQ)

PQ is designed for mission-critical applications. Mission-critical applications require preferential treatment to reduce the response delay when congestion occurs. PQ can flexibly determine the order of forwarding packets by network protocol (for example, IP and IPX), incoming interface, packet length, source/destination address, and so on. Priority queuing classifies packets into four queues (top, middle, normal, and bottom queues, in descending priority order). By default, packets are assigned to the normal queue. Each of the four queues is a FIFO queue.

PQ schedules the four queues in descending order of priority. It sends packets in the queue with the highest priority first. When the queue with the highest priority is empty, it sends packets in the queue with the second highest priority. To make sure mission-critical packets are always served first, assign the mission-critical packets to the highest-priority queue. The common service packets that are assigned to the low-priority queues are transmitted when the high-priority queues are empty.

However, packets in the lower-priority queues cannot be transmitted when congestion occurs if packets exist in the higher-priority queues for a long time.

CQ

Figure 16 Custom queuing (CQ)

CQ provides 16 queues, numbered from 1 to 16, as shown in Figure 16. You can define traffic classification rules and divide bandwidth across queues by specifying the byte count for each queue. By default, packets are assigned to queue 1.

During a cycle of queue scheduling, CQ schedules the 16 queues in a round robin way. It sends a certain number of bytes out of each queue in the ascending order of queue 1 to queue 16. CQ guarantees a certain amount of bandwidth to common packets, and ensures that mission-critical packets are assigned more bandwidth. The bandwidth ratio for each queue is the byte count configured for that queue divided by the total byte count configured for all queues.

CQ can assign free bandwidth of idle queues to busy queues. Even though it performs round robin queue scheduling, CQ does not assign fixed time slots to the queues. If a queue is empty, CQ immediately moves to the next queue. When a class does not have packets, the bandwidth for other classes increases.

WFQ

Figure 17 Weighted fair queuing (WFQ)

FQ is designed to equally allocate network resources to reduce the delay and jitter of each traffic flow as much as possible. FQ follows these principles:

· Different queues have fair dispatching opportunities for delay balancing among flows.

· Short packets and long packets are equally scheduled. If long packets and short packets exist in queues, statistically the short packets are scheduled preferentially to reduce the jitter between packets.

WFQ considers weights when determining the queue scheduling order. Statistically, WFQ gives high-priority traffic more scheduling opportunities than low-priority traffic. To balance the delay of every traffic flow, WFQ performs the following operations:

· Automatically classifies traffic according to the "session" information of traffic.

· Attempts to provide as many queues as possible for traffic flows.

The session information of traffic includes the following information:

· Protocol type.

· TCP or UDP source/destination port numbers.

· Source/destination IP addresses.

· IP precedence bits in the ToS field.

When dequeuing packets, WFQ assigns the outgoing interface bandwidth to each traffic flow by precedence. The higher precedence value a traffic flow has, the more bandwidth it gets.

For example, five flows exist in the current interface with precedence 0, 1, 2, 3, and 4, respectively. The total bandwidth quota is the sum of all the (precedence value + 1)s, 1 + 2 + 3 + 4 + 5 = 15.

The bandwidth percentage assigned to each flow is (precedence value of the flow + 1)/total bandwidth quota. The bandwidth percentages for flows are 1/15, 2/15, 3/15, 4/15, and 5/15, respectively.

Because WFQ can balance the delay and jitter of each flow when congestion occurs, it is suitable for handling special situations. For example, WFQ is used in the assured forwarding (AF) services of the RSVP, and WFQ is used to schedule buffered packets in GTS.

CBQ

Figure 18 CBQ

Class-based queuing (CBQ) extends WFQ by supporting user-defined classes. When network congestion occurs, CBQ uses user-defined traffic match criteria to enqueue packets. Before packets are enqueued, congestion avoidance actions, such as tail drop or WRED and bandwidth restriction check, are performed. When being dequeued, packets are scheduled by WFQ.

CBQ provides the following queues:

· Emergency queue—Enqueues emergent packets. The emergency queue is a FIFO queue without bandwidth restriction.

· Strict priority (SP) queuing—SP queuing is designed for mission-critical applications. Mission-critical applications require preferential treatment to reduce the response delay when congestion occurs. With SP queuing, CBQ can provide strict priority service. A maximum of 64 SP queues are supported.

· Low Latency Queuing (LLQ)—An EF queue. Because packets are fairly treated in CBQ, delay-sensitive flows like video and voice packets might not be transmitted timely. To solve this problem, LLQ combines PQ and CBQ to preferentially transmit delay-sensitive flows like voice packets. When defining traffic classes for LLQ, you can configure a class of packets to be preferentially transmitted. The packets of all priority classes are assigned to the same priority queue. Bandwidth restriction on each class of packets is checked before the packets are enqueued. During the dequeuing operation, packets in the priority queue are transmitted first. To reduce the delay of the other queues except the priority queue, LLQ assigns the maximum available bandwidth to each priority class. The bandwidth value polices traffic during congestion. When no congestion is present, a priority class can use more than the bandwidth assigned to it. During congestion, the packets of each priority class exceeding the assigned bandwidth are discarded.

· Bandwidth queuing (BQ)—An AF queue. The BQ provides guaranteed bandwidth for AF traffic, and schedules the AF classes proportionally. The system supports up to 64 AF queues.

· Default queue—A WFQ queue. The default queue transmits the BE traffic by using the remaining interface bandwidth.

The system matches packets with classification rules in the following order:

· Match packets with priority classes and then the other classes.

· Match packets with priority classes in the configuration order.

· Match packets with other classes in the configuration order.

· Match packets with classification rules in a class in the configuration order.

RTPQ

RTP queuing (RTPQ) is designed for delay-sensitive, real-time traffic (such as voice and video). You can assign voice or video packets to a high-priority queue by specifying a UDP port range as the match criterion. These packets are given strict priority service and are sent before packets in other queues are sent.

Figure 19 RTPQ

Congestion management technique comparison

Congestion management techniques offer different QoS capabilities to meet different application requirements, as explained in Table 2.

Table 2 Congestion management technique comparison

Type	Number of queues	Advantages	Disadvantages
FIFO	1	· No need to configure, easy to use. · Easy to operate, low delay.	· All packets are treated equally. The available bandwidth, delay and drop probability are determined by the arrival order of packets. · No restriction on traffic from connectionless protocols (protocols without any flow control mechanism, UDP, for example). This problem results in bandwidth loss for traffic of connection-oriented protocols (TCP, for example). · No delay guarantee for time-sensitive real-time applications, such as VoIP.
PQ	4	Provides strict priority service for mission-critical applications and guarantees low delay for real-time traffic, such as voice traffic.	· Need to configure, low processing speed. · If packets always exist in high-priority queues, packets in low-priority queues cannot be sent.
CQ	16	· Bandwidth assignment in percentages for different applications. · Bandwidth reassignment to increase bandwidth for each class when packets of certain classes are not present.	Need to configure, low processing speed.
WFQ	Configurable	· Easy to configure. · Bandwidth guarantee for packets from cooperative (interactive) sources (such as TCP packets). · Reduces jitter. · Reduces the delay for interactive applications with a small amount of data. · Bandwidth assignment based on traffic priority. · Automatic bandwidth reassignment to increase bandwidth for each class when the number of traffic classes decreases.	The processing speed is slower than FIFO.
CBQ	Configurable (0 to 64)	· Flexible traffic classification based on rules and differentiated queue scheduling mechanisms for EF, AF and BE services. · Highly precise bandwidth guarantee and queue scheduling on the basis of AF service weights for various AF services. · Absolute preferential queue scheduling for the EF service to meet the delay requirement of real-time data. · Overcomes the PQ disadvantage where some low-priority queues are not serviced by restricting the high-priority traffic. · WFQ scheduling for best-effort traffic (the default class).	The system overheads are large.
RTPQ	1	· Provides preferential treatment for real-time applications. · Performs traffic policing before enqueuing packets to prevent other queues from being starved.	Applicable only to delay-sensitive applications, such as voice and video.

‌

Setting the FIFO queue size

FIFO is the default queue scheduling mechanism for an interface, and the FIFO queue size is configurable. Queue length can affect delay and packet loss ratio.

Setting the FIFO queue size for an interface

Restrictions and guidelines

For the FIFO queuing feature to take effect on a subinterface, you must configure the rate limit on the subinterface.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Set the FIFO queue size for the interface.

qos fifo queue-length queue-length

The default setting is 75.

If the burst traffic is too heavy, increase the queue length to make queue scheduling more accurate.

Setting the FIFO queue size for a PVC

1. Enter system view.

system-view

2. Execute the following commands in sequence to enter PVC view:

interface atm interface-number

pvc vpi/vci

3. Set the FIFO queue size for the PVC.

qos fifo queue-length queue-length

The default setting is 75.

If the burst traffic is too heavy, increase the queue length to make queue scheduling more accurate.

Setting the FIFO queue size for a PW

1. Enter system view.

system-view

2. Enter PW view.

¡ Execute the following commands in sequence to enter cross-connect PW view:

xconnect-group group-name

connection connection-name

peer ip-address pw-id pw-id [ in-label label-value out-label label-value ] [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

¡ Execute the following commands in sequence to enter VSI LDP PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling ldp

peer ip-address [ pw-id pw-id ] [ hub | no-split-horizon ] [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

¡ Execute the following commands in sequence to enter VSI static PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling static

peer ip-address [ pw-id pw-id ] [ in-label label-value out-label label-value [ hub | no-split-horizon | pw-class class-name | tunnel-policy tunnel-policy-name ] * ]

3. Set the FIFO queue size for the PW.

qos fifo queue-length queue-length

The default setting is 75.

If the burst traffic is too heavy, increase the queue length to make queue scheduling more accurate.

Configuring PQ

About configuring PQ

You can define a set of assignment rules in a PQ list and then apply the PQ list to an interface or PVC. An assignment rule assigns a packet that meets a specific match criterion to a queue.

When a packet arrives, it is examined against match criteria in their configuration order.

· When a match is found, the packet is assigned to the corresponding queue, and the matching process ends.

· If no match is found, the packet is assigned to the default queue.

Restrictions and guidelines

· If you apply multiple PQ lists to an interface or PVC, the PQ list last applied takes effect.

· You must configure the rate limit for the PQ feature to take effect on the following interfaces:

¡ Tunnel interfaces.

¡ Subinterfaces.

¡ Layer 3 aggregate interfaces.

¡ HDLC link bundle interfaces.

¡ RPR logical interfaces.

¡ VT and dialer interfaces configured with PPPoE, PPPoA, PPPoEoA, PPPoFR, or MPoFR. (To configure MPoFR, make sure the Frame Relay interface in MPoFR is not enabled with FRTS.)

For information about the rate limit function, see "Configuring the rate limit."

Configuring PQ for an interface

1. Enter system view.

system-view

2. Configure a PQ list.

¡ Configure a protocol-based PQ list.

qos pql pql-index protocol { ip | ipv6 } [ queue-key key-value ] queue { bottom | middle | normal | top }

¡ Configure an interface-based PQ list.

qos pql pql-index inbound-interface interface-type interface-number queue { bottom | middle | normal | top }

¡ Configure a local-precedence-based PQ list.

qos pql pql-index local-precedence local-precedence-list queue { bottom | middle | normal | top }

¡ Configure an MPLS-EXP-based PQ list.

qos pql pql-index protocol mpls exp exp-list queue { bottom | middle | normal | top }

3. (Optional.) Configure a queue as the default queue for the PQ list.

qos pql pql-index default-queue { bottom | middle | normal | top }

By default, the normal queue is the default queue.

The default queue enqueues packets that do not match any criteria in a PQ list.

4. (Optional.) Set the maximum queue length for a queue in the PQ list.

qos pql pql-index queue { bottom | middle | normal | top } queue-length queue-length

By default:

¡ The maximum top queue length is 20.

¡ The maximum middle queue length is 40.

¡ The maximum normal queue length is 60.

¡ The maximum bottom queue length is 80.

5. Enter interface view.

interface interface-type interface-number

6. Apply the PQ list to the interface.

qos pq pql pql-index

By default, FIFO is used.

Configuring PQ for a PVC

1. Enter system view.

system-view

2. Configure a PQ list.

¡ Configure a protocol-based PQ list.

qos pql pql-index protocol { ip | ipv6 } [ queue-key key-value ] queue { bottom | middle | normal | top }

¡ Configure an interface-based PQ list.

qos pql pql-index inbound-interface interface-type interface-number queue { bottom | middle | normal | top }

¡ Configure a local-precedence-based PQ list.

qos pql pql-index local-precedence local-precedence-list queue { bottom | middle | normal | top }

¡ Configure an MPLS-EXP-based PQ list.

qos pql pql-index protocol mpls exp exp-list queue { bottom | middle | normal | top }

3. (Optional.) Configure a queue as the default queue for the PQ list.

qos pql pql-index default-queue { bottom | middle | normal | top }

By default, the normal queue is the default queue.

The default queue enqueues packets that do not match any criteria in a PQ list.

4. (Optional.) Set the maximum queue length for a queue in the PQ list.

qos pql pql-index queue { bottom | middle | normal | top } queue-length queue-length

By default:

¡ The maximum top queue length is 20.

¡ The maximum middle queue length is 40.

¡ The maximum normal queue length is 60.

¡ The maximum bottom queue length is 80.

5. Execute the following commands in sequence to enter PVC view:

interface atm interface-number

pvc vpi/vci

6. Apply the PQ list to the PVC.

qos pq pql pql-index

By default, FIFO is used.

Example: Configuring PQ

Network configuration

As shown in Figure 20, both the server and Host A send data to Host B through Device A. The server sends critical packets, and Host A sends non-critical packets.

Configure PQ on GigabitEthernet 2/0/2 of Device A, so that the critical packets from the server are transmitted preferentially when congestion occurs.

Figure 20 Network diagram

‌

Procedure

# Configure two ACLs to match packets from the server and Host A.

[DeviceA] acl basic 2001

[DeviceA-acl-ipv4-basic-2001] rule permit source 1.1.1.1 0

[DeviceA] acl basic 2002

[DeviceA-acl-ipv4-basic-2002] rule permit source 1.1.1.2 0

# Configure a PQ list to assign the packets from the server to the top queue when congestion occurs.

[DeviceA] qos pql 1 protocol ip acl 2001 queue top

# Configure a PQ list to assign the packets from Host A to the bottom queue when congestion occurs.

[DeviceA] qos pql 1 protocol ip acl 2002 queue bottom

# Set the maximum queue size of the top queue to 50 and that of the bottom queue to 100 in the PQ list.

[DeviceA] qos pql 1 queue top queue-length 50

[DeviceA] qos pql 1 queue bottom queue-length 100

# Apply PQ list 1 to GigabitEthernet 2/0/2.

[DeviceA] interface gigabitethernet 2/0/2

[DeviceA-GigabitEthernet2/0/2] qos pq pql 1

Configuring CQ

About configuring CQ

You can configure a CQ list that contains up to 16 queues. The CQ list specifies the following information:

· The queue where a packet is placed in.

· The maximum length of each queue.

· The number of bytes sent from the queue during a cycle of round robin scheduling.

Restrictions and guidelines

· If you apply multiple CQ lists to an interface or PVC, the CQ list last applied takes effect.

· You must configure the rate limit for the CQ feature to take effect on the following interfaces:

¡ Tunnel interfaces.

¡ Subinterfaces.

¡ Layer 3 aggregate interfaces.

¡ HDLC link bundle interfaces.

¡ RPR logical interfaces.

¡ VT and dialer interfaces configured with PPPoE, PPPoA, PPPoEoA, PPPoFR, or MPoFR. (To configure MPoFR, make sure the Frame Relay interface in MPoFR is not enabled with FRTS.)

For information about the rate limit function, see "Configuring the rate limit."

Configuring CQ for an interface

1. Enter system view.

system-view

2. Configure a CQ list.

¡ Configure a protocol-based CQ list.

qos cql cql-index protocol { ip | ipv6 } [ queue-key key-value ] queue queue-id

¡ Configure an interface-based PQ list.

qos cql cql-index inbound-interface interface-type interface-number queue queue-id

¡ Configure a local-precedence-based CQ list.

qos cql cql-index local-precedence local-precedence-list queue queue-id

¡ Configure an MPLS-EXP-based CQ list.

qos cql cql-index protocol mpls exp exp-list queue queue-id

3. (Optional.) Configure a queue as the default queue for the CQ list.

qos cql cql-index default-queue queue-id

By default, queue 1 is the default queue.

The default queue enqueues packets that do not match any criteria in a CQ list.

4. (Optional.) Set the maximum length of a queue in the CQ list.

qos cql cql-index queue queue-id queue-length queue-length

The default setting is 20.

5. (Optional.) Configure the number of bytes sent from a queue during a cycle of round robin scheduling in the CQ list.

qos cql cql-index queue queue-id serving byte-count

The default setting is 1500 bytes.

6. Enter interface view.

interface interface-type interface-number

7. Apply the CQ list to the interface.

qos cq cql cql-index

By default, FIFO is used.

Configuring CQ for a PVC

1. Enter system view.

system-view

2. Configure a CQ list.

¡ Configure a protocol-based CQ list.

qos cql cql-index protocol { ip | ipv6 } [ queue-key key-value ] queue queue-id

¡ Configure an interface-based CQ list.

qos cql cql-index inbound-interface interface-type interface-number queue queue-id

¡ Configure a local-precedence-based CQ list.

qos cql cql-index local-precedence local-precedence-list queue queue-id

¡ Configure an MPLS-EXP-based CQ list.

qos cql cql-index protocol mpls exp exp-list queue queue-id

3. (Optional.) Configure a queue as the default queue for the CQ list.

qos cql cql-index default-queue queue-id

By default, queue 1 is the default queue.

The default queue enqueues packets that do not match any criteria in a CQ list.

4. (Optional.) Set the maximum length of a queue in the CQ list.

qos cql cql-index queue queue-id queue-length queue-length

The default setting is 20.

5. (Optional.) Configure the number of bytes sent from a queue during a cycle of round robin scheduling in the CQ list.

qos cql cql-index queue queue-id serving byte-count

The default setting is 1500 bytes.

6. Execute the following commands in sequence to enter PVC view:

interface atm interface-number

pvc vpi/vci

7. Apply the CQ list to the PVC.

qos cq cql cql-index

By default, FIFO is used.

Configuring WFQ

Restrictions and guidelines

· You must configure the rate limit for the WFQ feature to take effect on the following interfaces:

¡ Tunnel interfaces.

¡ Subinterfaces.

¡ Layer 3 aggregate interfaces.

¡ HDLC link bundle interfaces.

¡ RPR logical interfaces.

¡ VT and dialer interfaces configured with PPPoE, PPPoA, PPPoEoA, PPPoFR, or MPoFR. (To configure MPoFR, make sure the Frame Relay interface in MPoFR is not enabled with FRTS.)

For information about the rate limit function, see "Configuring the rate limit."

· On an interface or PVC that is not enabled with WFQ, the qos wfq command can enable WFQ and configure WFQ-related parameters. If WFQ has been enabled for the interface or PVC, the qos wfq command can modify the WFQ-related parameters.

Configuring WFQ for an interface

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Configure WFQ for the interface.

qos wfq [ dscp | precedence ] [ queue-length max-queue-length | queue-number total-queue-number ] *

By default, WFQ is not configured for an interface.

Configuring WFQ for a PVC

1. Enter system view.

system-view

2. Execute the following commands in sequence to enter PVC view:

interface atm interface-number

pvc vpi/vci

3. Configure WFQ for the PVC.

qos wfq [ dscp | precedence ] [ queue-length max-queue-length | queue-number total-queue-number ] *

By default, WFQ is not configured for a PVC.

Configuring WFQ for a PW

1. Enter system view.

system-view

2. Enter PW view.

¡ Execute the following commands in sequence to enter cross-connect PW view:

xconnect-group group-name

connection connection-name

peer ip-address pw-id pw-id [ in-label label-value out-label label-value ] [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

¡ Execute the following commands in sequence to enter VSI LDP PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling ldp

peer ip-address [ pw-id pw-id ] [ hub | no-split-horizon ] [ pw-class class-name | tunnel-policy tunnel-policy-name ] *

¡ Execute the following commands in sequence to enter VSI static PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling static

peer ip-address [ pw-id pw-id ] [ in-label label-value out-label label-value [ hub | no-split-horizon | pw-class class-name | tunnel-policy tunnel-policy-name ] * ]

3. Configure WFQ for the PW.

qos wfq [ dscp | precedence ] [ queue-length max-queue-length | queue-number total-queue-number ] *

By default, WFQ is not configured for a PW.

Configuring RTPQ

Restrictions and guidelines

· RTPQ and CBQ are mutually exclusive.

· You must configure the rate limit for the RTPQ feature to take effect on the following interfaces:

¡ Tunnel interfaces.

¡ Subinterfaces.

¡ Layer 3 aggregate interfaces.

¡ HDLC link bundle interfaces.

¡ RPR logical interfaces.

¡ VT and dialer interfaces configured with PPPoE, PPPoA, or PPPoEoA.

For information about the rate limit function, see "Configuring the rate limit."

Configuring RTPQ on an interface

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Configure RTPQ.

qos rtpq start-port first-rtp-port-number end-port last-rtp-port-number bandwidth bandwidth [ cbs cbs ]

By default, RTPQ is not configured.

Configuring RTPQ on a PVC

1. Enter system view.

system-view

2. Execute the following commands in sequence to enter PVC view:

interface atm interface-number

pvc vpi/vci

3. Configure RTPQ.

qos rtpq start-port first-rtp-port-number end-port last-rtp-port-number bandwidth bandwidth [ cbs cbs ]

By default, RTPQ is not configured.

Enabling packet information pre-extraction

About this task

The IP packets received on the physical interface for a tunnel interface might have been processed by the tunnel interface. For example, if the tunnel interface has used GRE to encapsulate packets, the GRE-encapsulated packets enter the QoS module for processing on the physical interface. As a result, the QoS module cannot get the IP information of the original packets.

To process the original IP packets with QoS on the physical interface for a tunnel interface, configure packet information pre-extraction on the tunnel interface.

For more information about tunnel interfaces, see Layer 3—IP Services Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enter tunnel interface view.

interface tunnel number [ mode { ds-lite-aftr | evi [ ipv6 ] | gre [ ipv6 ] | ipv4-ipv4 | ipv6 | ipv6-ipv4 [ 6to4 | auto-tunnel | isatap ] | mpls-te } ]

3. Enable packet information pre-extraction.

qos pre-classify

By default, packet information pre-extraction is disabled.

Enabling enhanced queuing

Restrictions and guidelines

Only RT-FIP-680 base cards support this feature. This feature takes effect on fixed ports on the base card, but not on interfaces on subcards installed in the base card.

After this feature is configured, the router processes queue scheduling in hardware, which improves queue scheduling performance.

Procedure

1. Enter system view.

system-view

2. Enable enhanced queuing for a card.

In standalone mode:

qos-queue enhanced slot slot-number

In IRF mode:

qos-queue enhanced chassis chassis-number slot slot-number

By default, enhanced queuing is disabled for a card.

Displaying and maintaining congestion management

Execute display commands in any view and reset commands in user view.

Task	Command
Display the configuration of CQ lists.	display qos cql [ cql-index ]
Display QoS policy configuration.	display qos policy { system-defined \| user-defined } [ policy-name [ classifier classifier-name ] ]
(In standalone mode.) Display information about QoS policies applied to interfaces or PVCs.	display qos policy interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ] [ slot slot-number ] [ inbound \| outbound ]
(In IRF mode.) Display information about QoS policies applied to interfaces or PVCs.	display qos policy interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ] [ chassis chassis-number slot slot-number ] [ inbound \| outbound ]
Display the configuration of PQ lists.	display qos pql [ pql-index ]
Display the CBQ configuration and statistics for interfaces, PVCs, or PWs.	display qos queue cbq { interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ] \| l2vpn-pw [ peer ip-address pw-id pw-id ] }
Display the CQ configuration and statistics for interfaces or PVCs.	display qos queue cq interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ]
Display the FIFO configuration and statistics for interfaces, PVCs, or PWs.	display qos queue fifo { interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ] \| l2vpn-pw [ peer ip-address pw-id pw-id ] }
Display queuing configuration and statistics for interfaces or PVCs.	display qos queue interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ]
Display queuing configuration and statistics for PWs.	display qos queue l2vpn-pw [ peer ip-address pw-id pw-id ]
Display the PQ configuration and statistics for interfaces or PVCs.	display qos queue pq interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ]
Display the RTPQ configuration and statistics for interfaces or PVCs.	display qos queue rtpq interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ]
Display the WFQ configuration and statistics for interfaces, PVCs, or PWs.	display qos queue wfq { interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ] \| l2vpn-pw [ peer ip-address pw-id pw-id ] }
Display traffic behavior configuration.	display traffic behavior { system-defined \| user-defined } [ behavior-name ]
Display class configuration.	display traffic classifier { system-defined \| user-defined } [ classifier-name ]
Clear QoS statistics for PWs.	reset qos statistics l2vpn-pw [ peer ip-address pw-id pw-id ]

‌

Configuring congestion avoidance

About congestion avoidance

Avoiding congestion before it occurs is a proactive approach to improving network performance. As a flow control mechanism, congestion avoidance:

· Actively monitors network resources (such as queues and memory buffers).

· Drops packets when congestion is expected to occur or deteriorate.

When dropping packets from a source end, congestion avoidance cooperates with the flow control mechanism at the source end to regulate the network traffic size. The combination of the local packet drop policy and the source-end flow control mechanism implements the following functions:

· Maximizes throughput and network use efficiency.

· Minimizes packet loss and delay.

Tail drop

Congestion management techniques drop all packets that are arriving at a full queue. This tail drop mechanism results in global TCP synchronization. If packets from multiple TCP connections are dropped, these TCP connections go into the state of congestion avoidance and slow start to reduce traffic. However, traffic peak occurs later. Consequently, the network traffic jitters all the time.

RED and WRED

You can use Random Early Detection (RED) or Weighted Random Early Detection (WRED) to avoid global TCP synchronization.

Both RED and WRED avoid global TCP synchronization by randomly dropping packets. When the sending rates of some TCP sessions slow down after their packets are dropped, other TCP sessions remain at high sending rates. Link bandwidth is efficiently used, because TCP sessions at high sending rates always exist.

The RED or WRED algorithm sets an upper threshold and lower threshold for each queue, and processes the packets in a queue as follows:

· When the queue size is shorter than the lower threshold, no packet is dropped.

· When the queue size reaches the upper threshold, all subsequent packets are dropped.

· When the queue size is between the lower threshold and the upper threshold, the received packets are dropped at random. The drop probability in a queue increases along with the queue size under the maximum drop probability.

If the current queue size is compared with the upper threshold and lower threshold to determine the drop policy, burst traffic is not fairly treated. To solve this problem, WRED compares the average queue size with the upper threshold and lower threshold to determine the drop probability.

The average queue size reflects the queue size change trend but is not sensitive to burst queue size changes, and burst traffic can be fairly treated.

When WFQ queuing is used, you can set the following parameters for packets with different precedence values to provide differentiated drop policies:

· Exponent for average queue size calculation.

· Upper threshold.

· Lower threshold.

· Drop probability.

When FIFO, PQ, or CQ is used, you can set the following parameters for each queue to provide differentiated drop policies:

· Exponent for average queue size calculation.

· Upper threshold.

· Lower threshold.

· Drop probability.

Relationship between WRED and queuing mechanisms

Figure 21 Relationship between WRED and queuing mechanisms

Through combining WRED with WFQ, the flow-based WRED can be realized. Each flow has its own queue after classification.

· A flow with a smaller queue size has a lower packet drop probability.

· A flow with a larger queue size has a higher packet drop probability.

In this way, the benefits of the flow with a smaller queue size are protected.

ECN

By dropping packets, WRED alleviates the influence of congestion on the network. However, the network resources for transmitting packets from the sender to the device which drops the packets are wasted. When congestion occurs, it is a better idea to perform the following actions:

· Inform the sender of the congestion status.

· Have the sender proactively slow down the packet sending rate or decrease the window size of packets.

This better utilizes the network resources.

RFC 2482 defined an end-to-end congestion notification mechanism named Explicit Congestion Notification (ECN). ECN uses the DS field in the IP header to mark the congestion status along the packet transmission path. An ECN-capable terminal can determine whether congestion occurs on the transmission path according to the packet contents. Then, it adjusts the packet sending speed to avoid deteriorating congestion. ECN defines the last two bits (ECN field) in the DS field of the IP header as follows:

· Bit 6 indicates whether the sending terminal device supports ECN, and is called the ECN-Capable Transport (ECT) bit.

· Bit 7 indicates whether the packet has experienced congestion along the transmission path, and is called the Congestion Experienced (CE) bit.

For more information about the DS field, see "Appendixes."

In actual applications, the following packets are considered as packets that an ECN-capable endpoint transmits:

· Packets with ECT set to 1 and CE set to 0.

· Packets with ECT set to 0 and CE set to 1.

After you enable ECN on a device, congestion management processes packets as follows:

· When the average queue size is below the lower threshold, no packet is dropped, and the ECN fields of packets are not identified or marked.

· When the average queue size is between the lower threshold and the upper threshold, the device performs the following operations:

a. Picks out packets to be dropped according to the drop probability.

b. Examines the ECN fields of these packets and determines whether to drop these packets.

¡ If the ECN field shows that the packet is sent out of ECN-capable terminal, the device performs the following operations:

- Sets both the ECT bit and the CE bit to 1.

- Forwards the packet.

¡ If both the ECT bit and the CE bit are 1 in the packet, the device forwards the packet without modifying the ECN field. The combination of ECT bit 1 and CE bit 1 indicates that the packet has experienced congestion along the transmission path.

¡ If both the ECT bit and the CE bit is 0 in the packet, the device drops the packet.

· When the average queue size exceeds the upper threshold, the device drops the packet, regardless of whether the packet is sent from an ECN-capable terminal.

WRED configuration approaches

You can configure WRED parameters on an interface or PVC and then enable WRED.

WRED parameters

Determine the following parameters before configuring WRED:

· Upper threshold and lower threshold—When the average queue size is smaller than the lower threshold, packets are not dropped. When the average queue size is between the lower threshold and the upper threshold, the packets are dropped at random. The longer the queue, the higher the drop probability. When the average queue size exceeds the upper threshold, subsequent packets are dropped.

· Drop precedence—A parameter used for packet drop. The value 0 corresponds to green packets, the value 1 corresponds to yellow packets, and the value 2 corresponds to red packets. Red packets are dropped preferentially.

· Exponent for average queue size calculation—The greater the exponent, the less sensitive the average queue size is to real-time queue size changes. The formula for calculating the average queue size is:

Average queue size = ( previous average queue size x (1 – 2–n) ) + (current queue size x 2–n), where n is the exponent.

· Denominator for drop probability calculation—The greater the denominator, the smaller the calculated drop probability. (Applicable when you configure WRED parameters on an interface or PVC.)

· Drop probability—Drop probability in percentage. The greater the value, the higher the drop probability. (Applicable when you configure a WRED table on an interface.)

Configuring WRED parameters on an interface

Restrictions and guidelines

To enable WRED on an interface, you must first enable WFQ on the interface.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Enable WRED.

qos wred [ dscp | ip-precedence ] enable

By default, tail drop is adopted.

4. (Optional.) Set the WRED exponent for average queue size calculation.

qos wred weighting-constant exponent

The default setting is 9.

5. (Optional.) Set the drop-related parameters for a precedence value.

qos wred { ip-precedence ip-precedence | dscp dscp-value } low-limit low-limit high-limit high-limit discard-probability discard-prob

By default, the lower limit is 10, the upper limit is 30, and the drop probability denominator is 10.

Repeat this command to configure more precedence values.

Example: Configuring WRED on an interface

Network configuration

· Enable IP precedence-based WRED on GigabitEthernet 2/0/1.

· Set the following parameters for packets with IP precedence 3: lower threshold 20, upper threshold 40, and drop probability denominator 15.

· Set the exponent for average queue size calculation to 6.

Procedure

# Enter system view.

<Sysname> system-view

# Enter interface view.

[Sysname] interface gigabitethernet 2/0/1

# Enable IP precedence-based WRED.

[Sysname-GigabitEthernet2/0/1] qos wred ip-precedence enable

# Set the following parameters for packets with IP precedence value 3: lower threshold 20, upper threshold 40, and drop probability 1/15.

[Sysname-GigabitEthernet2/0/1] qos wred ip-precedence 3 low-limit 20 high-limit 40 discard-probability 15

# Set the exponent for average queue size calculation to 6.

[Sysname-GigabitEthernet2/0/1] qos wred weighting-constant 6

Configuring WRED parameters on a PVC

Restrictions and guidelines

To enable WRED on a PVC, you must first enable WFQ on the PVC before configuring the qos wred enable command.

Procedure

1. Enter system view.

system-view

2. Execute the following commands in sequence to enter PVC view:

interface atm interface-number

pvc vpi/vci

3. Enable WRED.

qos wred [ dscp | ip-precedence ] enable

By default, tail drop is adopted.

4. (Optional.) Set the WRED exponent for average queue size calculation.

qos wred weighting-constant exponent

The default setting is 9.

5. (Optional.) Set the drop-related parameters for a precedence value.

qos wred { ip-precedence ip-precedence | dscp dscp-value } low-limit low-limit high-limit high-limit discard-probability discard-prob

By default, the lower limit is 10, the upper limit is 30, and the drop probability denominator is 10.

Repeat this command to configure more precedence values.

Display and maintenance commands for WRED

Execute display commands in any view.

Task	Command
Display WRED configuration and statistics for an interface or PVC.	display qos wred interface [ interface-type interface-number [ pvc { pvc-name \| vpi/vci } ] ]

‌

Configuring traffic filtering

About traffic filtering

You can filter in or filter out traffic of a class by associating the class with a traffic filtering action. For example, you can filter packets sourced from an IP address according to network status.

Restrictions and guidelines: Traffic filtering configuration

The device supports the following application destinations for traffic filtering:

· Interface.

· PVC.

· Control plane.

· User profile.

Procedure

1. Enter system view.

system-view

2. Define a traffic class.

a. Create a traffic class and enter traffic class view.

traffic classifier classifier-name [ operator { and | or } ]

b. Configure a match criterion.

if-match [ not ] match-criteria

By default, no match criterion is configured.

For more information about configuring match criteria, see ACL and QoS Command Reference.

c. Return to system view.

quit

3. Define a traffic behavior.

a. Create a traffic behavior and enter traffic behavior view.

traffic behavior behavior-name

b. Configure the traffic filtering action.

filter { deny | permit }

By default, no traffic filtering action is configured.

If a traffic behavior has the filter deny action, all other actions in the traffic behavior except class-based accounting do not take effect.

c. Return to system view.

quit

4. Define a QoS policy.

a. Create a QoS policy and enter QoS policy view.

qos policy policy-name

b. Associate the traffic class with the traffic behavior in the QoS policy.

classifier classifier-name behavior behavior-name

By default, a traffic class is not associated with a traffic behavior.

c. Return to system view.

quit

5. Apply the QoS policy.

For more information, see "Applying the QoS policy."

By default, no QoS policy is applied.

6. (Optional.) Display the traffic filtering configuration.

In standalone mode:

display traffic behavior user-defined [ behavior-name ] [ slot slot-number ]

In IRF mode:

display traffic behavior user-defined [ behavior-name ] [ chassis chassis-number slot slot-number ]

This command is available in any view.

Traffic filtering configuration examples

Example: Configuring traffic filtering for an interface

Network configuration

As shown in Figure 22, configure traffic filtering on GigabitEthernet 2/0/1 to deny the incoming packets with a source port number other than 21.

Figure 22 Network diagram

‌

Procedure

# Create advanced ACL 3000, and configure a rule to match packets whose source port number is not 21.

<Device> system-view

[Device] acl advanced 3000

[Device-acl-ipv4-adv-3000] rule 0 permit tcp source-port neq 21

[Device-acl-ipv4-adv-3000] quit

# Create a traffic class named classifier_1, and use ACL 3000 as the match criterion in the traffic class.

[Device] traffic classifier classifier_1

[Device-classifier-classifier_1] if-match acl 3000

[Device-classifier-classifier_1] quit

# Create a traffic behavior named behavior_1, and configure the traffic filtering action to drop packets.

[Device] traffic behavior behavior_1

[Device-behavior-behavior_1] filter deny

[Device-behavior-behavior_1] quit

# Create a QoS policy named policy, and associate traffic class classifier_1 with traffic behavior behavior_1 in the QoS policy.

[Device] qos policy policy

[Device-qospolicy-policy] classifier classifier_1 behavior behavior_1

[Device-qospolicy-policy] quit

# Apply QoS policy policy to the incoming traffic of GigabitEthernet 2/0/1.

[Device] interface gigabitethernet 2/0/1

[Device-GigabitEthernet2/0/1] qos apply policy policy inbound

Example: Configuring global traffic filtering

Network configuration

As shown in Figure 23, configure global traffic filtering to deny the incoming packets with source port number 23.

Figure 23 Network diagram

‌

Procedure

# Create advanced ACL 3000, and configure a rule to match the TCP packets with source port number 23.

<Device> system-view

[Device] acl advanced 3000

[Device-acl-ipv4-adv-3000] rule 0 permit tcp destination-port eq 23

[Device-acl-ipv4-adv-3000] quit

# Create a traffic class named match_telnet, and use ACL 3000 as the match criterion in the traffic class.

[Device] traffic classifier match_telnet

[Device-classifier-match_telnet] if-match acl 3000

[Device-classifier-match_telnet] quit

# Create a traffic behavior named deny_telnet and configure the traffic filtering action to drop packets.

[Device] qos policy deny_all_telnet

[Device-qospolicy-deny_all_telnet] classifier match_telnet behavior deny_telnet

[Device-qospolicy-deny_all_telnet] quit

# Create a QoS policy named deny_all_telnet, and associate traffic class match_telnet with traffic behavior deny_telnet in the QoS policy.

[Device] qos policy deny_all_telnet

[Device-qospolicy-deny_all_telnet] classifier match_telnet behavior deny_telnet

[Device-qospolicy-deny_all_telnet] quit

# Globally apply QoS policy deny_all_telnet to the incoming traffic.

[Device] qos apply policy deny_all_telnet global inbound

Configuring priority marking

About priority marking

Priority marking sets the priority fields or flag bits of packets to modify the priority of packets. For example, you can use priority marking to set IP precedence or DSCP for a class of IP packets to control the forwarding of these packets.

To configure priority marking to set the priority fields or flag bits for a class of packets, perform the following tasks:

1. Configure a traffic behavior with a priority marking action.

2. Associate the traffic class with the traffic behavior.

Configuring priority marking

Restrictions and guidelines

The device supports the following application destinations for priority marking:

· Interface.

· PVC.

· Control plane.

· User profile.

Procedure

1. Enter system view.

system-view

2. Define a traffic class.

a. Create a traffic class and enter traffic class view.

traffic classifier classifier-name [ operator { and | or } ]

b. Configure a match criterion.

if-match [ not ] match-criteria

By default, no match criterion is configured.

For more information about the if-match command, see ACL and QoS Command Reference.

c. Return to system view.

quit

3. Define a traffic behavior.

a. Create a traffic behavior and enter traffic behavior view.

traffic behavior behavior-name

b. Configure a priority marking action.

For configurable priority marking actions, see the remark commands in ACL and QoS Command Reference.

c. Return to system view.

quit

4. Define a QoS policy.

a. Create a QoS policy and enter QoS policy view.

qos policy policy-name

b. Associate the traffic class with the traffic behavior in the QoS policy.

classifier classifier-name behavior behavior-name

By default, a traffic class is not associated with a traffic behavior.

c. Return to system view.

quit

5. Apply the QoS policy.

For more information, see "Applying the QoS policy."

By default, no QoS policy is applied.

6. (Optional.) Display the priority marking configuration.

In standalone mode:

display traffic behavior user-defined [ behavior-name ] [ slot slot-number ]

In IRF mode:

display traffic behavior user-defined [ behavior-name ] [ chassis chassis-number slot slot-number ]

This command is available in any view.

Priority marking configuration examples

Example: Configuring priority marking

Network configuration

As shown in Figure 24, configure priority marking on the device to meet the following requirements:

Traffic source	Destination	Processing priority
Host A, B	Data server	High
Host A, B	Mail server	Medium
Host A, B	File server	Low

Figure 24 Network diagram

‌

Procedure

# Create advanced ACL 3000, and configure a rule to match packets with destination IP address 192.168.0.1.

<Device> system-view

[Device] acl advanced 3000

[Device-acl-ipv4-adv-3000] rule permit ip destination 192.168.0.1 0

[Device-acl-ipv4-adv-3000] quit

# Create advanced ACL 3001, and configure a rule to match packets with destination IP address 192.168.0.2.

[Device] acl advanced 3001

[Device-acl-ipv4-adv-3001] rule permit ip destination 192.168.0.2 0

[Device-acl-ipv4-adv-3001] quit

# Create advanced ACL 3002, and configure a rule to match packets with destination IP address 192.168.0.3.

[Device] acl advanced 3002

[Device-acl-ipv4-adv-3002] rule permit ip destination 192.168.0.3 0

[Device-acl-ipv4-adv-3002] quit

# Create a traffic class named classifier_dbserver, and use ACL 3000 as the match criterion in the traffic class.

[Device] traffic classifier classifier_dbserver

[Device-classifier-classifier_dbserver] if-match acl 3000

[Device-classifier-classifier_dbserver] quit

# Create a traffic class named classifier_mserver, and use ACL 3001 as the match criterion in the traffic class.

[Device] traffic classifier classifier_mserver

[Device-classifier-classifier_mserver] if-match acl 3001

[Device-classifier-classifier_mserver] quit

# Create a traffic class named classifier_fserver, and use ACL 3002 as the match criterion in the traffic class.

[Device] traffic classifier classifier_fserver

[Device-classifier-classifier_fserver] if-match acl 3002

[Device-classifier-classifier_fserver] quit

# Create a traffic behavior named behavior_dbserver, and configure the action of setting the local precedence value to 4.

[Device] traffic behavior behavior_dbserver

[Device-behavior-behavior_dbserver] remark local-precedence 4

[Device-behavior-behavior_dbserver] quit

# Create a traffic behavior named behavior_mserver, and configure the action of setting the local precedence value to 3.

[Device] traffic behavior behavior_mserver

[Device-behavior-behavior_mserver] remark local-precedence 3

[Device-behavior-behavior_mserver] quit

# Create a traffic behavior named behavior_fserver, and configure the action of setting the local precedence value to 2.

[Device] traffic behavior behavior_fserver

[Device-behavior-behavior_fserver] remark local-precedence 2

[Device-behavior-behavior_fserver] quit

# Create a QoS policy named policy_server, and associate traffic classes with traffic behaviors in the QoS policy.

[Device] qos policy policy_server

[Device-qospolicy-policy_server] classifier classifier_dbserver behavior behavior_dbserver

[Device-qospolicy-policy_server] classifier classifier_mserver behavior behavior_mserver

[Device-qospolicy-policy_server] classifier classifier_fserver behavior behavior_fserver

[Device-qospolicy-policy_server] quit

# Apply QoS policy policy_server to the incoming traffic of GigabitEthernet 2/0/1.

[Device] interface gigabitethernet 2/0/1

[Device-GigabitEthernet2/0/1] qos apply policy policy_server inbound

[Device-GigabitEthernet2/0/1] quit

Configuring QPPB

About QPPB

The QoS Policy Propagation Through the Border Gateway Protocol (QPPB) feature enables you to classify IP packets based on the following attributes:

· BGP community lists.

· Prefix lists.

· BGP AS paths.

Application scenarios

QPPB minimizes the QoS policy configuration and management efforts on the BGP route receiver when the network topology changes. It is suitable for a large-scaled complex network.

The QPPB feature is implemented as follows:

· The BGP route sender preclassifies routes before advertising them.

· The BGP route receiver performs the following operations:

¡ Sets the IP precedence and local QoS ID for the routes.

¡ Takes appropriate QoS actions on the packets that match the routes.

QPPB is used in the following scenarios:

· Traffic classification based on source or destination IP addresses.

· Traffic classification based on IBGP and EBGP within an autonomous system or across multiple autonomous systems.

QPPB fundamentals

QPPB works on the BGP receiver by applying a QoS policy to BGP routes with the same IP precedence or local QoS ID. It depends on the BGP route sender to preclassify routes.

The BGP route sender uses a routing policy to set route attributes for BGP routes before advertising them.

The BGP receiver performs the following operations:

· Uses a routing policy to match routes based on these route attributes.

· Sets IP precedence and local QoS ID for the matching routes.

The BGP receiver performs the following operations:

1. Compares the routes with the incoming route policy based on their BGP AS path, prefix, or community attributes.

2. Applies the IP precedence and local QoS ID to the matching routes.

3. Adds the BGP routes and their associated IP precedence and local QoS ID to the routing table.

4. Applies the IP precedence and local QoS ID to the packets sourced from or destined to the IP address in the route.

5. Takes QoS actions on the packets according to the QoS priority settings.

QPPB tasks at a glance

To configure QPPB, perform the following tasks:

1. Configuring the route sender

a. Configuring basic BGP functions

b. (Optional.) Creating a routing policy

2. Configuring the route receiver

a. Configuring basic BGP functions

b. Configuring a routing policy

c. Enabling QPPB on the route receiving interface

Configuring the route sender

Configure the BGP route sender to set route attributes for routes before advertising them.

Configuring basic BGP functions

For more information, see Layer 3—IP Routing Configuration Guide.

Creating a routing policy

Configure a routing policy to classify routes and set route attributes for the route classes. For more information, see Layer 3—IP Routing Configuration Guide.

Configuring the route receiver

Configuring basic BGP functions

For more information, see Layer 3—IP Routing Configuration Guide.

Configuring a routing policy

Configure a routing policy to perform the following operations:

· Match the route attributes set by the route sender.

· Set the IP precedence, local QoS ID, or both for the matching routes.

For more information, see Layer 3—IP Routing Configuration Guide.

Enabling QPPB on the route receiving interface

Restrictions and guidelines

For QPPB to work correctly, you must configure the QoS policy as follows:

· Use the IP precedence or local QoS ID set in the routing policy to match packets.

· Specify the mode qppb-manipulation keyword when associating a traffic behavior with a traffic class.

For more information about QoS policies, see "Configuring a QoS policy."

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Enable QPPB on the interface.

bgp-policy { destination | source } { ip-prec-map | ip-qos-map } *

By default, QPPB is disabled.

This command applies only to incoming traffic.

4. Apply a QoS policy to the interface.

qos apply policy policy-name { inbound | outbound }

By default, no QoS policy is applied to an interface.

QPPB configuration examples

Example: Configuring QPPB in an IPv4 network

Network configuration

As shown in Figure 25, all devices run BGP.

Configure QPPB so that Device B can perform the following operations:

· Receive routes.

· Set IP precedence values and local QoS IDs according to the routing policy.

· Use the QoS policy to limit the traffic rate to 512000 kbps.

Figure 25 Network diagram

‌

Procedure

1. Configure IP addresses for each interface. (Details not shown.)

2. Configure a BGP connection to Device B, and add the network 1.1.1.0/8 to the BGP routing table on Device A.

<DeviceA> system-view

[DeviceA] bgp 1000

[DeviceA-bgp] peer 168.1.1.2 as-number 2000

[DeviceA-bgp] peer 168.1.1.2 connect-interface gigabitethernet 2/0/2

[DeviceA-bgp] address-family ipv4

[DeviceA-bgp-ipv4] import-route direct

[DeviceA-bgp-ipv4] peer 168.1.1.2 enable

[DeviceA-bgp-ipv4] quit

[DeviceA-bgp] quit

3. Configure Device B:

# Configure a BGP connection to Device A.

<DeviceB> system-view

[DeviceB] bgp 2000

[DeviceB-bgp] peer 168.1.1.1 as-number 1000

[DeviceB-bgp] peer 168.1.1.1 connect-interface gigabitethernet 2/0/2

[DeviceB-bgp] address-family ipv4

[DeviceB-bgp-ipv4] peer 168.1.1.1 enable

[DeviceB-bgp-ipv4] peer 168.1.1.1 route-policy qppb import

[DeviceB-bgp-ipv4] quit

[DeviceB-bgp] quit

# Configure the routing policy qppb.

[DeviceB] route-policy qppb permit node 0

[DeviceB-route-policy-qppb-0] apply ip-precedence 1

[DeviceB-route-policy-qppb-0] apply qos-local-id 3

[DeviceB-route-policy-qppb-0] quit

# Enable QPPB on GigabitEthernet 2/0/2.

[DeviceB] interface gigabitethernet 2/0/2

[DeviceB-GigabitEthernet2/0/2] bgp-policy source ip-prec-map ip-qos-map

[DeviceB-GigabitEthernet2/0/2] quit

# Configure a QoS policy.

[DeviceB] traffic classifier qppb

[DeviceB-classifier-qppb] if-match ip-precedence 1

[DeviceB-classifier-qppb] if-match qos-local-id 3

[DeviceB-classifier-qppb] quit

[DeviceB] traffic behavior qppb

[DeviceB-behavior-qppb] car cir 512000 green pass red discard

[DeviceB-behavior-qppb] quit

[DeviceB] qos policy qppb

[DeviceB-qospolicy-qppb] classifier qppb behavior qppb mode qppb-manipulation

[DeviceB-qospolicy-qppb] quit

# Apply the QoS policy to incoming traffic on GigabitEthernet 2/0/2.

[DeviceB] interface gigabitethernet 2/0/2

[DeviceB-GigabitEthernet2/0/2] qos apply policy qppb inbound

[DeviceB-GigabitEthernet2/0/2] quit

Verifying the configuration

# Verify that the related route on Device B takes effect.

[DeviceB] display bgp routing-table ipv4 1.1.1.0

BGP local router ID: 168.1.1.2

Local AS number: 2000

Paths: 1 available, 1 best

BGP routing table information of 168.1.1.0/24:

From : 168.1.1.1 (168.1.1.1)

Rely nexthop : 168.1.1.1

Original nexthop: 168.1.1.1

Out interface : GigabitEthernet2/0/2

Route age : 00h30m12s

OutLabel : NULL

RxPathID : 0x0

TxPathID : 0x0

AS-path : 1000

Origin : incomplete

Attribute value : MED 0, pref-val 0

State : valid, external, best

IP precedence : 1

QoS local ID : 3

Traffic index : N/A

Tunnel policy : NULL

Rely tunnel IDs : N/A

# Display the QoS policy configuration on GigabitEthernet 2/0/2 of Device B.

[DeviceB] display qos policy interface gigabitethernet 2/0/2

Interface: GigabitEthernet2/0/2

Direction: Inbound

Policy: qppb

Classifier: default-class

Mode: qppb-manipulation

Matched : 51 (Packets) 4022 (Bytes)

5-minute statistics:

Forwarded: 0/28 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match any

Behavior: be

-none-

Classifier: qppb

Mode: qppb-manipulation

Matched : 0 (Packets) 0 (Bytes)

5-minute statistics:

Forwarded: 0/0 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match ip-precedence 1

If-match qos-local-id 3

Behavior: qppb

Committed Access Rate:

CIR 512000 (kbps), CBS 32000000 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets) 0 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Example: Configuring QPPB in an MPLS L3VPN

Network configuration

As shown in Figure 26, all devices run BGP.

Configure QPPB so that Device C can perform the following operations:

· Receive routes.

· Set the QPPB local QoS IDs.

· Use the QoS policy to limit the traffic rate to 200000 kbps in each direction.

Figure 26 Network diagram

‌

Table 3 Interfaces and IP address assignment

Device	Interface	IP address	Device	Interface	IP address
Device A	GE2/0/1	192.168.1.2/24	Device B	GE2/0/1	167.1.1.2/24
Device A	GE2/0/2	167.1.1.1/24	Device B	GE2/0/2	168.1.1.2/24
Device C	GE2/0/1	169.1.1.2/24	Device D	GE2/0/2	169.1.1.1/24
Device C	GE2/0/2	168.1.1.1/24	Device D	GE2/0/1	192.168.3.2/24

Procedure

1. Configure IP addresses for each interface. (Details not shown.)

2. Configure a BGP connection on Device A.

<DeviceA> system-view

[DeviceA] bgp 100

[DeviceA-bgp] peer 167.1.1.2 as-number 200

[DeviceA-bgp] peer 167.1.1.2 connect-interface gigabitethernet 2/0/2

[DeviceA-bgp] address-family ipv4

[DeviceA-bgp-ipv4] import-route direct

[DeviceA-bgp-ipv4] peer 167.1.1.2 enable

[DeviceA-bgp-ipv4] quit

[DeviceA-bgp] quit

3. Configure Device B:

# Configure a VPN instance.

<DeviceB> system-view

[DeviceB] ip vpn-instance vpn1

[DeviceB-vpn-instance-vpn1] route-distinguisher 200:1

[DeviceB-vpn-instance-vpn1] vpn-target 200:1 export-extcommunity

[DeviceB-vpn-instance-vpn1] vpn-target 200:1 import-extcommunity

[DeviceB-vpn-instance-vpn1] quit

# Configure a BGP connection.

[DeviceB] router id 1.1.1.1

[DeviceB] bgp 200

[DeviceB-bgp] peer 2.2.2.2 as-number 200

[DeviceB-bgp] peer 2.2.2.2 connect-interface loopback 0

[DeviceB-bgp] ip vpn-instance vpn1

[DeviceB-bgp-vpn1] peer 167.1.1.1 as-number 100

[DeviceB-bgp-vpn1] address-family ipv4

[DeviceB-bgp-ipv4-vpn1] peer 167.1.1.1 enable

[DeviceB-bgp-ipv4-vpn1] quit

[DeviceB-bgp] address-family vpnv4

[DeviceB-bgp-vpnv4] peer 2.2.2.2 enable

[DeviceB-bgp-vpnv4] quit

[DeviceB-bgp] quit

# Configure MPLS.

[DeviceB] mpls lsr-id 1.1.1.1

[DeviceB] mpls ldp

[DeviceB-mpls-ldp] quit

# Configure OSPF.

[DeviceB] ospf

[DeviceB-ospf-1] area 0

[DeviceB-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0

[DeviceB-ospf-1-area-0.0.0.0] network 168.1.1.0 0.0.0.255

[DeviceB-ospf-1-area-0.0.0.0] quit

[DeviceB-ospf-1] quit

# Bind GigabitEthernet 2/0/1 to VPN instance vpn1.

[DeviceB] interface gigabitethernet 2/0/1

[DeviceB-GigabitEthernet2/0/1] ip binding vpn-instance vpn1

[DeviceB-GigabitEthernet2/0/1] ip address 167.1.1.2 24

[DeviceB-GigabitEthernet2/0/1] quit

# Enable MPLS on GigabitEthernet 2/0/2.

[DeviceB] interface gigabitethernet 2/0/2

[DeviceB-GigabitEthernet2/0/2] mpls enable

[DeviceB-GigabitEthernet2/0/2] mpls ldp enable

[DeviceB-GigabitEthernet2/0/2] quit

4. Configure Device C:

# Configure a VPN instance.

<DeviceC> system-view

[DeviceC] ip vpn-instance vpn1

[DeviceC-vpn-instance-vpn1] route-distinguisher 200:1

[DeviceC-vpn-instance-vpn1] vpn-target 200:1 export-extcommunity

[DeviceC-vpn-instance-vpn1] vpn-target 200:1 import-extcommunity

[DeviceC-vpn-instance-vpn1] quit

# Configure a BGP connection.

[DeviceC] router id 2.2.2.2

[DeviceC] bgp 200

[DeviceC-bgp] peer 1.1.1.1 as-number 200

[DeviceC-bgp] peer 1.1.1.1 connect-interface loopback 0

[DeviceC-bgp] ip vpn-instance vpn1

[DeviceC-bgp-vpn1] peer 169.1.1.1 as-number 300

[DeviceC-bgp-vpn1] address-family ipv4

[DeviceC-bgp-ipv4-vpn1] peer 169.1.1.1 enable

[DeviceC-bgp-ipv4-vpn1] peer 169.1.1.1 route-policy qppb import

[DeviceC-bgp-ipv4-vpn1] quit

[DeviceC-bgp-vpn1] quit

[DeviceC-bgp] address-family vpnv4

[DeviceC-bgp-vpnv4] peer 1.1.1.1 enable

[DeviceC-bgp-vpnv4] peer 1.1.1.1 route-policy qppb import

[DeviceC-bgp-vpnv4] quit

[DeviceC-bgp] quit

# Configure a routing policy.

[DeviceC] route-policy qppb permit node 0

[DeviceC-route-policy-qppb-0] apply qos-local-id 3

[DeviceC-route-policy-qppb-0] quit

# Configure MPLS.

[DeviceC] mpls lsr-id 2.2.2.2

[DeviceC] mpls ldp

[DeviceC-mpls-ldp] quit

# Configure OSPF.

[DeviceC] ospf

[DeviceC-ospf-1] area 0

[DeviceC-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0

[DeviceC-ospf-1-area-0.0.0.0] network 168.1.1.0 0.0.0.255

[DeviceC-ospf-1-area-0.0.0.0] quit

[DeviceC-ospf-1] quit

# Configure a QoS policy.

[DeviceC] traffic classifier qppb

[DeviceC-classifier-qppb] if-match qos-local-id 3

[DeviceC-classifier-qppb] quit

[DeviceC] traffic behavior qppb

[DeviceC-behavior-qppb] car cir 200000 green pass red discard

[DeviceC-behavior-qppb] quit

[DeviceC] qos policy qppb

[DeviceC-qospolicy-qppb] classifier qppb behavior qppb mode qppb-manipulation

[DeviceC-qospolicy-qppb] quit

# Enable MPLS on GigabitEthernet 2/0/2.

[DeviceC] interface gigabitethernet 2/0/2

[DeviceC-GigabitEthernet2/0/2] mpls enable

[DeviceC-GigabitEthernet2/0/2] mpls ldp enable

# Enable QPPB on GigabitEthernet 2/0/1 and GigabitEthernet 2/0/2.

[DeviceC-GigabitEthernet2/0/2] bgp-policy source ip-qos-map

[DeviceC-GigabitEthernet2/0/2] quit

[DeviceC] interface gigabitethernet 2/0/1

[DeviceC-GigabitEthernet2/0/1] bgp-policy source ip-qos-map

[DeviceC-GigabitEthernet2/0/1] quit

# Bind GigabitEthernet 2/0/1 to VPN instance vpn1.

[DeviceC] interface gigabitethernet 2/0/1

[DeviceC-GigabitEthernet2/0/1] ip binding vpn-instance vpn1

[DeviceC-GigabitEthernet2/0/1] ip address 169.1.1.2 24

# Apply QoS policy qppb to the incoming traffic of GigabitEthernet 2/0/1.

[DeviceC-GigabitEthernet2/0/1] qos apply policy qppb inbound

[DeviceC-GigabitEthernet2/0/1] quit

# Apply QoS policy qppb to the incoming traffic of GigabitEthernet 2/0/2.

[DeviceC] interface gigabitethernet 2/0/2

[DeviceC-GigabitEthernet2/0/2] qos apply policy qppb inbound

5. Configure a BGP connection on Device D.

<DeviceD> system-view

[DeviceD] bgp 300

[DeviceD-bgp] peer 169.1.1.2 as-number 200

[DeviceD-bgp] peer 169.1.1.2 connect-interface gigabitethernet 2/0/2

[DeviceD-bgp] address-family ipv4

[DeviceD-bgp-ipv4] peer 169.1.1.2 enable

[DeviceD-bgp-ipv4] import-route direct

[DeviceD-bgp-ipv4] quit

Verifying the configuration

# Verify that the related routes on Device A take effect.

[DeviceA] display ip routing-table

Destinations : 18 Routes : 18

Destination/Mask Proto Pre Cost NextHop Interface

0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

167.1.1.0/24 Direct 0 0 167.1.1.1 GE2/0/2

167.1.1.0/32 Direct 0 0 167.1.1.1 GE2/0/2

167.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

167.1.1.255/32 Direct 0 0 167.1.1.1 GE2/0/2

169.1.1.0/24 BGP 255 0 167.1.1.2 GE2/0/2

192.168.1.0/24 Direct 0 0 192.168.1.2 GE2/0/1

192.168.1.0/32 Direct 0 0 192.168.1.2 GE2/0/1

192.168.1.2/32 Direct 0 0 127.0.0.1 InLoop0

192.168.1.255/32 Direct 0 0 192.168.1.2 GE2/0/1

192.168.3.0/24 BGP 255 0 167.1.1.2 GE2/0/2

224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0

224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0

255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

# Verify that the related routes on Device B take effect.

[DeviceB] display ip routing-table

Destinations : 14 Routes : 14

Destination/Mask Proto Pre Cost NextHop Interface

0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

1.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

2.2.2.2/32 OSPF 10 1 168.1.1.1 GE2/0/2

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

168.1.1.0/24 Direct 0 0 168.1.1.2 GE2/0/2

168.1.1.0/32 Direct 0 0 168.1.1.2 GE2/0/2

168.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0

168.1.1.255/32 Direct 0 0 168.1.1.2 GE2/0/2

224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0

224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0

255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

[DeviceB] display ip routing-table vpn-instance vpn1

Destinations : 16 Routes : 16

Destination/Mask Proto Pre Cost NextHop Interface

0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

167.1.1.0/24 Direct 0 0 167.1.1.2 GE2/0/1

167.1.1.0/32 Direct 0 0 167.1.1.2 GE2/0/1

167.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0

167.1.1.255/32 Direct 0 0 167.1.1.2 GE2/0/1

169.1.1.0/24 BGP 255 0 2.2.2.2 GE2/0/2

192.168.1.0/24 BGP 255 0 167.1.1.1 GE2/0/1

192.168.2.0/24 BGP 255 0 167.1.1.1 GE2/0/1

192.168.3.0/24 BGP 255 0 2.2.2.2 GE2/0/2

224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0

224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0

255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

# Verify that the related routes on Device C take effect.

[DeviceC] display ip routing-table

Destinations : 14 Routes : 14

Destination/Mask Proto Pre Cost NextHop Interface

0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

1.1.1.1/32 OSPF 10 1 168.1.1.2 GE2/0/2

2.2.2.2/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

168.1.1.0/24 Direct 0 0 168.1.1.1 GE2/0/2

168.1.1.0/32 Direct 0 0 168.1.1.1 GE2/0/2

168.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

168.1.1.255/32 Direct 0 0 168.1.1.1 GE2/0/2

224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0

224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0

255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

[DeviceC] display ip routing-table vpn-instance vpn1

Destinations : 16 Routes : 16

Destination/Mask Proto Pre Cost NextHop Interface

0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

167.1.1.0/24 BGP 255 0 1.1.1.1 GE2/0/2

169.1.1.0/24 Direct 0 0 169.1.1.2 GE2/0/1

169.1.1.0/32 Direct 0 0 169.1.1.2 GE2/0/1

169.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0

169.1.1.255/32 Direct 0 0 169.1.1.2 GE2/0/1

192.168.1.0/24 BGP 255 0 1.1.1.1 GE2/0/2

192.168.2.0/24 BGP 255 0 169.1.1.1 GE2/0/1

192.168.3.0/24 BGP 255 0 169.1.1.1 GE2/0/1

224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0

224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0

255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

# Verify that the related routes on Device D take effect.

[DeviceD] display ip routing-table

Destinations : 18 Routes : 18

Destination/Mask Proto Pre Cost NextHop Interface

0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

167.1.1.0/24 BGP 255 0 169.1.1.2 GE2/0/2

169.1.1.0/24 Direct 0 0 169.1.1.1 GE2/0/2

169.1.1.0/32 Direct 0 0 169.1.1.1 GE2/0/2

169.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

169.1.1.255/32 Direct 0 0 169.1.1.1 GE2/0/2

192.168.1.0/24 BGP 255 0 169.1.1.2 GE2/0/2

192.168.3.0/24 Direct 0 0 192.168.3.2 GE2/0/1

192.168.3.0/32 Direct 0 0 192.168.3.2 GE2/0/1

192.168.3.2/32 Direct 0 0 127.0.0.1 InLoop0

192.168.3.255/32 Direct 0 0 192.168.3.2 GE2/0/1

224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0

224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0

255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

# Display the QoS policy configuration in the inbound direction on Device C.

[DeviceC] display qos policy interface inbound

Interface: GigabitEthernet2/0/1

Direction: Inbound

Policy: qppb

Classifier: default-class

Mode: qppb-manipulation

Matched : 312 (Packets) 18916 (Bytes)

5-minute statistics:

Forwarded: 0/24 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match any

Behavior: be

-none-

Classifier: qppb

Mode: qppb-manipulation

Matched : 0 (Packets) 0 (Bytes)

5-minute statistics:

Forwarded: 0/0 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match qos-local-id 3

Behavior: qppb

Committed Access Rate:

CIR 200000 (kbps), CBS 1250000 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets) 0 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Interface: GigabitEthernet2/0/2

Direction: Inbound

Policy: qppb

Classifier: default-class

Mode: qppb-manipulation

Matched : 311 (Packets) 23243 (Bytes)

5-minute statistics:

Forwarded: 0/24 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match any

Behavior: be

-none-

Classifier: qppb

Mode: qppb-manipulation

Matched : 0 (Packets) 0 (Bytes)

5-minute statistics:

Forwarded: 0/0 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match qos-local-id 3

Behavior: qppb

Committed Access Rate:

CIR 200000 (kbps), CBS 12500480 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets) 0 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Example: Configuring QPPB in an IPv6 network

Network configuration

As shown in Figure 27, all devices run BGP.

Configure QPPB so that Device B can perform the following operations:

· Receive routes.

· Set the QPPB IP precedence value.

· Use the QoS policy to limit the rate of traffic with the IP precedence value to 512000 kbps.

Figure 27 Network diagram

‌

Procedure

1. Configure IPv6 addresses for each interface. (Details not shown.)

2. Configure BGP on Device A.

<DeviceA> system-view

[DeviceA] bgp 1000

[DeviceA] peer 168::2 as-number 2000

[DeviceA] peer 168::2 connect-interface gigabitethernet 2/0/2

[DeviceA-bgp] address-family ipv6

[DeviceA-bgp-ipv6] peer 168::2 enable

[DeviceA-bgp-ipv6] import-route direct

[DeviceA-bgp-ipv6] quit

[DeviceA-bgp] quit

3. Configure Device B:

# Configure BGP.

<DeviceB> system-view

[DeviceB] bgp 2000

[DeviceB] peer 168::1 as-number 1000

[DeviceB] peer 168::1 connect-interface gigabitethernet 2/0/2

[DeviceB-bgp] address-family ipv6

[DeviceB-bgp-ipv6] peer 168::1 enable

[DeviceB-bgp-ipv6] peer 168::1 route-policy qppb import

[DeviceB-bgp-ipv6] quit

[DeviceB-bgp] quit

# Configure a routing policy.

[DeviceB] route-policy qppb permit node 0

[DeviceB-route-policy-qppb-0] apply ip-precedence 4

[DeviceB-route-policy-qppb-0] apply qos-local-id 3

[DeviceB-route-policy-qppb-0] quit

# Enable QPPB on GigabitEthernet 2/0/2.

[DeviceB] interface gigabitethernet 2/0/2

[DeviceB-GigabitEthernet2/0/2] bgp-policy source ip-prec-map ip-qos-map

# Configure a QoS policy.

[DeviceB] traffic classifier qppb

[DeviceB-classifier-qppb] if-match ip-precedence 4

[DeviceB-classifier-qppb] if-match qos-local-id 3

[DeviceB-classifier-qppb] quit

[DeviceB] traffic behavior qppb

[DeviceB-behavior-qppb] car cir 512000 red discard

[DeviceB-behavior-qppb] quit

[DeviceB] qos policy qppb

[DeviceB-qospolicy-qppb] classifier qppb behavior qppb mode qppb-manipulation

[DeviceB-qospolicy-qppb] quit

# Apply the QoS policy to the incoming traffic of GigabitEthernet 2/0/2.

[DeviceB] interface gigabitethernet 2/0/2

[DeviceB-GigabitEthernet2/0/2] qos apply policy qppb inbound

[DeviceB-GigabitEthernet2/0/2] quit

Verifying the configuration

# Verify that the related routes on Device A take effect.

[DeviceA] display bgp routing-table ipv6 2:: 64

BGP local router ID: 0.0.0.0

Local AS number: 1000

Paths: 1 available, 1 best

BGP routing table information of 168::/64:

Imported route.

Original nexthop: ::

Out interface : GigabitEthernet2/0/2

Route age : 00h17m18s

OutLabel : NULL

RxPathID : 0x0

TxPathID : 0x0

AS-path : (null)

Origin : incomplete

Attribute value : MED 0, pref-val 32768

State : valid, local, best

IP precedence : N/A

QoS local ID : N/A

Traffic index : N/A

Tunnel policy : NULL

Rely tunnel IDs : N/A

# Verify that the related routes on Device B take effect.

[DeviceB] display bgp routing-table ipv6 1:: 64

BGP local router ID: 0.0.0.0

Local AS number: 2000

Paths: 1 available, 1 best

BGP routing table information of 168::/64:

Imported route.

Original nexthop: ::

Out interface : GigabitEthernet2/0/2

Route age : 00h05m17s

OutLabel : NULL

RxPathID : 0x0

TxPathID : 0x0

AS-path : (null)

Origin : incomplete

Attribute value : MED 0, pref-val 32768

State : valid, local, best

IP precedence : 4

QoS local ID : 3

Traffic index : N/A

Tunnel policy : NULL

Rely tunnel IDs : N/A

# Display the configuration and statistics for the QoS policy applied to GigabitEthernet 2/0/2 on Device C.

[DeviceC] display qos policy interface gigabitethernet 2/0/2

Interface: GigabitEthernet2/0/2

Direction: Inbound

Policy: qppb

Classifier: default-class

Mode: qppb-manipulation

Matched : 0 (Packets) 0 (Bytes)

5-minute statistics:

Forwarded: 0/0 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match any

Behavior: be

-none-

Classifier: qppb

Mode: qppb-manipulation

Matched : 0 (Packets) 0 (Bytes)

5-minute statistics:

Forwarded: 0/0 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match ip-precedence 4

If-match qos-local-id 3

Behavior: qppb

Committed Access Rate:

CIR 512000 (kbps), CBS 32000000 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets) 0 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Appendixes

Appendix A Acronyms

Table 4 Appendix A Acronyms

Acronym	Full spelling
AF	Assured Forwarding
BE	Best Effort
BQ	Bandwidth Queuing
CAR	Committed Access Rate
CBS	Committed Burst Size
CBQ	Class Based Queuing
CE	Congestion Experienced
CIR	Committed Information Rate
CQ	Custom Queuing
DCBX	Data Center Bridging Exchange Protocol
DiffServ	Differentiated Service
DSCP	Differentiated Services Code Point
EBS	Excess Burst Size
ECN	Explicit Congestion Notification
EF	Expedited Forwarding
FIFO	First in First out
FQ	Fair Queuing
GMB	Guaranteed Minimum Bandwidth
GTS	Generic Traffic Shaping
IntServ	Integrated Service
ISP	Internet Service Provider
LLQ	Low Latency Queuing
LSP	Label Switched Path
MPLS	Multiprotocol Label Switching
PE	Provider Edge
PIR	Peak Information Rate
PQ	Priority Queuing
PW	Pseudowire
QoS	Quality of Service
QPPB	QoS Policy Propagation Through the Border Gateway Protocol
RED	Random Early Detection
RSVP	Resource Reservation Protocol
RTP	Real-Time Transport Protocol
SP	Strict Priority
ToS	Type of Service
VoIP	Voice over IP
VPN	Virtual Private Network
WFQ	Weighted Fair Queuing
WRED	Weighted Random Early Detection
WRR	Weighted Round Robin

Appendix B Default priority maps

Table 5

Table 6 Default dot1p-lp priority map

Input priority value	dot1p-lp map
dot1p	lp
0	2
1	0
2	1
3	3
4	4
5	5
6	6
7	7

Table 7 Default dscp-lp priority map

Input priority value	dscp-lp map
dscp	lp
0 to 7	0
8 to 15	1
16 to 23	2
24 to 31	3
32 to 39	4
40 to 47	5
48 to 55	6
56 to 63	7

Table 8 Default lp-dot1p priority map

Input priority value	lp-dot1p map
lp	dot1p
0	1
1	2
2	0
3	3
4	4
5	5
6	6
7	7

‌

Appendix C Introduction to packet precedence

IP precedence and DSCP values

Figure 28 ToS and DS fields

As shown in Figure 28, the ToS field in the IP header contains 8 bits. The first 3 bits (0 to 2) represent IP precedence from 0 to 7. According to RFC 2474, the ToS field is redefined as the differentiated services (DS) field. A DSCP value is represented by the first 6 bits (0 to 5) of the DS field and is in the range 0 to 63. The remaining 2 bits (6 and 7) are reserved.

Table 9 IP precedence

IP precedence (decimal)	IP precedence (binary)	Description
0	000	Routine
1	001	priority
2	010	immediate
3	011	flash
4	100	flash-override
5	101	critical
6	110	internet
7	111	network

Table 10 DSCP values

DSCP value (decimal)	DSCP value (binary)	Description
46	101110	ef
10	001010	af11
12	001100	af12
14	001110	af13
18	010010	af21
20	010100	af22
22	010110	af23
26	011010	af31
28	011100	af32
30	011110	af33
34	100010	af41
36	100100	af42
38	100110	af43
8	001000	cs1
16	010000	cs2
24	011000	cs3
32	100000	cs4
40	101000	cs5
48	110000	cs6
56	111000	cs7
0	000000	be (default)

802.1p priority

802.1p priority lies in the Layer 2 header. It applies to occasions where Layer 3 header analysis is not needed and QoS must be assured at Layer 2.

Figure 29 An Ethernet frame with an 802.1Q tag header

As shown in Figure 29, the 4-byte 802.1Q tag header contains the 2-byte tag protocol identifier (TPID) and the 2-byte tag control information (TCI). The value of the TPID is 0x8100. Figure 30 shows the format of the 802.1Q tag header. The Priority field in the 802.1Q tag header is called 802.1p priority, because its use is defined in IEEE 802.1p. Table 11 shows the values for 802.1p priority.

Figure 30 802.1Q tag header

Table 11 Description on 802.1p priority

802.1p priority (decimal)	802.1p priority (binary)	Description
0	000	best-effort
1	001	background
2	010	spare
3	011	excellent-effort
4	100	controlled-load
5	101	video
6	110	voice
7	111	network-management

EXP values

The EXP field is in MPLS labels for MPLS QoS purposes. As shown in Figure 31, the EXP field is 3-bit long and is in the range of 0 to 7.

Figure 31 MPLS label structure

11-ACL and QoS Configuration Guide

QoS techniques in a network

Defining a traffic class

Defining a traffic behavior

Defining a QoS policy

About this task

Restrictions and guidelines

Prerequisites

Procedure

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Applying the QoS policy to a control plane

About this task

Procedure

About this task

Procedure

Applying the QoS policy to a user profile

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Priority mapping process

Priority mapping tasks at a glance

Configuring a priority map

Procedure

About this task

Procedure

Network configuration

Procedure

Network configuration

Procedure

Traffic evaluation and token buckets

Token bucket features

Evaluating traffic with the token bucket

Complicated evaluation

Configuring traffic policing

Restrictions and guidelines

Procedure

Configuring CAR-list-based traffic policing

Configuring ACL-based traffic policing

Configuring traffic policing for a user profile

About this task

Procedure

Configuring GTS

Restrictions and guidelines

Procedure

Configuring the rate limit

Network requirements

Procedure

Network configuration

Procedure

Congestion management technique comparison

Setting the FIFO queue size

Restrictions and guidelines

Procedure

Network configuration

Procedure

Configuring CQ