-
FlexWAN and Enhanced FlexWAN Modules Installation and Configuration Guide
-
Preface
-
FlexWAN and Enhanced FlexWAN Modules Overview
-
FlexWAN and Enhanced FlexWAN Software Features Configuration Information
-
Configuring Multiprotocol Label Switching on FlexWAN and Enhanced FlexWAN Modules
-
Configuring QoS on the FlexWAN and Enhanced FlexWAN Modules
-
Upgrading Field-Programmable Devices on the Enhanced FlexWAN Module
-
Multilink Feature Support
-
Table Of Contents
Configuring QoS on the FlexWAN and Enhanced FlexWAN Modules
Understanding QoS on FlexWAN and Enhanced FlexWAN
Restrictions and Usage Guidelines
Additional QoS Features and Resources
Restrictions and Usage Guidelines
Distributed Network-Based Application Recognition
Restrictions and Usage Guidelines
Configuring Priority Percent on a Policy- Map
Restrictions and Usage Guidelines
Configuring Class-Based Weighted Fair Queuing
Restrictions and Usage Guidelines
Configuring a Service Policy in the Policy Map
Configuring CBWFQ for MLPPP Links
Flow-Based Weighted Fair Queuing (WFQ)
Configuring Low Latency Queuing
Restrictions and Usage Guidelines
Configuring LLQ for MLPPP Links
Distribution of Remaining Bandwidth
Configuring Weighted Random Early Detection
Restrictions and Usage Guidelines
Restrictions and Usage Guidelines
Configuring Hierarchical Traffic Shaping
Restrictions and Usage Guidelines
Restrictions and Usage Guidelines
Configuring QoS for ATM VC Access Trunk Emulation
Configuring ATM Cell Loss Priority Setting
Configuring QoS on Bridged Interfaces
Restrictions and Usage Guidelines
Configuring QoS on Bridged Interfaces
QoS over Bridging Class-Map and Policy-Map Statements
Sample Interface Configurations
QoS over Bridging Configuration Examples
FlexWAN and Enhanced FlexWAN MPLS QoS Feature Summary
Using MPLS QoS with FlexWAN and Enhanced FlexWAN Modules
IP to MPLS Edge (Ingress Interface) QoS Features
MPLS to IP Edge (Egress Interface) QoS Features
FlexWAN MPLS QoS with Supervisor Engine 2
Supported FlexWAN MPLS QoS Features
Understanding the MPLS Experimental Field
Setting the MPLS Experimental Field
Configuring Class-Based Marking for MPLS
Configuring a Class Map to Classify MPLS Packets
Configuring a Policy Map to Set the MPLS Experimental Field
Ingress PE Router Configuration
Core Router Ingress and Egress Interface Configuration
Configuring QoS with Any Transport over MPLS
How to Set Experimental Bits with AToM
Ethernet over MPLS and EXP Bits
Displaying the Traffic Policy Assigned to an Interface
ATM AAL5 over MPLS and EXP Bits
ATM Cell Relay over MPLS and EXP Bits
Frame Relay over MPLS and EXP Bits
Setting the Priority of Packets with EXP Bits
EoMPLS QoS Example—Displaying the Traffic Policy Assigned to an Interface
Ethernet over MPLS QoS Example—Configuring QoS on VLAN
ATM over MPLS QoS Example—Configuring Ingress QoS
Frame Relay over MPLS QoS Example—Configuring Ingress QoS
DE/CLP and EXP Mapping on Frame Relay and ATM over MPLS VC
Configuring Match on ATM CLP Bit for Ingress Policy
Match on ATM CLP Bit Configuration Example
Verifying Match on ATM CLP Bit
Guideline for Match on FR-DE Bit
Configuring Match on FR-DE Bit for Ingress Policy
Example of Configuring a Match on the FR-DE Bit
Examples of Matching on the FR-DE Bit Verification
Configuring Set on ATM CLP Bit for Egress Policy
Set on ATM CLP Bit Configuration Example
Match on ATM CLP Bit Verification Example
Configuring Set on FR-DE Bit for the Egress Policy
Set on FR-DE Configuration Example
Set on FR-DE Verification Example
HQoS for Ethernet over MPLS Virtual Circuits
Prerequisites for the HQoS for EoMPLS VCs Feature
Restrictions for the HQoS for EoMPLS VCs Feature
Configuring the HQoS for EoMPLS VCs Feature
Creating and Assigning a Policy Map to Mark the QoS Group at the Incoming Interface
Configuring the Class Map to Match on a QoS Group
Creating the Child Policy Map for the Egress Interface
Configuring the Class Maps for Matching on an Input VLAN
Creating the Parent Policy Map and Attaching It to the Egress Interface
Configuration Examples for the HQoS for EoMPLS VCs Feature
Simple Hierarchical Configuration Example
Complete Hierarchical QoS Example
Multiple Parent Policies Using the Same Child Policy Example
Common Class-Map Templates Example
Configuring QoS on the FlexWAN and Enhanced FlexWAN Modules
This chapter describes how to configure Quality of Service (QoS) on the Cisco 7600 FlexWAN and Enhanced FlexWAN modules.
Note
Cisco IOS Release 12.2SRA and later releases do not support the FlexWAN module or Supervisor Engine 2. These releases support the Enhanced FlexWAN module and the Sup720 and Sup32. In addition, note that Cisco IOS Release 12.2SRB introduced support for the Route Switch Processor 720 (RSP720).
This chapter contains the following sections:
•
•
•
•
•
•
•
Understanding QoS on FlexWAN and Enhanced FlexWAN
Each FlexWAN and Enhanced FlexWAN module has both ingress and egress QoS capability.
Ingress QoS Capability
Because the FlexWAN and Enhanced FlexWAN modules provide for both policing and marking in the FlexWAN module itself, packets that are received through a FlexWAN port bypass the QoS functionality of the policy feature card (PFC). As a result, the QoS functionality of the PFC is not required. Policing and marking on the FlexWAN is configured by means of the Modular QoS command-line interface.
QoS features are performed by the CPUs on the FlexWAN and Enhanced FlexWAN modules; enabling more complex QoS features may affect port adapter performance.
The FlexWAN and Enhanced FlexWAN modules support the following QoS implementations on ingress ports:
•
•
•
•
•
•
•
•
Egress QoS Capability
The outbound QoS capabilities of the FlexWAN module include policing, marking, Class-Based Weighted Fair Queuing (CBWFQ), Weighted Random Early Detection (WRED), and traffic shaping. All features are configured using the Modular QoS command-line interface. As the features are implemented in Cisco IOS software, there are few limits on the complexity of the QoS configuration. However, as the complexity increases, the probability of a noticeable performance impact also increases.
The FlexWAN and Enhanced FlexWAN modules support the following QoS implementations on egress ports:
•
•
•
•
•
•
•
•
Note
Note
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xe/120xe5/mqc/
mcli.htm
IPv6 Hop-by-Hop Rate Limiter
The IPv6 Hop-by-Hop (HBH) extension header is part of the original specification of the IPv6 protocol (RFC 2460). It is identified by the next header field being 0, and when present, this extension header must always be the first extension header (EH) to follow the main header. Because a node must process any received packet that has an HBH extension header, forwarding of packets containing the HBH header can represent or be used as a security threat.
The IPv6 Hop- by- Hop (IPv6 HBH) Rate Limiter feature provides protection from denial of service (DoS) attacks by allowing you to rate limit IPv6 HBH packets.
To connect to a specific line card to execute the test platform police set command or the test platform police get command, use the attach command in privileged EXEC mode. You can then set the IPv6 internal police rate by using the test platform police set command in privileged EXEC mode from the line card console.
Restrictions and Usage Guidelines
When rate limiting IPv6 HBH packets on the FlexWAN card, follow these restrictions and usage guidelines:
•
–
–
–
–
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Example
The following sample configuration shows how to set the IPv6 internal police rate.
FLEXWAN-ENH-2/0#test platform ?
atom PLATFORM specific atom test commands
debugger Debugger utilities
fwd-idx Test the Forwarding Index Mangager
hardware Test hardware platform information
police IPv6 Aggregate Policer
software Test platform software information
FLEXWAN-ENH-2/0#test platform pol
FLEXWAN-ENH-2/0#test platform police ?
ipv6 IPv6 packet with HBH header
FLEXWAN-ENH-2/0#test platform police ip
FLEXWAN-ENH-2/0#test platform police ipv6 ?
get Get IPv6 policer rate
set Set IPv6 Policer rate
<cr>
FLEXWAN-ENH-2/0#test platform police ipv6
IPv6 HBH packet policer rate = 2000 pps, Rate in rommon = 2000 pps
FLEXWAN-ENH-2/0#test platform police ipv6 get
IPv6 HBH packet policer rate = 2000 pps, Rate in rommon = 2000 pps
FLEXWAN-ENH-2/0#test platform police ipv6 set
% Incomplete command.
FLEXWAN-ENH-2/0#test platform police ipv6 set ?
<0-25600> IPv6 HBH policer rate in pps
FLEXWAN-ENH-2/0#test platform police ipv6 set 0
Turning off the IPv6 HBH Policer
IPv6 HBH packet policer rate = 0 pps
FLEXWAN-ENH-2/0#test platform police ipv6 set 1000
IPv6 HBH packet policer rate = 1000 pps
FLEXWAN-ENH-2/0#test platform police ipv6 get
IPv6 HBH packet policer rate = 1000 pps, Rate in rommon = 1000 pps
FLEXWAN-ENH-2/0#test platform police ipv6 set
FLEXWAN-ENH-2/0#test platform police ipv6 set ?
<0-25600> IPv6 HBH policer rate in pps
FLEXWAN-ENH-2/0#test platform police ipv6 set 25600
IPv6 HBH packet policer rate = 25600 pps
FLEXWAN-ENH-2/0#test platform police ipv6 set 25601
^
% Invalid input detected at '^' marker.
FLEXWAN-ENH-2/0#test platform police ipv6 set 1000
IPv6 HBH packet policer rate = 1000 pps
FLEXWAN-ENH-2/0#
FLEXWAN-ENH-2/0#test platform police ipv6 get
IPv6 HBH packet policer rate = 1000 pps, Rate in rommon = 1000 pps
FLEXWAN-ENH-2/0#sho
FLEXWAN-ENH-2/0#show pl
FLEXWAN-ENH-2/0#show platform so
FLEXWAN-ENH-2/0#show platform software ip
FLEXWAN-ENH-2/0#show platform software ipv6-policer
IPv6 HBH packet policer rate = 1000 pps
Rate in rommon = 1000 pps
Packets dropped = 2196472, Packets punted to RP = 525811
FLEXWAN-ENH-2/0#
FLEXWAN-ENH-2/0#
Terminate IPC console session? [confirm]
Left#
Left#hw-module module 2 reset
Proceed with reload of module?[confirm]
% reset issued for module 2
Left#
Left#att 2
Entering CONSOLE for slot 2
Type "^C^C^C" to end this session
FLEXWAN-ENH-2/0>
FLEXWAN-ENH-2/0>
FLEXWAN-ENH-2/0>en
FLEXWAN-ENH-2/0#sh platform software ipv6-policer
IPv6 HBH packet policer rate = 1000 pps
Rate in rommon = 1000 pps
Packets dropped = 297850, Packets punted to RP = 37424
FLEXWAN-ENH-2/0#
On fresh bootup default policer is stored in Rommon too.
SIP-200-6#show platform software ipv6-policer
IPv6 HBH packet policer rate = 1000 pps
Rate in rommon = 1000 pps
Packets dropped = 0, Packets punted to RP = 0
Use the show platform software ipv6-policer command to display the IPv6 packet policer and rommon rates in packets per second.
FlexWAN-ENH-3/0#show platform software ipv6-policer
IPv6 HBH packet policer rate = 1 pps
Rate in rommon = 1 pps
Packets dropped = 0, Packets punted to RP = 12
FlexWAN-ENH-3/0#
Additional QoS Features and Resources
•
–
–
•
–
–
•
–
Classification
Classification entails using a traffic descriptor to categorize a packet within a specific group to define that packet and make it accessible for QoS handling on the network. Using packet classification, you can partition network traffic into multiple priority levels or classes of service.
For more information, see the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at:
http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/fqos_c.html
Configuring Classification
This section contains information for configuring classification for the FlexWAN and Enhanced FlexWAN QoS features.
The FlexWAN and Enhanced FlexWAN modules can classify traffic based on the following criteria:
•
•
Note
•
•
•
•
•
•
•
•
•
•
•
•
•
Use the class-map commands in global configuration mode to specify the name of the class map and define the class matching criteria.
Restrictions and Usage Guidelines
The classification restrictions and usage guidelines are as follows:
•
•
Configuration Tasks
To configure classification, perform the following steps in global configuration mode on the MSFC:
This example shows how to configure a class map named ipp5, and enter a match statement for IP precedence 5:
Router(config)# class-map ipp5Router(config-cmap)# match ip precedence 5Router(config-cmap)#This example shows how to display class-map information for a specific class map using the show class-map command:
Router# show class-map ipp5Class Map match-all ipp5 (id 1)Match ip precedence 5Distributed Network-Based Application Recognition
Distributed Network-Based Application Recognition (DNBAR) is a classification engine used with the FlexWAN and Enhanced FlexWAN modules that recognizes a wide variety of applications, including web-based and other difficult-to-classify protocols that utilize dynamic TCP/UDP port assignments. When an application is recognized and classified by DNBAR, a network can invoke services for that specific application. DNBAR ensures that network bandwidth is used efficiently by working with QoS features to provide the following features:
•
•
•
•
For more information, see Distributed Network-Based Application Recognition at:
http://www.cisco.com/en/US/docs/ios/12_1/12_1e11/feature/guide/dtnbarad.html
Policing
Policing rate limits a particular flow or group of flows using a token bucket policer. Packets not conforming to the user-specified rate and burst parameters are considered to be out-of-profile and are subject to either being dropped or marked down.
For more information, see the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_c/fqcprt4/qcfpolsh.htm
The FlexWAN and Enhanced FlexWAN modules support percentage-based policing and priority percent on a policy map.
Additionally, you can mark packets by setting the following:
•
•
•
•
•
•
Configuring Policing
Use the police command to enable policing on a class of traffic. The police command imposes a maximum rate on a particular class of traffic and provides the following actions if the rate is exceeded:
•
•
•
Note
Restrictions and Usage Guidelines
The classification restrictions and usage guidelines are as follows:
•
•
–
–
–
For each of the above states, policing is accomplished through one of these actions: drop and transmit with re-marking or drop and transmit without re-marking.
For additional information, see Traffic Policing at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dtpoli.htm
Configuration Tasks
To configure policing, perform the following steps in global configuration mode on the MSFC:
This example shows a traffic policing configuration with the average rate at 8000 bits per second, the normal burst size at 2000 bytes, and the excess burst size at 4000 bytes:
Router(config)# class-map acgroup2Router(config-cmap)# match access-group 2Router(config-cmap)# exitRouter(config)# policy-map policeRouter(config-pmap)# class acgroup2Router(config-pmap-c)# police 8000 2000 4000 conform-action transmit exceed-action set-qos-transmit 4 violate-action dropRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fastethernet 0/0Router(config-if)# service-policy input policeUse the following commands to verify policing:
This example shows how to display policing statistics using the show policy-map interface command in the EXEC mode.
Router# show policy-map interfacePOS6/1/0service-policy output: xclass-map: a (match-all)0 packets, 0 bytes5 minute rate 0 bpsmatch: ip precedence 0police:1000000 bps, 10000 limit, 10000 extended limitconformed 0 packets, 0 bytes; action: transmitexceeded 0 packets, 0 bytes; action: dropconformed 0 bps, exceed 0 bps, violate 0 bpsConfiguring Priority Percent on a Policy- Map
To configure priority percent on a policy map, follow these commands:
Note
The following example shows a sample configuration of the priority percent on a policy-map:
class-map voipmatch ip precedence 3policy-map llqclass voippriority percent <1-100>Marking
Associating a packet with an IP Precedence or IP DSCP marking allows users to classify traffic based on IP Precedence and IP DSCP value, depending on which value is marked. These markings can be used to identify traffic within the network, and other interfaces can match traffic based on the IP Precedence or DSCP markings.
For more information, see the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at:
Configuring Marking
Marking sets various attributes of packets belonging to a particular class. You can mark IP and MPLS packets with the FlexWAN and Enhanced FlexWAN modules.
In Cisco IOS Release 12.2SR and later releases, you can also mark bridged Ethernet packets with the Enhanced FlexWAN module. See "Configuring QoS on Bridged Interfaces" section for more information.
Note
Restrictions and Usage Guidelines
The marking restrictions and usage guidelines are as follows:
•
–
–
–
Note
–
Configuration Tasks
To configure marking, perform the following steps in global configuration mode on the MSFC:
This examples shows the creation of a service policy called policy1. This service policy is associated to a previously defined classification policy through the use of the class command. This example assumes that a classification policy called class1 was previously configured.
Router(config)# policy-map policy1Router(config-pmap)# class class1Router(config-pmap-c)# set ip precedence 1Use the following commands to verify marking:
Congestion Management
Congestion management features allow you to control congestion by determining the order in which packets are sent out an interface based on priorities assigned to those packets. Congestion management entails the creation of queues, assignment of packets to those queues based on the classification of the packets, and scheduling of the packets in a queue for transmission. The congestion management QoS feature offers four types of queueing protocols, each of which allows you to specify creation of a different number of queues, affording greater or lesser degrees of differentiation of traffic, and to specify the order in which that traffic is sent.
For more information, see the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at:
The following sections describe congestion management on the FlexWAN and Enhanced FlexWAN modules:
•
•
•
•
•
•
Configuring Class-Based Weighted Fair Queuing
This section contains information for configuring Class-Based Weighted Fair Queueing (CBWFQ). CBWFQ provides guaranteed bandwidth rate to a non-priority class. Under congestion conditions, the class receives the guaranteed bandwidth. To configure CBWFQ, use one of the three forms of the bandwidth command:
•
•
•
Note
The FlexWAN and Enhanced FlexWAN modules also support distributed CBWFQ. For more information, see Distributed Class-Based Weighted Fair Queueing and Distributed Weighted Random Early Detection at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dtcbwred.htm
Restrictions and Usage Guidelines
•
•
•
•
•
•
•
•
Configuring a Service Policy in the Policy Map
To configure CBWFQ, use the Modular QoS command-line interface. Define the class of traffic with the class-map command, create a policy map that contains the bandwidth command, and apply the policy to the appropriate interface with the service-policy command.
To configure the class of traffic, see the "Configuring Classification" section. To configure a policy with CBWFQ and to assign the policy to an interface, perform the following tasks in global configuration mode:
This example shows a service policy called policy1 that specifies the amount of bandwidth to allocate for traffic classes 1 and 2:
Router(config)# class-map class1 Router(config-cmap)# match ip dscp 30Router(config-cmap)# exitRouter(config)# class-map class2 Router(config-cmap)# match ip dscp 10Router(config-cmap)# exit
Router(config)# policy-map policy1Router(config-pmap)# class class1Router(config-pmap-c)# bandwidth 30000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# class class2Router(config-pmap-c)# bandwidth 20000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)#
Router(config)# interface pos 2/0/0 Router(config-if)# service-policy output policy1Router(config-if)# exitUse the following commands to verify CBWFQ:
Note
This example shows the information displayed when you enter the show policy-map interface command:
Router1-PE# show policy-map interfacePOS6/2/0service-policy output:queue stats for all priority classes:queue size 0, queue limit 32655packets output 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0class-map:dscp0 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:ip dscp 0queue size 0, queue limit 610packets output 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0shape:cir 2440000, Bc 9760, Be 9760(shape parameter is rounded to 2439000 due to granularity)output bytes 0, shape rate 0 bpsclass-map:dscp1 (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:ip dscp 10 packets, 0 bytes30 second rate 0 bpsqueue size 0, queue limit 100000packets output 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0bandwidth:kbps 400000, weight 64(bandwidth parameter is rounded to 397592 kbps due to granularity)class-map:dscp2 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:ip dscp 2Priority:21% (130620 kbps), burst bytes 3265500, b/w exceed drops:0(Priority parameter is rounded to 129278 kbps due to granularity)class-map:class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:any0 packets, 0 bytes30 second rate 0 bpsqueue size 0, queue limit 11422packets output 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0Configuring CBWFQ for MLPPP Links
Multilink Point-to-Point Protocol (MLPPP) allows multiple T1/E1 links to be bundled together to offer bandwidth greater than multiple T1s/E1s but less than a T3/E3. MLPPP with QoS supports CBWFQ, enabling MLPPP to carry voice and data on the same MLPPP bundle.
For information on configuring CBWFQ on MLPPP links, see the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_c/index.htm
Note
Flow-Based Weighted Fair Queuing (WFQ)
Flow-based weighted fair queuing (WFQ) tries to ensure that reserved flows receive enough bandwidth and bounds latency to meet their minimum needs in the event of congestion. With standard WFQ, packets are queued by flow. Packets with the same source IP address, destination IP address, source Transmission Control Protocol (TCP) or UDP port, destination TCP or UDP port belong to the same flow.
For configuration information, see the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at: /en/US/docs/ios/12_2/qos/configuration/guide/qcfwfq.html#1000917
Configuring Low Latency Queuing
LLQ lets you specify low-latency behavior for a traffic class. LLQ allows delay-sensitive data to be given preferential treatment. You can give one or more classes priority status. You configure LLQ with the priority command.
The priority command configures guaranteed bandwidth to a priority class under worst-case congestion scenarios. It does not limit the bandwidth to the configured rate if the priority class is over subscribed. Typically, you would use the priority command in conjunction with an admission control mechanism that controls the amount of load offered to the priority class to avoid starvation of other classes.
Note
Restrictions and Usage Guidelines
The LLQ restrictions and usage guidelines are as follows:
•
•
•
•
•
On very slow links, giving priority to both voice and control packets may produce degraded voice quality. Therefore, if you are only assigning priority based on port numbers, you should use the ip rtp priority command instead of the priority command. (The ip rtp priority command provides priority only for even port numbers.)
•
The priority command can be configured in multiple classes, but it should only be used for voice-like, constant bit rate (CBR) traffic.
•
•
Configuration Tasks
To configure LLQ, use the Modular QoS command-line interface. Define the class of traffic with the class-map command, create a policy map that contains the priority command, and apply the policy to the appropriate interface with the service-policy command.
To configure the class of traffic, see the "Configuring Classification" section. To configure a policy with LLQ and to assign the policy to an interface, perform the following tasks in global configuration mode:
This example shows how to configure a priority queue reserved for traffic with an IP DSCP value of 40:
Router(config)# class-map gold-dataRouter(config-cmap)# match-any ip dscp 40Router(config-cmap)# exitRouter(config)# class-map match barRouter(config-cmap)# match-any ip dscp 8Router(config-cmap)# exitRouter(config)#In the example, a priority queue for the class gold-data is reserved with a guaranteed allowed bandwidth of 50 Mbps, and a bandwidth of 20 Mbps is configured for the class bar. The service-policy command attaches the policy map to interface pos 4/1.
Router(config)# policy-map policy1Router(config-pmap)# class gold-dataRouter(config-pmap-c)# priority 50000Router(config-pmap)# class barRouter(config-pmap-c)# bandwidth 20000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface pos 4/1/1Router(config-if)# service-policy output policy1Router(config-if)# exitUse the following command to verify LLQ:
Router# show queue interface-type interface-number
Displays queueing configuration and statistics for a particular interface.
Configurable LLQ Burst Size
Configurable LLQ Burst Size extends the functionality available with LLQ. This feature allows customers to specify the Committed Burst (Bc) size in LLQ and, therefore, configure the network to accommodate temporary bursts of traffic.
For information on configuring LLQ burst size, see the Configuring Burst Size in Low Latency Queueing at:
https://www.cisco.com/en/US/docs/ios/12_1t/12_1t3/feature/guide/dtcfgbst.html
Configuring LLQ for MLPPP Links
MLPPP allows multiple T1/E1 links to be bundled together to offer bandwidth greater than multiple T1s/E1s but less than a T3/E3. MLPPP with QoS supports LLQ, enabling MLPPP to carry voice and data on the same MLPPP bundle.
For information on configuring LLQ on MLPPP links, see Configuring Distributed Low Latency Queueing and Other QoS Features in a Traffic Policy, page 3-25.
Note
Distribution of Remaining Bandwidth
You can use MQC to specify how the remaining bandwidth is distributed among the output queues on a Cisco 7600 router interface or subinterface. Remaining bandwidth is the available bandwidth left on an interface or subinterface after all guaranteed traffic is accounted for. The amount of remaining bandwidth available for use is determined by the excess information rate (EIR) configured for the queue.
In MQC, the bandwidth remaining percent command allows you to configure the remaining bandwidth for output queues.
The following example shows how to use the bandwidth remaining percent command to distribute percentages of remaining bandwidth to various traffic classes in a policy map.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# policy-map myPolicyRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining percent 20Router(config-pmap-c)# class prec1Router(config-pmap-c)# bandwidth remaining percent 30Router(config-pmap-c)# class prec2Router(config-pmap-c)# bandwidth remaining percent 10Router(config-pmap-c)# bandwidth percent 50Router(config-pmap-c)# ^ZRouter#20:44:36: %SYS-5-CONFIG_I: Configured from console by consoleRouter# show policy-map myPolicyPolicy Map myPolicyClass prec1bandwidth remaining percent 30Class prec2bandwidth percent 50bandwidth remaining percent 10Class class-defaultbandwidth remaining percent 20Command Reference
To specify how the remaining bandwidth is distributed among the output queues on a Cisco 7600 series router interface or subinterface, use the MQC bandwidth remaining percent command in policy-map class configuration mode. To remove the percentage of remaining bandwidth specified for a traffic class, use the no form of this command.
•
•
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
Modular QoS policy-map class configuration
Command History
Usage Guidelines
Use the MQC bandwidth remaining percent command to specify how the remaining bandwidth is distributed among the output queues on a Cisco 7600 series router interface or subinterface. Remaining bandwidth is the available bandwidth left on an interface or subinterface after all guaranteed traffic is accounted for.
The bandwidth remaining percent command allows you to configure the remaining bandwidth for output queues. The percentage parameter specified with the bandwidth remaining percent command is translated into an internal excess information rate (EIR) value between 0 and 255. The aggregate of all user-configured EIR bandwidth percentages cannot exceed 100 percent.
If the aggregate of all remaining bandwidth is less than 100 percent, the remainder is evenly split among user queues (including the default queue) that do not have a remaining bandwidth percentage configured. The minimum EIR value of each output queue is 1.
The EIR parameter for the network control queue is fixed at 128 and is not configurable.
If you have not configured a committed information rate (CIR) value for the default queue and it is the only user queue, the default queue receives half of the remaining bandwidth percentage of the network control queue.
Congestion Avoidance
Congestion avoidance techniques monitor network traffic loads in an effort to anticipate and avoid congestion at common network bottlenecks. Congestion avoidance is achieved through packet dropping. Among the more commonly used congestion avoidance mechanisms is Random Early Detection (RED), which is optimum for high-speed transit networks. Cisco IOS QoS includes an implementation of RED that, when configured, controls when the router drops packets. If you do not configure Weighted Random Early Detection (WRED), the router uses the cruder default packet drop mechanism called tail drop.
For more information, see the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_c/fqcprt3/qcfconav.htm
The following sections describe congestion avoidance on the FlexWAN and Enhanced FlexWAN modules:
•
Configuring Weighted Random Early Detection
Weighted Random Early Detection (WRED) is a congestion avoidance mechanism that takes advantage of the congestion control mechanism of TCP. By selectively dropping packets based on IP precedence prior to periods of high congestion, WRED tells the packet source to decrease its transmission rate. Edge routers assign IP Precedence to packets as they enter the network. WRED is useful on any output interface where you expect to have congestion. However, WRED is usually used in the core routers of a network rather than at the edge. WRED uses these precedences to determine how it treats different types of traffic.
When a packet arrives, the average queue size is calculated and one of the following events occurs:
•
•
•
Restrictions and Usage Guidelines
The WRED restrictions and usage guidelines are as follows:
•
–
–
•
For more details on the queue calculations and how WRED works, refer to the section "About WRED" in the chapter "Congestion Avoidance Overview" in the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at the following URL:
http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/fqos_c.html
Configuration Tasks
To configure WRED, use the Modular QoS command-line interface.
1.
2.
3.
To configure the class of traffic, see the "Configuring Classification" section.
To configure a policy with WRED and to assign the policy to an interface, perform the following steps in global configuration mode:
Configuration Example
This example shows how to configure WRED:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# policy-map wred_testRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# random-detectRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface pos 7/1/0Router(config-if)# service-policy output wred_testRouter(config-if)# endThis example shows how to verify the configuration:
Router# show policy-map interface pos 7/1/0POS7/1/0Service-policy output: wred_testClass-map: class-default (match-any)16634097 packets, 8217243918 bytes30 second offered rate 482198000 bps, drop rate 0 bpsMatch: anyqueue size 0, queue limit 128packets output 16634097, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0Random-detect:Exp-weight-constant: 3 (1/8)Mean queue depth: 0Class Random Tail Minimum Maximum Mark Outputdrop drop threshold threshold probability packets0 104806 0 32 64 1/10 30268121 104569 0 36 64 1/10 30270502 104732 0 40 64 1/10 30268843 104169 0 44 64 1/10 30274494 103047 0 48 64 1/10 30285695 103156 0 52 64 1/10 30284606 0 0 56 64 1/10 07 0 0 60 64 1/10 0Distributed WRED
Distributed WRED (dWRED) is useful on any output interface where you expect to have congestion. However, dWRED is usually used in the core routers of a network, rather than the edge. Edge routers assign IP precedences to packets as they enter the network. WRED uses these precedences to determine how to treat different types of traffic. For more information, see Distributed Class-Based Weighted Fair Queueing and Distributed Weighted Random Early Detection at:
http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dtcbwred.html
DiffServ-Compliant WRED
DiffServ Compliant WRED extends the functionality of WRED to enable support for DiffServ and Assured Forwarding (AF) Per Hop Behavior (PHB). This feature enables customers to implement AF PHB by coloring packets according to DSCP values and then assigning preferential drop probabilities to those packets.
This feature can be used with IP packets only. It is not intended for use with Multiprotocol Label Switching (MPLS)-encapsulated packets. For configuration information, see Configuring Weighted Random Early Detection at:
Traffic Shaping
A shaper typically delays excess traffic using a buffer, or queueing mechanism, to hold packets and shape the flow when the data rate of the source is higher than expected.
For more information, see the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at:
http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/fqos_c.html
The FlexWAN and Enhanced FlexWAN modules also support Distributed Traffic Shaping (DTS). For more information, see Configuring Distributed Traffic Shaping at: http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/qcfdts.html
The following sections describe shaping on the FlexWAN and Enhanced FlexWAN modules:
•
Configuring Traffic Shaping
Traffic shaping allows us to impose a maximum rate for a particular class of traffic. The rationale for shaping is to smooth out bursty traffic into the network. It is accomplished by buffering. You perform traffic shaping with the shape command. These are the basic forms of the command:
•
•
Restrictions and Usage Guidelines
The traffic shaping restrictions and usage guidelines are as follows:
•
•
•
Configuration Tasks
Use MQC to configure traffic shaping. Create a class-map using the class-map command and a policy map using the policy-map command. Attach the class to the policy using the class command and then use the shape command to configure shaping for that class.
This example shows traffic shaping on a main interface; traffic leaving interface pos1/0/0 is shaped at the rate of 10 Mbps:
Router(config)# class-map class-interface-allRouter(config-cmap)# match anyRouter(config-cmap)# exitRouter(config)# policy-map dts-interface-all-actionRouter(config-pmap)# class class-interface-allRouter(config-pmap-c)# shape average 10000000Router(config-pmap-c)# exitRouter(config)# interface pos1/0/0Router(config-if)# service-policy output dts-interface-all-action
Use the following commands to verify traffic shaping:
Configuring Hierarchical Traffic Shaping
Hierarchical traffic shaping allows multiple classes of traffic to be shaped at a single rate. A hierarchical traffic shaping policy consists of a child policy that identifies one or more classes of traffic, and a parent policy that shapes the output of the traffic classes into a single shape rate. You can apply a nested policy to an interface or subinterface.
Restrictions and Usage Guidelines
The hierarchical traffic shaping restrictions and usage guidelines are as follows:
•
•
Configuration Tasks
To configure hierarchical traffic shaping, use the Modular QoS command-line interface to define the parent and child policies. For the child policy, define the classes of traffic with the class-map command and create a policy with the policy-map command. For the parent policy, create a policy with the policy-map command, apply the child policy to the default class with the service-policy command, and apply the parent policy to the appropriate interface with the service-policy command.
To configure the classes of traffic, see the "Configuring Classification" section. To configure a child and parent policies for hierarchical traffic shaping, perform the following tasks in global configuration mode:
Step 1
Router(config)# policy-map child-policy-name
Specifies the name of the child policy map to configure.
Step 2
Router(config-pmap)# class class-name
Specifies the name of a predefined class included in the service policy.
Step 3
Router(config-pmap-c)# priority bandwidth-kbps | percent % of available bandwidth1
Gives priority to a class of traffic belonging to the policy map.
Step 4
Specifies the name of the traffic class to be associated with the service policy.
Step 5
Router(config-pmap-c)# bandwidth bandwidth-kbps | percent % of available bandwidth2
Specifies the percentage of available bandwidth in kilobits per second to be assigned to packets that meet the match criteria of the associated traffic class.
Step 6
Router(config)# policy-map parent-policy-name
Specifies the name of the parent policy map to configure.
Step 7
Router(config-pmap)# class class-name
Specifies the name of a predefined class included in the service policy.
Step 8
Router(config-pmap-c)# shape average cir
Shapes traffic to the indicated bit rate for the specified class.
Step 9
Router(config-pmap-c)# service-policy child-policy-name
Links the parent and child policy and class.
Step 10
Router(config)# interface interface-name
Specifies the interface to which the policy map will be applied.
Step 11
Router(config-if)# service-policy [output parent-policy-name]
Attaches the specified nested parent and child policies to the interface.
1 Only the parameters shown are supported.
2 Only the parameters shown are supported.
This example shows a nested traffic policy configuration where traffic matching the class called "voice" will be guaranteed 3,200 Kbps, or 10% of the parent_policy's shape average:
Router(config)# class-map match-all voiceRouter(config-cmap)# match ip dscp 5Router(config-cmap)# exitRouter(config)# policy-map child_policyRouter(config-pmap)# class voiceRouter(config-pmap-c)# priority percent 10Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# policy-map parent_policyRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 32000000Router(config-pmap-c)# service-policy child_policyRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface Serial6/1:1.1 point-to-pointRouter(config-subif)# service-policy output parent_policyConfiguring Queue Limit
For the class-based traffic shaping and CBWFQ features, you can specify or modify the maximum number of packets the queue can hold for a class policy configured in a policy map using the queue-limit command from policy-map class configuration mode.
Restrictions and Usage Guidelines
The queue limit restrictions and usage guidelines are as follows:
•
Configuration Tasks
To configure the queue limit, use the Modular QoS command-line interface. Define the class of traffic with the class-map command, create a policy-map that contains the queue-limit command, and apply the policy to the appropriate interface with the service-policy command.
To configure the class of traffic, see the "Configuring Classification" section. To configure a policy with the queue-limit command and assign the policy to an interface, perform the following tasks in global configuration mode:
Layer 2 QoS Applications
This section describes the QoS features for Layer 2 operations. It contains the following sections:
•
•
For information about how to configure QoS for interfaces that support bridging, see the "Configuring QoS on Bridged Interfaces" section.
Configuring QoS for ATM VC Access Trunk Emulation
Ingress and Egress QoS
The ingress QoS features are as follows:
•
•
•
Note
Egress QoS features based on dot1q ID or CoS value of the dot1q header:
•
•
•
Configuration of QoS is shown in the following example:
Router(config)# interface atm3/0/0.100 point-to-pointRouter(config-if)# pvc 1/21Router(config-if-atm-vc)# bridge-domain 200 dot1q 100Router(config-if-atm-vc)# bridge-domain 300 dot1q 101Router(config-if-atm-vc)# service-policy in atm-policy-inRouter(config-if-atm-vc)# service-policy out atm-policy-outAs a result of this configuration of the VC, the match vlan or match cos parameters shown in the following example are the values from the dot1q header for 100 and 101.
Router(config)# class-map match-all match-cos-2Router(config-cmap)# match cos inner 2Router(config)# class-map match-all match-cos-3Router(config-cmap)# match cos inner 3Router(config)# class-map match-all match-vlan-101Router(config-cmap)# match vlan inner 101Router(config)# class-map match-all match-vlan-100Router(config-cmap)# match vlan inner 100!Router(config)# policy-map atm-policy-outRouter(config-pmap)# class match-vlan-100Router(config-pmap)# shape average 64000 256 256Router(config-pmap)# class match-cos-2Router(config-pmap)# priority percent 70!Router(config)# policy-map atm-policy-inRouter(config-pmap)# class match-cos-3Router(config-pmap)# police 128000 4000 4000 conform-action transmit exceed-action drop!Verifying the Configuration
Use the following show commands to verify the configurations or counters:
Router# show class mapClass Map match-any class-default (id 0)Match anyClass Map match-all match-cos-2 (id 1)Match cos inner 2Class Map match-all match-cos-3 (id 2)Match cos inner 3Class Map match-all match-vlan-101 (id 4)Match vlan inner 101Class Map match-all match-vlan-100 (id 5)Match vlan inner 100Router# show policy-mapPolicy Map atm-policy-outClass match-vlan-100shape average 64000 256 256Class match-cos-2priority percent 70Class class-defaultPolicy Map atm-policy-inClass match-cos-3police 128000 4000 conform-action transmit exceed-action dropRouter# show policy-map interfaceATM3/0/0.100: VC 1/21Service-policy input: atm-policy-inClass-map: match-cos-3 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: cos inner 3Queueingqueue size 0, queue limit 5packets input 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0, flow drops 0police:128000 bps, 4470 limitconformed 0 packets, o bytes; action: transmitexceeded 0 packets, 0 bytes; action: dropconformed 0 bps, exceed 0 bpsClass-map: class-default (match-any)51 packets, 6408 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: anyqueue size 0, queue limit 1772packets input, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0, flow drops 0Service-policy output: atm-policy-outqueue stats for all priority classes:queue limit 8272 (packets)(queue depth/total drops/no-buffer drops) 0/0/0(pkts queued/bytes queued) 0/0Class-=map match-vlan-100 (match-all)921 packets, 77748 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: vlan inner 100Queueingqueue limit 5 (packets)(queue depth/total drops/no-buffer drops) 0/0/0(pkts queued/bytes queued) 921/77748 shape (average) cir 64000 bc 256 be 256target shape rate 64000Class-map: match-cos-2 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: cos inner 2Priority: 70 (%) (104832 kbps), burst 2620800 (bytes)Class-map: class-default (match-any)870 packets, 71340 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: anyqueue limit 1772 (packets)(queue depth/total drops/no-buffer drops) 0/0/0(pkts queued/bytes queued) 870/71340Configuring ATM Cell Loss Priority Setting
The ATM Cell Loss Priority (CLP) Setting feature allows users to control the CLP bit setting on routers with the PA-A3 and PA-A6 port adapters.
When creating a class map, the following commands are supported:
•
•
•
•
Configure the CLP setting feature as described at the following URL:
Configuring QoS on Bridged Interfaces
This section describes the QoS features available for interfaces that support bridging and provides information about how to configure QoS on bridged interfaces. It contains the following sections:
•
•
QoS Over Bridging
In Cisco IOS Release 12.2SR and later releases, the Enhanced FlexWAN module supports the QoS over bridging feature, which provides QoS services to bridged packets carrying Ethernet frames. The QoS over bridging feature is available on interfaces that are configured for one of the following encapsulation types:
•
•
•
•
•
•
The QoS over bridging feature allows you to classify bridged Ethernet packets into different traffic classes and perform QoS based on packet classification. This way you can apply different QoS features to different classes of traffic.
QoS over Bridging Features
You can apply the following QoS features to bridged Ethernet packets:
•
–
–
–
–
–
–
–
•
–
–
–
–
–
•
–
•
–
–
–
•
•
•
•
Note
For a list of QoS over bridging classification and marking statements, see Table 5-1 and Table 5-2.
Restrictions and Usage Guidelines
The QoS over bridging feature has the following restrictions and usage guidelines:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Configuring QoS on Bridged Interfaces
To configure a policy map that provides QoS features for bridged packets carrying Ethernet frames, follow these steps. See the "QoS over Bridging Configuration Examples" section for configuration examples.
Note
Step 1
Router(config)# class-map [match-all | match-any]
class-name
Creates a class map that assigns packets to a QoS traffic class.
The match-all option requires that a packet meet all match statements to be assigned to this traffic class. The match-any option allows a match on any statement.
Step 2
Router(config-cmap)# match {vlan inner vlan-value | cos inner cos-value | match ip dscp dscp-value | match ip precedence prec-value | match fr-de | match fr-dlci dlci-value | match atm clp }
Specifies a value to match (see Table 5-1 for details). Specify one or more match statements to define the characteristics of traffic to assign to this traffic class. Enter the exit command when you are done.
Step 3
Router(config)# policy-map policy-name
Creates a policy map that defines the QoS actions to apply to the traffic classes in this policy map.
Step 4
Router(config-pmap)# class class-name
Specifies the name of a traffic class to perform QoS on. The traffic class must already exist (Step 1).
Step 5
Specify one or more QoS actions (such as marking, policing, and queuing) to perform on packets in this traffic class, and enter the exit command when you are done. Repeat Steps 4 through 7 for other traffic classes that are part of this policy. When you are done, enter the exit command twice to return to configuration mode.
Note
Step 6
Router(config-pmap-c)# set {cos-inner cos-value | set fr-de | set atm clp}
Marks the CoS bits, Frame Relay discard eligibility (FR-DE) bit, or ATM cell loss priority (CLP) bit of packets in this traffic class (see Table 5-2 for details).
You can also use the set-cos-inner-transmit option in a police statement.
Step 7
Configures traffic policing, which sets the traffic rate for a traffic class and specifies whether to drop, transmit, or transmit with re-marking packets that conform, exceed, or violate the specified traffic rate. This command syntax is for two-rate policing, with committed and peak information rates (CIR, PIR).
In addition to the standard options for action, the following option is available for bridged packets:
•
Step 8
Router(config)# interface interface-name
Specifies the interface to attach the policy map to. The interface must be configured to support bridging.
Step 9
Router(config-if)# service-policy {input | output} policy-name
Attaches the specified policy map (policy-name) to the interface, and specifies whether to apply the QoS policy to ingress or egress packets on the interface.
QoS over Bridging Class-Map and Policy-Map Statements
Table 5-1 and Table 5-2 list the class-map and policy-map statements for QoS over bridging features. The tables list the types of interfaces that support each statement; the terms ingress and egress refer to whether the statement applies to incoming (ingress) or outgoing (egress) packets on the interface. See the "QoS over Bridging Configuration Examples" section for configuration examples.
Table 5-2 lists the marking statements available for QoS on bridged packets.
Table 5-3 lists the other QoS features that are available for bridged packets. Examples of most of these features are provided in the "QoS over Bridging Configuration Examples" section.
Table 5-3 Additional QoS Features for Bridged Packets (Policy Map)
Traffic shaping
(shape command)
Allows you to control the speed of traffic entering or leaving an interface. Shaping can be used to match traffic flow to interface speed and to ensure that service agreements are adhered to. It can also help control traffic bottlenecks. See the "Traffic Shaping" section for more information.
Interfaces (ingress and egress): ATM, Frame Relay,
PPP/BCP (single-VLAN, trunk), BRE, RBE, Half-bridgingTraffic policing
(police command)
Allows you to control the speed of traffic entering or leaving an interface, and to specify whether to drop or transmit packets that conform, exceed, or violate the specified traffic rate. In addition, policing allows you to change the precedence of packets before transmitting them. See the "Configuring Policing" section for more information.
Interfaces (ingress and egress): ATM, Frame Relay, PPP/BCP (single-VLAN, trunk), BRE, RBE, Half-bridging
Low latency queuing
(priority command)
LLQ provides strict priority queuing on ATM VCs and serial interfaces. See the "Configuring Low Latency Queuing" section for more information.
Interfaces (egress): ATM, Frame Relay, PPP/BCP (single-VLAN, trunk), BRE, RBE, Half-bridging
Class-based weighted fair queuing
(bandwidth command)
CBWFQ allows you to allocate the bandwidth on an interface among several classes of traffic. Traffic is then assigned bandwidth based on the traffic class it belongs to. See the "Configuring Class-Based Weighted Fair Queuing" section for more information.
Interfaces (egress): ATM, Frame Relay, PPP/BCP (single-VLAN, trunk), BRE, RBE, Half-bridging
Hierarchical QoS (HQoS)
Allows you to configure a policy map (parent) that contains other policy maps (children).
Interfaces (ingress and egress): ATM, Frame Relay, PPP/BCP (single-VLAN, trunk), BRE, RBE, Half-bridging
Sample Interface Configurations
Following are several sample configurations for the types of interfaces that support the QoS over bridging feature:
ATM (RFC 1483) Interface:
interface atm3/0/0pvc 10/100bridge-domain 100 dot1qRouting Bridged Encapsulation (RBE) Interface:
interface atm3/0/0.2 pointip address 20.0.0.2 255.255.0.0atm route-bridge ippvc 10/100Bridged Routing Encapsulation (BRE) Interface:
interface atm3/0/0.1 point-to-pointpvc 0/40bre-connect 40Half-bridging Interface:
interface atm3/0/0.2 pointip address 20.0.0.2 255.255.0.0pvc 10/100encapsulation aal5snap bridgeFrame Relay (RFC 1490) Interface:
interface POS1/0/0encapsulation frame-relay ietfframe-relay interface-dlci 100bridge-domain 100BCP/PPP (RFC 3518) Interface (Single-VLAN Mode):
interface POS1/0/0encapsulation pppbridge-domain 200 dot1qBCP/PPP (RFC 3518) Interface (Trunk Mode):
interface POS5/0/0switchportswitchport trunk allowed vlan allswitchport mode trunkswitchport nonegotiateno ip addressencapsulation pppclock source internalBCP/PPP (RFC 3518) Interface (Tunnel Mode):
interface POS5/0/0no ip addressencapsulation pppbridge-domain 100 dot1q-tunnelclock source internalQoS over Bridging Configuration Examples
The following sections provide several examples of how to configure QoS on interfaces that support bridging. The following types of configuration examples are included:
•
•
•
•
Traffic Classification
The following several examples show how to filter (classify) traffic based on the VLAN ID or CoS bits in the Ethernet header, the Frame Relay DLCI (FR-DLCI) or discard eligibility (FR-DE) bit, and IP precedence or IP DSCP value.
The following class maps classify traffic based on the VLAN ID in the Ethernet (inner) header:
Router(config)# class-map match-all vlan100Router(config-cmap)# match vlan inner 100Router(config-cmap)# exit Router(config)# class-map match-all vlan101Router(config-cmap)# match vlan inner 101Router(config-cmap)# exitThe following class map creates a traffic class that matches all packets whose CoS bits are equal to 7:
Router(config)# class-map match-all cos7Router(config-cmap)# match cos inner 7Router(config-cmap)# exitThe following class maps match Frame Relay traffic with a DLCI of 100 or 101:
Router(config)# class-map match-all dlci100Router(config-cmap)# match fr-dlci 100Router(config-cmap)# exit Router(config)# class-map match-all dlci101Router(config-cmap)# match fr-dlci 101Router(config-cmap)# exitThe following class maps classify traffic based on the IP precedence or IP DSCP value:
Router(config)# class-map match-any prec2Router(config-cmap)# match ip prec 2Router(config-cmap)# exitRouter(config)# class-map match-any dscp10Router(config-cmap)# match ip dscp 10Router(config-cmap)# exitThe following class maps classify traffic based on whether the packets are marked for discard during congestion. The first example matches Frame Relay packets whose discard eligibility (FR-DE) bit is set, and the second matches ATM packets whose cell loss priority (ATM-CLP) bit is set:
Router(config)# class-map match-all FRdiscardRouter(config-cmap)# match fr-deRouter(config-cmap)# exitRouter(config)# class-map match-all ATMdiscardRouter(config-cmap)# match atm clpRouter(config-cmap)# exitShaping Traffic
The next two examples show how to classify and shape traffic based on VLAN ID and Frame Relay DLCI.
This example creates class maps to filter VLAN 100 and VLAN 101 traffic into separate traffic classes and a policy map that shapes the traffic on the VLANs. The policy map is then attached to an ATM PVC.
Router(config)# class-map match-all vlan100Router(config-cmap)# match vlan inner 100Router(config-cmap)# exit Router(config)# class-map match-all vlan101Router(config-cmap)# match vlan inner 101Router(config-cmap)# exitRouter(config)# policy-map match-vlanRouter(config-pmap)# class vlan100Router(config-pmap-c)# shape average 1000000 8000 8000Router(config-pmap)# class vlan101Router(config-pmap-c)# shape average 1000000 8000 8000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface ATM3/0/0Router(config-if)# pvc 10/100Router(config-if)# bridge-domain 100 dot1qRouter(config-if)# service-policy output match-vlanRouter(config-if)# service-policy input match-vlanRouter(config-if)# exitThe following commands create class maps and a policy map to classify and shape Frame Relay traffic on POS interface 1/0/0. This example is similar to the one above.
Router(config)# class-map match-all DLCI00Router(config-cmap)# match fr-dlci 100Router(config-cmap)# exitRouter(config)# policy-map DLCIRouter(config-pmap)# class DLCI100Router(config-pmap-c)# shape average 1000000 8000 8000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface POS1/0/0Router(config-if)# encapsulation frame-relay ietfRouter(config-if)# frame-relay interface-dlci 100Router(config-if)# bridge-domain 100Router(config-if)# service policy output DLCIRouter(config-if)# exitMarking Traffic
The following example matches Frame Relay traffic with a DLCI of 100 and sets the discard eligibility bit (FR-DE) of those packets:
Router(config)# class-map match-all DLCI100Router(config-cmap)# match fr-dlci 100Router(config-cmap)# exit Router(config)# policy-map FR-DERouter(config-pmap)# class-map DLCI100Router(config-pmap-c)# set fr-deRouter(config-pmap-c)# exitRouter(config-pmap)# exitThe following examples set the ATM CLP bit of packets that have a CoS or IP precedence value of 2. The class maps match traffic based on the value of the CoS or IP precedence bits in the Ethernet header within the packet.
Router(config)# class-map match-all COS2Router(config-cmap)# match cos inner 2Router(config-cmap)# exit Router(config)# policy-map ATM-CLP-COSRouter(config-pmap)# class-map COS2Router(config-pmap-c)# set atm-clpRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# class-map match-all IP-PREC2Router(config-cmap)# match ip prec 2Router(config)# policy-map ATM-CLP-IPRouter(config-pmap)# class-map IP-PREC2Router(config-pmap-c)# set atm-clpRouter(config-pmap-c)# exitRouter(config-pmap)# exitThe following commands filter traffic from VLANs 100 and 101 and set the CoS bits of those packets. VLAN 100 traffic is assigned a CoS value of 3 and VLAN 101 traffic is assigned a CoS value of 7 (highest priority):
Router(config)# class-map match-all vlan100Router(config-cmap)# match vlan inner 100Router(config-cmap)# exit Router(config)# class-map match-all vlan101Router(config-cmap)# match vlan inner 101Router(config-cmap)# exitRouter(config)# policy-map set-cosRouter(config-pmap)# class vlan100Router(config-pmap-c)# set cos-inner 3Router(config-pmap)# class vlan101Router(config-pmap-c)# set cos-inner 7Router(config-pmap-c)# exitRouter(config-pmap)# exitThe following commands perform policing on traffic in VLAN 101. The police command (two-rate) sets the traffic rate for VLAN 101 traffic as follows: the committed information rate is 1 Mbps and the peak information rate is 2 Mbps. In addition, the command sets the CoS bits to 6 for traffic that conforms to the specified rate. In this example, the policy is attached to a PVC on ATM interface 3/0/0, but it could be applied to other types of interfaces.
Router(config)# class-map match-all vlan101Router(config-cmap)# match vlan inner 101Router(config-cmap)# exitRouter(config)# policy-map police101Router(config-pmap)# class vlan101Router(config-pmap-c)# police cir 1000000 bc 31250 pir 2000000 be 31250 conform-action set-cos-inner-transmit 6 exceed-action dropRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface atm3/0/0Router(config-if)# pvc 10/100Router(config-if)# bridge-domain 101 dot1qRouter(config-if)# service-policy input police101Router(config-if)# service-policy output police101Hierarchical QoS
The following configuration example shows a hierarchical QoS policy that filters traffic from different VLANs (100, 200, 300) into different traffic classes and then allocates bandwidth to the traffic based on CoS values. This example uses child policies within a parent policy (hierarchical QoS).
1.
Router(config)# class-map match-all vlan100Router(config-cmap)# match vlan inner 100Router(config-cmap)# exit Router(config)# class-map match-all vlan200Router(config-cmap)# match vlan inner 200Router(config-cmap)# exit Router(config)# class-map match-all vlan300Router(config-cmap)# match vlan inner 300Router(config-cmap)# exit2.
Router(config)# class-map match-all cos0Router(config-cmap)# match cos inner 0Router(config-cmap)# exit Router(config)# class-map match-all cos2Router(config-cmap)# match cos inner 2Router(config-cmap)# exit Router(config)# class-map match-all cos4Router(config-cmap)# match cos inner 4Router(config-cmap)# exit Router(config)# class-map match-all cos7Router(config-cmap)# match cos inner 7Router(config-cmap)# exit3.
Router(config)# policy-map vlan100Router(config-pmap)# class cos2Router(config-pmap-c)# bandwidth percent 10Router(config-pmap)# class cos4Router(config-pmap-c)# bandwidth percent 20Router(config-pmap)# class cos7Router(config-pmap-c)# priority percent 30Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# policy-map vlan200Router(config-pmap)# class cos2Router(config-pmap-c)# bandwidth percent 10Router(config-pmap)# class cos4Router(config-pmap-c)# bandwidth percent 20Router(config-pmap)# class cos7Router(config-pmap-c)# priority percent 30Router(config-pmap-c)# exitRouter(config-pmap)# exit4.
Router(config)# policy-map egress_mpbRouter(config-pmap)# class vlan100Router(config-pmap-c)# bandwidth percent 30Router(config-pmap-c)# service-policy vlan100Router(config-pmap-c)# exitRouter(config-pmap)# class vlan200Router(config-pmap-c)# bandwidth percent 40Router(config-pmap-c)# service-policy vlan200Router(config-pmap-c)# exit5.
Router(config)# policy-map ingress_mpbRouter(config-pmap)# class vlan100Router(config-pmap-c)# set cos-inner 5Router(config-pmap-c)# exitRouter(config-pmap)# class vlan200Router(config-pmap-c)# set cos-inner 3Router(config-pmap-c)# exitRouter(config-pmap)# exit6.
Router(config)# policy-map atm-clpRouter(config-pmap)# class cos2Router(config-pmap-c)# set atm-clpRouter(config-pmap-c)# exit7.
Router(config)# interface POS3/0/0Router(config-if)# switchportRouter(config-if)# switchport trunk allowed vlan 100,200,300Router(config-if)# service-policy output egress_mpbRouter(config-if)# service-policy input ingress_mpbRouter(config-if)# encapsulation pppRouter(config-if)# shutdownRouter(config-if)# no shutdownRouter(config-if)# exit8.
Router(config)# interface ATM4/1/0Router(config-if)# pvc 15/100Router(config-if)# bridge-domain 100 dot1qRouter(config-if)# service-policy output atm-clpRouter(config-if)# exitRouter(config)# exitUnderstanding MPLS QoS
MPLS QoS allows a network administrator to provide differentiated levels of service across an MPLS network. Network administrators can satisfy a wide range of networking requirements by specifying the class of service applicable to each transmitted frame or packet. Different classes of service can be established for frames and packets by setting EXP bits in the attached MPLS label.
Note
http://www.cisco.com/en/US/products/sw/iosswrel/ps5014/products_feature_guide_chapter09186a008008813a.html
FlexWAN and Enhanced FlexWAN MPLS QoS Feature Summary
The following paragraphs provide a summary of MPLS QoS features for the FlexWAN and Enhanced FlexWAN modules.
Trust
Trust is a port assignment instructing the port whether to trust (leave) existing priorities as is on incoming frames or to rewrite the priority back to zero. Ports on the FlexWAN or Enhanced FlexWAN modules have a default trust state of IP precedence that cannot be changed. The FlexWAN or Enhanced FlexWAN module defaults to accepting the IP precedence or DSCP value contained in the received packets. If you want to mark these values, you can configure a distributed class-based packet marking policy that is applied to ingress traffic while the traffic is still on the FlexWAN or Enhanced FlexWAN module.
Note
Classification
Classification is the process of generating a distinct path for a packet by associating it with a QoS label. For received MPLS packets, the FlexWAN or Enhanced FlexWAN modules match on the EXP in the received topmost label using the match mpls experimental command. The QoS label that is generated identifies all future QoS actions to be performed on this packet.
Note
Marking and Policing
Policing decides whether a packet is in or out of profile by comparing the rate of the inbound traffic to the configured policer. The policer limits the bandwidth consumed by a flow of traffic. The result is passed to the marker.
Marking evaluates the policer configuration information for the action to take when a packet is out of profile. Marking actions are to pass through a packet without modification, to mark down the QoS label in the packet, or to drop the packet.
The FlexWAN or Enhanced FlexWAN modules perform MPLS marking and policing; interfaces are trusted by default.
Note
Preserving IP ToS
The FlexWAN or Enhanced FlexWAN module automatically preserves the IP ToS during all MPLS operations including imposition, swapping, and disposition. You do not need to configure a command to do this.
Using MPLS QoS with FlexWAN and Enhanced FlexWAN Modules
This section describes how to use FlexWAN and Enhanced FlexWAN MPLS QoS for the following:
•
•
Note
IP to MPLS Edge (Ingress Interface) QoS Features
This section describes the MPLS QoS features supported at the ingress to the MPLS network.
Note
Ingress Port Features
Classification based on the packet length is only supported for IPv4 and IPv6 packets.
EXP Marking Support
With the Cisco Supervisor Engine 2 (Sup2), EXP marking is supported for basic MPLS and MPLS/VPN. For MPLS VPN, there is EXP, IP Precedence, and DSCP marking based on IP information (IP Precedence, DSCP, ACL) for imposed (pushed) label only.
With the Sup720, Sup32, or RSP720, for MPLS and MPLS VPN, EXP marking is supported based on IP information (IP Precedence, DSCP, ACL) for imposed (pushed) label only.
Note
Egress Port Features
The FlexWAN and Enhanced FlexWAN module port features classify using the match mpls experimental command. The match mpls experimental command does not match on the EXP in the topmost label.
The Supervisor Engine 2 supports EXP marking at the output QoS policy based on the EXP value for all labels in the label stacks.
The Sup720, Sup32, and RSP720 support EXP marking at the output QoS policy based on EXP value for all labels in the label stacks.
MPLS to IP Edge (Egress Interface) QoS Features
This section describes the MPLS QoS features are supported at the egress interface to the MPLS network.
Ingress Port Features
The FlexWAN and Enhanced FlexWAN module port features classify using the match mpls experimental command. The match mpls experimental command matches on the EXP in the received topmost label.
EXP matching is supported.
Egress Port Features
The FlexWAN and Enhanced FlexWAN module port features classify on information in the transmitted IP header.
EXP matching is supported.
MPLS Core QoS Features
This section describes the MPLS QoS features are supported at the MPLS to MPLS core.
Ingress Port Features
The FlexWAN and Enhanced FlexWAN module port features classify using the match mpls experimental command. The match mpls experimental command matches on the EXP in the received topmost label.
EXP marking is supported at the input QoS policy based on EXP bits.
Egress Port Features
The FlexWAN and Enhanced FlexWAN module port features classify using the match mpls experimental command.
EXP marking is supported.
Configuring MPLS QoS
Note
QoS is configured through the Modular QoS command-line interface (class maps and policy maps). QoS functionality is distributed and performed on the FlexWAN and Enhanced FlexWAN modules.
These sections provide configuration information for MPLS QoS:
•
•
•
•
•
FlexWAN MPLS QoS
Cisco 7600 Supervisor Engines and the Route Switch Processor 720 provide MPLS QoS capabilities; however, the FlexWAN and Enhanced FlexWAN modules do not use them. All MPLS QoS features are distributed by the FlexWAN and Enhanced FlexWAN modules. In this respect, FlexWAN QoS behavior is similar to that of the Cisco 7500 VIP QoS. The FlexWAN and Enhanced FlexWAN modules perform all input and output QoS while the Supervisor Engine or RSP720 performs MPLS switching.
Note
The FlexWAN and Enhanced FlexWAN modules provide the following:
•
•
•
FlexWAN MPLS QoS with Supervisor Engine 2
With the Supervisor Engine 2, the FlexWAN and Enhanced FlexWAN modules perform the label lookup and label operations. With the Supervisor Engine 2, the FlexWAN and Enhanced FlexWAN modules provide the following:
•
•
•
Supported FlexWAN MPLS QoS Features
The FlexWAN and Enhanced FlexWAN modules support the following MPLS QoS features:
•
•
The following additional QoS features are supported in MPLS QoS in the same manner as in IP QoS:
•
•
•
•
•
•
Understanding the MPLS Experimental Field
Setting the MPLS experimental field value satisfies the requirement of service providers that do not want the value of the IP precedence field modified within IP packets transported through their networks.
By choosing different values for the MPLS experimental field, you can mark packets so that packets have the priority that they require during periods of congestion.
By default, the IP precedence value is copied into the MPLS experimental field during imposition.You can mark the MPLS EXP bits with a policy.
Figure 5-1 shows a service provider MPLS network connecting two sites of a customer network.
Figure 5-1 MPLS Network Connecting Two Sites of a Customer's IP Network
Setting the MPLS Experimental Field
Use the set mpls experimental command on the input interface to set the pushed label entry's value during label imposition.
By default, the label edge router copies the IP Precedence of the IP packet to the MPLS EXP field in all pushed label entries.
You can optionally map the IP Precedence or DSCP field to the MPLS EXP field in the MPLS header by using the set mpls experimental command.
Configuring Class-Based Marking for MPLS
To configure Class-based Marking for MPLS, perform the tasks described in the following sections:
•
•
Note
Configuring a Class Map to Classify MPLS Packets
To configure a class map, perform this task beginning in global configuration mode:
This example shows that all packets that contain MPLS experimental value 3 match any with the class name exp-class:
Router(config)# class-map match-any exp-class Router(config-cmap)# match mpls experimental 3 Router(config-cmap)# exitConfiguring a Policy Map to Set the MPLS Experimental Field
To configure a policy map, perform this task beginning in global configuration mode:
Step 1
Creates a policy map that can be attached to one or more interfaces to specify a service policy.
Step 2
Specifies the name of the class map previously designated in the class-map command.
Step 3
Designates the value to which the MPLS bits are set if the packets match the specified policy map.
Step 4
Exits policy-map configuration mode.
1 You can also configure additional supported features, such as shaping.
This example shows that the value in the MPLS experimental field of each packet that is matched by the policy-map MARKING is set to 5:
Router(config)# policy-map MARKING Router(config-pmap)# class exp-class Router(config-pmap-c)# set mpls experimental 5 Router(config-pmap-c)# exitRouter(config-pmap)# exitAttaching the Service Policy
To attach the service policy to an interface, perform the following steps from global configuration mode:
This example shows that the service policy set_experimental_5 is applied to outgoing traffic on the POS interface POS6/0/0:
Router(config)# policy-map MARKING Router(config-pmap)# class exp-class Router(config-pmap-c)# set mpls experimental 5 Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface POS6/0/0 Router(config-if)# service-policy output set_experimental_5 Router(config-if)# exitVerifying QoS Operation
To verify the operation of MPLS QoS, perform this task:
Router# show policy-map interface [interface-name]
Displays detailed information about QoS.
Configuration Examples
Sample configurations provided in this section can be applied to FlexWAN and Enhanced FlexWAN modules supported on the Cisco 7600 series routers.
Ingress PE Router Configuration
In the following example, IP packets with IP precedence 1 entering an MPLS network are shaped to 2,000,000 bits per second and set to MPLS experimental field 3.
Step 1
Router(config)# class-map exp1Router(config-cmap)# match mpls experimental 1Router(config-cmap)# exit
Note
Step 2
Router(config)# policy-map gold1Router(config-pmap)# class exp 1Router(config-pmap-c)# shape average 2000000Router(config-pmap-c)# set mpls experimental 3Router(config-pmap-c)# exitStep 3
Router(config)# interface POS6/1/0Router(config-if)# ip address 153.61.0.2 255.255.0.0Router(config-if)# tag-switching ipRouter(config-if)# service-policy output gold1Router(config-if)# exit
Core Router Ingress and Egress Interface Configuration
The following example provides ingress and egress interface configurations at the P router:
Step 1
Router(config)# interface pos 5/0/0Router(config-if)# ip address 153.61.0.1 255.255.0.0Router(config-if)# tag-switching ipRouter(config-if)# service-policy input gold1Step 2
Router(config)# interface pos 5/0/3Router(config-if)# ip address 153.62.0.1 255.255.0.0Router(config-if)# tag-switching ipRouter(config-if)# service-policy input gold1
Configuring MPLS VPN QoS
Note
The FlexWAN and Enhanced FlexWAN modules support the following MPLS VPN QoS features:
•
•
•
In addition to these features, with a Supervisor Engine 2, MPLS VPN also supports the set ip precedence command on the input WAN interfaces on the FlexWAN and Enhanced FlexWAN modules.
The following restrictions apply to the support for MPLS VPN QoS on the FlexWAN and Enhanced FlexWAN modules:
•
•
•
Configuration Example
The following example shows how to configure QoS on an MPLS VPN:
Router# configure terminalRouter(config)# class-map match-any vpn-classRouter(config-cmap)# match ip precedence 3Router(config-cmap)# exitRouter(config)# policy-map VPN-MARKINGRouter(config-pmap)# class vpn-classRouter(config-pmap-c)# set ip precedence 5Router(config-pmap-c)# set mpls exp 5Router(config-pmap-c)# ^ZRouter# configure terminalRouter(config)# interface POS 6/0/0Router(config-if)# service-policy output VPN-MARKINGRouter(config-if)# ^ZRouter# show running-config interface p6/0/0Building configuration...Current configuration: 175 bytes!interface POS 6/0/0ip vrf forwarding TESTip address 194.3.1.3 255.255.255.0negotiation autoservice-policy input VPN-MARKINGmls qos trust dscpendRouter#
Configuring QoS with Any Transport over MPLS
The following QoS features are supported on Any Transport over MPLS:
•
Note
•
•
•
This section explains how to configure QoS with AToM and includes the following procedures:
•
Note
How to Set Experimental Bits with AToM
For configuration steps and examples, see the "How to Set Experimental Bits with AToM" section.
MPLS AToM uses the three experimental bits in a label to determine the queue of packets. You statically set the experimental bits in both the VC label and the LSP tunnel label, because the LSP tunnel label might be removed at the penultimate router. The following sections explain the transport-specific implementations of the EXP bits.
Ethernet over MPLS and EXP Bits
Note
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/software/122sx/swcg/qos.htmFlexWAN-based EoMPLS supports the following QoS implementations:
•
•
You apply a VLAN interface policy to an individual VLAN. You may configure a unique policy for each individual VLAN. Within a policy, you can classify on 802.1q P bits to set the MPLS experimental bits. You can also implement a single traffic shaper that applies to all traffic within the VLAN.
You apply a core-facing interface policy to the EoMPLS uplink interface. This policy applies to traffic from all VLANs. It does not distinguish between different VLANs. Within a policy, you can classify on MPLS experimental bits and configure the following features:
•
•
•
•
Note
For more information on the commands used to enable Quality of Service, see the following documents:
•
•
Setting the Priority of Packets with the Experimental Bits
Ethernet over MPLS provides Quality of Service (QoS) using the three experimental bits in a label to determine the priority of packets. To support QoS between LERs, set the experimental bits in both the VC and tunnel labels. If you do not assign values to the experimental bits, the priority bits in the 802.1q header's "tag control information" field and are written into the experimental bit fields.
Perform the following steps to set the experimental bits:
Note
Note
Enabling Traffic Shaping
Traffic shaping limits the rate of transmission of data. Average rate shaping limits the transmission rate to the committed information rate (CIR). To add traffic shaping, issue the following commands:
Step 1
Router(config)# class-map class-nameSpecifies the user-defined name of the traffic class.
Step 2
Specifies that all packets will be matched. (Using the class-default in the policy-map would have the same effect.)
Step 3
Router(config-cmap)# policy-map policy-nameSpecifies the name of the traffic policy to configure.
Step 4
Router(config-pmap)# class class-nameSpecifies the name of a predefined traffic class, which was configured with the class-map command, used to classify traffic to the traffic policy.
Step 5
Shapes traffic according to the bit rate you specify.
Step 6
Router(config)# interface vlan vlan-numberEnters the VLAN interface.
Step 7
Assigns a traffic policy to an interface.
1 Only supported parameters are shown.
The shape average rate is rounded to the nearest multiple of the link rate divided by 255. If the shape value is lower than the link rate divided by 255, it is rounded up to link rate divided by 255.
This example shows how the shape value is rounded:
Router# show pol p2Policy Map p2class any-pktshape average 2000000 8000 8000Router# show pol intVlan101service-policy input:p2class-map:any-pkt (match-all)2018169 packets, 4575195376 bytes30 second offered rate 295768000 bps, drop rate 0 bpsmatch:anyqueue size 0, queue limit 0packets input 40492, packet drops 1977677tail/random drops 0, no buffer drops 0, other drops 1977677shape:cir 2000000, Bc 8000, Be 8000input bytes 40847436, shape rate 1874000 bpsclass-map:class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:any0 packets, 0 bytes30 second rate 0 bpsDisplaying the Traffic Policy Assigned to an Interface
To display the traffic policy attached to an interface, issue the following command:
Router# show policy-map vlan50service-policy input: badgerclass-map: blue (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch: anyqueue size 0, queue limit 2packets input 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0shape: cir 2000000, Bc 8000, Be 8000output bytes 0, shape rate 0 bpsclass-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch: any0 packets, 0 bytes30 second rate 0 bps
ATM AAL5 over MPLS and EXP Bits
•
•
ATM Cell Relay over MPLS and EXP Bits
•
•
Frame Relay over MPLS and EXP Bits
Frame Relay over MPLS provides QoS using the three experimental bits in a label to determine the priority of PDUs. If you do not assign values to the experimental bits, the priority bits in the header's tag control information field are set to zero. For Frame Relay over MPLS, you must set the experimental bits on a per-DLCI basis.
Setting the Priority of Packets with EXP Bits
Set the experimental bits in both the VC label and the LSP tunnel label. You set the experimental bits in the VC label, because the LSP tunnel label might be removed at the penultimate router.
Perform the following steps to set the experimental bits.
Enabling Traffic Shaping
Traffic shaping limits the rate of transmission of data. Average rate shaping limits the transmission rate to the committed information rate (CIR). To add traffic shaping, issue the following commands:
Note
Note
Displaying the Traffic Policy Assigned to an Interface
To display the traffic policy attached to an interface, use the show policy-map interface command.
EoMPLS QoS Example
If the egress MPLS tunnel is carried on a FlexWAN interface configured for fair queuing, the shape value is rounded to the nearest multiple of the link rate divided by 255. If the shape value is lower than the link rate divided by 255, it is rounded up to link rate divided by 255.
This example shows how the shape value is rounded:
Router# show pol p2Policy Map p2class any-pktshape average 2000000 8000 8000Router# show pol intVlan101service-policy input:p2class-map:any-pkt (match-all)2018169 packets, 4575195376 bytes30 second offered rate 295768000 bps, drop rate 0 bpsmatch:anyqueue size 0, queue limit 0packets input 40492, packet drops 1977677tail/random drops 0, no buffer drops 0, other drops 1977677shape:cir 2000000, Bc 8000, Be 8000(shape parameter is rounded to 2439000 due to granularity)input bytes 40847436, shape rate 1874000 bpsclass-map:class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:any0 packets, 0 bytes30 second rate 0 bpsEoMPLS QoS Example—Displaying the Traffic Policy Assigned to an Interface
To display the traffic policy attached to an interface, issue the following command:
Router# show policy-map vlan50service-policy input: badgerclass-map: blue (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch: anyqueue size 0, queue limit 2packets input 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0shape: cir 2000000, Bc 8000, Be 8000output bytes 0, shape rate 0 bpsclass-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch: any0 packets, 0 bytes30 second rate 0 bpsEthernet over MPLS QoS Example—Configuring QoS on VLAN
The following example show how to configure QoS on the VLAN.
class-map bluematch cos 1 2 3!policy-map badgerclass blueset mpls experimental 1class class-defaultshape average 2000000 8000 8000!interface vlan50no ip addressno ip mroute-cacheload-interval 30mpls l2transport route 192.168.255.255 50service-policy input badgerno cdp enableATM over MPLS QoS Example—Configuring Ingress QoS
This example shows ingress QoS. On this side the policy attaches to a multipoint l2transport PVC. In this configuration the EXP bits are set to 5 for all packets on PVC 1/101.
class-map match-any anyclassmatch any!policy-map set-policyclass anyclassset mpls experimental 5interface ATM6/0/0no ip addresslogging event link-statusatm clock INTERNALpvc 1/101 l2transportencapsulation aal5mpls l2transport route 10.10.10.10 101service-policy input set-policyFor input shaping, the config is same as above but the action in the policy-map should be changed to shape.
policy-map shape-policyclass anyclassshape average 16000 3200 3200For output shaping based on MPLS EXP, the policy is configured on the main interface.class-map match-any exp2match mpls experimental 2!policy-map shape-policyclass exp2shape average 16000 32 32interface POS4/0/1ip address 20.1.1.1 255.255.255.0service-policy output shape-policyno ip mroute-cacheload-interval 30no keepalivempls label protocol ldptag-switching ipmls qos trust dscpclock source internalno cdp enableFrame Relay over MPLS QoS Example—Configuring Ingress QoS
On the ingress side, you attach the policy to a switched frame-relay DLCI. The configuration below matches frame relay packets with DLCI 10 and sets the EXP bits to 5 during label imposition for the matched packets.
class-map match-any anyclassmatch any!!policy-map set-policyclass anyclassset mpls experimental 5map-class frame-relay dlci101service-policy input set-policyinterface POS1/0/1no ip addressencapsulation frame-relay IETFno ip mroute-cacheload-interval 30no keepalivemls qos trust dscpclock source internalframe-relay interface-dlci 101 switchedclass dlci101For input shaping, the configuration is same as above but the action in the policy-map is changed to shape as follows:
policy-map shape-policyclass anyclassshape average 1600000 6400 6400For output shaping based on MPLS EXP, the policy is configured on the main interface.
class-map match-any exp2match mpls experimental 2!policy-map shape-policyclass exp2shape average 1600000 6400 6400interface POS4/0/1ip address 20.1.1.1 255.255.255.0service-policy output shape-policyno ip mroute-cacheload-interval 30no keepalivempls label protocol ldptag-switching ipmls qos trust dscpclock source internalno cdp enableFor WRED based on MPLS EXP, configure the policy on the main interface.
class-map match-any exp2match mpls experimental 2!policy-map wred-polclass exp2bandwidth percent 20random-detectinterface POS4/0/1service-policy output wred-polDE/CLP and EXP Mapping on Frame Relay and ATM over MPLS VC
The DE/CLP and EXP Mapping on Frame Relay/ATM over MPLS VC feature allows you to map the Frame Relay Discard Eligibility (DE) bit or the ATM Congestion Loss Priority (CLP) bit to the MPLS EXP value at the ingress interface to an MPLS AToM network and to map the MPLS EXP value to the FR-DE or ATM CLP bit at the egress interface of an MPLS AToM network.
The DE bit indicates that a frame has lower importance than other frames. Similarly, the ATM CLP bit indicates whether the cell may be discarded if it encounters extreme congestion as it moves through the network.
In Figure 5-2, the PE1 tags the incoming packet with the MPLS EXP value and sends the packet to the next hop. At each hop, matching is done on the EXP value. At the PE2 egress interface, however, the packet is no longer MPLS but IP, so matching cannot occur on the EXP value.
Internally, the FlexWAN or Enhanced FlexWAN module preserves the EXP value in the QoS_group so matching on the QoS_group at the PE2 egress interface provides the same effect as matching on the EXP value.
Figure 5-2 DE/CLP and EXP Mapping
Match on ATM CLP Bit
Use Match on ATM CLP Bit at the ingress to an MPLS AToM network to map the ATM cell loss priority (CLP) of the packet arriving at an interface to the EXP value, and then apply the desired QoS functionality and actions (for example, traffic policing) to those packets.
Note
Configuring Match on ATM CLP Bit for Ingress Policy
Perform the following steps to configure Match on ATM CLP Bit for the ingress policy:
Match on ATM CLP Bit Configuration Example
The following provides an example a Match on ATM CLP Bit configuration:
CFLOW_PE1# configure terminalEnter configuration commands, one per line. End with CNTL/Z.CFLOW_PE1(config)# class-map CLPCFLOW_PE1(config-cmap)# match atm clpCFLOW_PE1(config-cmap)# exitCFLOW_PE1(config)# policy-map CLP2EXPCFLOW_PE1(config-pmap)# class CLPCFLOW_PE1(config-pmap-c)# set mpls experimental 1CFLOW_PE1(config-pmap-c)# exitCFLOW_PE1(config-pmap)# interface ATM3/0/0CFLOW_PE1(config-if)# pvc 1/100CFLOW_PE1(cfg-if-atm-l2trans-pvc)# service-policy input CLP2EXPCFLOW_PE1(cfg-if-atm-l2trans-pvc)# endCFLOW_PE1#Verifying Match on ATM CLP Bit
Use the show policy-map interface command to verify the Match on ATM CLP Bit as in the following example:
CFLOW_PE1# show policy-map interface a3/0/0ATM3/0/0: VC 1/100 -Service-policy input: CLP2EXPClass-map: CLP (match-all)200 packets, 22400 bytes5 minute offered rate 2000 bps, drop rate 0 bpsMatch: atm clpQoS Setmpls experimental imposition 1Packets marked 200Class-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyCFLOW_PE1#Match on FR-DE Bit
Use Match on FR-DE Bit at the ingress to an MPLS AToM network to map the Frame Relay discard eligible (DE) bit of the packet arriving at an interface to the EXP value.
Guideline for Match on FR-DE Bit
The following guideline applies to this feature:
•
Configuring Match on FR-DE Bit for Ingress Policy
Perform the following steps to configure Match on FR-DE Bit for the ingress policy:
Example of Configuring a Match on the FR-DE Bit
The following example shows how to configure a match on the FR-DE bit for the ingress policy by applying the map-class policy to the main interface.
Applying Map-Class Policy to the Main Interface
osr3# show class-map match_fr-deClass Map match-all match_fr-de (id 2)Match fr-deosr3# show policy fr-de_mpls4Policy Map fr-de_mpls4Class match_fr-deset mpls experimental imposition 4Class class-defaultset mpls experimental imposition 4osr3# show run map-class | begin fr-de_mpls4map-class frame-relay fr-de_mpls4service-policy input fr-de_mpls4!map-class frame-relay fr-de_mpls0service-policy input fr-de_mpls0!osr3# show run interface pos1/0/2Building configuration...Current configuration : 196 bytes!interface POS1/0/2mtu 5000no ip addressencapsulation frame-relay IETFno keepaliveclock source internalpos scramble-atmframe-relay intf-type dceendconnect frompls_1 POS1/0/2 16 l2transportxconnect 11.11.11.11 2001 encapsulation mpls!!connect frompls_2 POS1/0/2 17 l2transportxconnect 11.11.11.11 2002 encapsulation mpls!!connect frompls_3 POS1/0/2 18 l2transportxconnect 11.11.11.11 2003 encapsulation mpls!!osr3# configure terminalEnter configuration commands, one per line. End with CNTL/Z.osr3(config)# interface POS1/0/2osr3(config-if)# frame-relay class fr-de_mpls4osr3(config-if)#osr3(config-if)#^Zosr3# show run interface pos1/0/2Building configuration...Current configuration : 196 bytes!interface POS1/0/2mtu 5000no ip addressencapsulation frame-relay IETFno keepaliveclock source internalpos scramble-atmframe-relay class fr-de_mpls4frame-relay intf-type dceendExamples of Matching on the FR-DE Bit Verification
Verify the configuration with the show policy-map interface command.
osr3# show policy interface pos1/0/2POS1/0/2: DLCI 16 -Service-policy input: fr-de_mpls4Class-map: match_fr-de (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: fr-deQoS Setmpls experimental imposition 4Packets marked 0Class-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyQoS Setmpls experimental imposition 4Packets marked 0POS1/0/2: DLCI 1007 -Service-policy input: fr-de_mpls4--More--Configuring a Match on the FR-DE Bit for the Ingress Policy
The following example shows how to configure a match on the FR-DE bit for the ingress policy by applying the map-class policy to the different DLCIs:
osr1# show policy fr-de_mpls2Policy Map fr-de_mpls2Class match_fr-deset mpls experimental imposition 2Class class-defaultset mpls experimental imposition 2osr1# sh policy fr-de_mpls3Policy Map fr-de_mpls3Class match_fr-deset mpls experimental imposition 3Class class-defaultset mpls experimental imposition 3osr1# show class-map match_fr-deClass Map match-all match_fr-de (id 1)Match fr-deosr1# show run map-class | begin fr-de_mplsmap-class frame-relay fr-de_mpls2service-policy input fr-de_mpls2!map-class frame-relay fr-de_mpls3service-policy input fr-de_mpls3!osr1# configure terminalEnter configuration commands, one per line. End with CNTL/Z.osr1(config)#int pos1/7osr1(config-if)#frame-relay interface-dlci 16 switchedosr1(config-fr-dlci)#class fr-de_mpls2osr1(config-fr-dlci)#exitosr1(config-if)#osr1(config-if)#frame-relay interface-dlci 17 switchedosr1(config-fr-dlci)#class fr-de_mpls3osr1(config-fr-dlci)#osr1(config-fr-dlci)#exitosr1(config-if)#osr1(config-if)#^Zosr1#osr1# show run interface pos1/7Building configuration...Current configuration : 39671 bytes!interface POS1/7mtu 5000no ip addressencapsulation frame-relay IETFno keepalivemls qos trust dscpclock source internalpos scramble-atmframe-relay interface-dlci 16 switchedclass fr-de_mpls2frame-relay interface-dlci 17 switchedclass fr-de_mpls3frame-relay interface-dlci 18 switchedframe-relay interface-dlci 19 switched...Verify the Configuration
Verify the configuration with the show policy-map interface command.
osr1# show policy interface pos1/7POS1/7: DLCI 16 -Service-policy input: fr-de_mpls2Class-map: match_fr-de (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: fr-deQoS Setmpls experimental imposition 2Packets marked 0Class-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyQoS Setmpls experimental imposition 2Packets marked 0POS1/7: DLCI 17 -Service-policy input: fr-de_mpls3Class-map: match_fr-de (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: fr-deQoS Setmpls experimental imposition 3Packets marked 0Class-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyQoS Setmpls experimental imposition 3Packets marked 0osr1#Set on ATM CLP Bit
Use Set on ATM CLP Bit at the egress interface of an MPLS AToM network to map the EXP value to the ATM CLP bit.
Note
Configuring Set on ATM CLP Bit for Egress Policy
Perform the following steps to configure Set on ATM CLP Bit for the egress policy:
Set on ATM CLP Bit Configuration Example
The following provides a Set on ATM CLP Bit configuration example:
7600router# show policy qg2clpPolicy Map qg2clpClass qg1set atm-clp7600router# show class-map qg1Class Map match-all qg1 (id 23)Match qos-group 17600router# show run interface a9/1interface ATM9/1no ip addressatm clock INTERNALatm mtu-reject-callmls qos trust dscppvc 1/100 l2transportencapsulation aal5mpls l2transport route 101.101.101.101 1000service-policy out qg2clpMatch on ATM CLP Bit Verification Example
Verify the configuration with the show policy-map interface command.
7600router# show policy interface ATM9/1ATM9/1: VC 1/100 -Service-policy output: qg2clpClass-map: qg1 (match-all)1000 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: qos-group 1QoS Setatm-clpPackets marked 1000Set on FR-DE Bit
Use Set on FR-DE Bit at the egress interface of an MPLS AToM network to map the EXP value to the FR-DE bit.
Configuring Set on FR-DE Bit for the Egress Policy
Perform the following steps to configure Set on FR-DE Bit for the egress policy:
Set on FR-DE Configuration Example
The following example shows a Set on FR-DE configuration example:
7600router# show policy qg2dePolicy Map qg2deClass qg1set fr-de7600router# show class-map qg1Class Map match-all qg1 (id 23)Match qos-group 17600router# show run interface pos2/2/0interface POS2/2/0no ip addressencapsulation frame-relayframe-relay interface-dlci 16 switchedclass QG2DESet on FR-DE Verification Example
Verify the configuration with the show policy-map interface command.
7600router# show policy interface POS2/2/0POS2/2/0: DLCI 16 -Service-policy output: qg2deClass-map: qg1 (match-all)1000 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: qos-group 1QoS Setfr-dePackets marked 1000HQoS for Ethernet over MPLS Virtual Circuits
The Hierarchical Quality of Service (HQoS) for EoMPLS VCs feature enables hierarchical QoS services on WAN-based interfaces, allowing service providers to classify the traffic in customer Ethernet over MPLS networks before it is forwarded into the core network. This gives users of Cisco Catalyst 6500 series switches and Cisco 7600 series routers greater flexibility in providing QoS services to specific customers in their EoMPLS networks.
The HQoS for EoMPLS VCs feature allows you to classify EoMPLS networks in the following ways:
•
•
The use of hierarchical policy maps can simplify the configuration of the router, because the same child policy map can be used in multiple parent maps. You can also match multiple VLANs with one class map, as opposed to having separate class maps for each VLAN.
The HQoS for EoMPLS VCs feature does not require any upgrades to the customer-facing interfaces, because the HQoS policy map is applied to the WAN interface, allowing the customer-facing interfaces to be standard Ethernet interfaces.
Prerequisites for the HQoS for EoMPLS VCs Feature
•
Restrictions for the HQoS for EoMPLS VCs Feature
The following section lists restrictions for the HQoS for EoMPLS VC feature. Other restrictions may also apply to QoS services in general, depending on the supervisor module and line cards being used.
•
Note
•
•
•
•
•
Note
•
Attaching service policy to main and sub-interface concurrently is not allowed•
•
•
–
–
–
Note
•
•
•
•
Note
Supported Features
The HQoS for Ethernet over MPLS VCs feature supports the following commands on the class maps and policy maps for output interfaces.
The following are supported on parent policy maps:
•
•
The following are supported on child policy maps:
•
•
•
•
•
Related Commands
Do not confuse the match input vlan command with the match vlan command, which is also a class-map configuration command.
•
•
The match input vlan command can also be confused with the match input-interface vlan command, which matches packets being received on a logical VLAN interface that is used for inter-VLAN routing.
Tip
Configuring the HQoS for EoMPLS VCs Feature
To use a hierarchical QoS policy map for EoMPLS traffic, you must perform the following tasks. (All tasks are required.)
•
•
•
•
•
Note
Creating and Assigning a Policy Map to Mark the QoS Group at the Incoming Interface
To be able to classify traffic on a QoS group, you must first create a policy map that marks incoming packets with the desired QoS group value. You can set the QoS group value to the value of either the IP precedence bits or 802.1P CoS bits of the incoming packets. You then must assign that policy map to the incoming interface (which must be a Layer 2 LAN interface).
To perform these tasks, use the following procedure.
Command Sequence Summary
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Detailed Steps
Step 1
enable
Example:Router> enable
Router#
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Router(config)#
Enters global configuration mode.
Step 3
policy-map policy-map-name
Example:Router(config)# policy-map cos-to-qosgrp-pmap
Router(config-pmap)#
Creates a policy map with the specified name and enters policy-map configuration mode.
•
Step 4
description string
Example:Router(config-pmap)# description Sets QoS group to IP precedence bits of incoming packets
Router(config-pmap)#
(Optional) Defines an arbitrary string, up to 200 characters long, that describes this policy map.
Step 5
class class-default
Example:Router(config-pmap)# class class-default
Router(config-pmap-c)#
Specifies the default class to be used for traffic with this policy, and enters policy-map class configuration mode.
Step 6
set qos-group {cos | ip-precedence}
Example:Router(config-pmap-c)# set qos-group cos
Router(config-pmap-c)#
Sets a quality of service (QoS) group identifier (ID) that can be used later to classify packets.
•
•
Note
Step 7
interface if-type {slot/port | slot/subslot/port}
Example:Router(config-pmap-c)# interface GigabitEthernet 5/2
Router(config-if)#
Enters interface configuration mode for the incoming interface.
Note
Step 8
service-policy input policy-map-name
Example:Router(config-if)# service-policy input cos-to-qosgrp-pmap
Router(config-if)#
Attaches the specified policy map to the interface for input (ingress) traffic.
•
Note
Step 9
show policy-map policy-map-name [class class-map]
Example:Router# show policy-map prec-to-qosgrp-pmap
(command output)
Router#
(Optional) Displays the configured class map to verify the configuration. To display all policy maps, enter the command without any options. To display a specific policy map, specify its name on the command line. You can also display a specific class that is part of a specific policy map by adding the class option.
The following policy map sets the QoS group value to match the CoS value of the incoming packets. The policy map is then assigned to two interfaces:
policy-map cos-to-qosgroup-pmapclass class-defaultset qos-group cos...!interface GE 6/0service-policy input cos-to-qosgroup-pmap...!interface GE 6/1service-policy input cos-to-qosgroup-pmap...What to Do Next
After attaching the policy map to the input interface, create the class map to match on the QoS group value at the egress (outgoing) interface. See the next section, "Configuring the Class Map to Match on a QoS Group," for details.
Configuring the Class Map to Match on a QoS Group
To be able to match EoMPLS traffic using QoS groups, you must create class maps to match traffic on the basis of the QoS group value at the egress (outgoing) interface. To create these class maps, use the following procedure.
Prerequisites
•
•
Restrictions
•
–
–
•
Command Sequence Summary
These are the commands you
1.
2.
3.
4.
5.
6.
Detailed Steps
