To configure QoS features using the Modular QoS CLI, complete the following basic steps:

The class-map command is used to create a traffic class. A traffic class contains three major elements: a name, a series of match commands, and, if more than one match command exists in the traffic class, an instruction on how to evaluate these match commands.

The match commands are used to specify various criteria for classifying packets. Packets are checked to determine whether they match the criteria specified in the match commands; if a packet matches the specified criteria, that packet is considered a member of the class and is forwarded according to the QoS specifications set in the traffic policy. Packets that fail to meet any of the matching criteria are classified as members of the default traffic class.

For more information about the default traffic class, refer to the “Configuring the Modular Quality of Service Command-Line Interface” chapter of the http:/​/​www.cisco.com/​en/​US/​docs/​ios/​12_2/​qos/​configuration/​guide/​qcfmdcli.html Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 document.

After creating traffic classes, you can configure traffic policies to configure marking features to apply certain actions to the selected traffic in those classes.

The policy-map command is used to create a traffic policy. The purpose of a traffic policy is to configure the QoS features that should be associated with the traffic that has been classified in a user-specified traffic class.

Note	A packet can match only one traffic class within a traffic policy. If a packet matches more than one traffic class in the traffic policy, the first traffic class defined in the policy will be used.

The service-policy command is used to attach the traffic policy, as specified with the policy-map command, to an interface. Because the elements of the traffic policy can be applied to packets entering and leaving the interface, it is essential to specify whether the traffic policy characteristics should be applied to incoming or outgoing packets.

To attach a policy map that the router can use to apply QoS policies to inbound and outbound packets, use the service-policy command in interface or map class configuration mode.

To restrict the WAN interface bandwidth output rate to a smaller value than that of the physical link bandwidth, use the output-rate command in interface configuration mode.

Note	The output-rate command is valid only for Gigabit Ethernet interfaces.

Note	Starting with Cisco IOS Release 12.2(33)SCG, the output-rate command is not supported and the value 10,000 is used for the output line rate on a Cisco uBR10012 router.

To configure input MQC on a cable bundle interface to differentiate upstream traffic and set corresponding “qos-group” features, follow the steps given below.

The following example shows how to create two traffic classes and specify their match criteria. For the first traffic class called class1, access control list (ACL) 101 is used as the match criteria. For the second traffic class called class2, ACL 102 is used as the match criteria. Packets are checked against the contents of these ACLs to determine if they belong to the class.

Router(config)# class-map class1
 
Router(config-cmap)# match access-group 101 
Router(config-cmap)# exit
 
Router(config)# class-map class2
 
Router(config-cmap)# match access-group 102
 
Router(config-cmap)# exit

The following example shows how to define a traffic policy called policy1 that contains policy specifications for class1.

Router(config)# policy-map policy1
Router(config-pmap)# class class1 
Router(config-pmap-c)# bandwidth 3000
  
Router(config-pmap-c)# queue-limit 30
 
Router(config-pmap)# exit

The following example shows how to attach an existing traffic policy to an interface. After you define a traffic policy with the policy-map command, you can attach it to one or more interfaces by using the service-policy command in interface configuration mode. Although you can assign the same traffic policy to multiple interfaces, each interface can have only one traffic policy attached at the input and only one traffic policy attached at the output.

Router(config)# interface GigabitEthernet 3/0/0
Router(config-if)# service-policy output policy1
  
Router(config-if)# exit
 

The following example shows how to verify a policy map configuration by entering any of the following commands in privileged EXEC mode.

Router# show policy-map policy-map-name class class-name
Class foobar
      bandwidth percent 20 
       packet-based wred, exponential weight 9
      random-detect aggregate
      random-detect precedence values 2 minimum-thresh 1024 maximum-thresh 20481

The following example shows how to differentiate upstream traffic on the cable bundle interfaces and set corresponding “qos-group” features.

!Define two different class maps.
class-map match-all class-ip-prec-6
  match ip precedence 6
class-map match-all class-ip-prec-7
  match ip precedence 7
!Define a policy map.
policy-map policy-input
  class class-ip-prec-6
   set qos-group 6
  class class-ip-prec-7
   set qos-group 7   
!Attach the policy map to the cable bundle interface in the input direction. 
configure terminal
 interface bundle 1
  service-policy input policy-input

Use the following procedure to specify a class-map and match a packet based on the CoS marking.

Use the following procedure to specify a policy-map and associate a map class with it to set the CoS value for an outgoing packet.

Use the following procedure to specify a class-map and match a packet based on the EXP marking.

Use the following procedure to specify a policy-map and associate a map class set to the EXP value for an outgoing packet.

The following example shows how to match traffic classes within the 802.1p domain using packet CoS values.

Router> enable
Router# configure terminal
Router(config)# class-map cos1 
Router(config-cmap)# match cos 0
Router(config-cmap)# end

The following example shows how to define traffic classes within the 802.1p domain using packet CoS values.

Router> enable
Router# configure terminal
Router(config)# policy-map cos2
Router(config-pmap)# class cos1
Router(config-pmap)# set cos 2
Router(config-pmap)# end

The following example shows how to match traffic classes within the MPLS domain using packet EXP values.

Router> enable
Router# configure terminal
Router(config)# class-map exp1
Router(config-cmap)# match mpls experimental topmost 2
Router(config-cmap)# end

The following example shows how to define traffic classes within the MPLS domain using packet EXP values.

Router> enable
Router# configure terminal
Router(config)# policy-map exp2
Router(config-pmap)# class exp1
Router(config-pmap)# set mpls experimental topmost 2
Router(config-pmap)# end

The following example shows how to verify the matching and marking configuration by entering the following command in privileged EXEC mode:

Router# ping vrf vrfa 1.3.99.98
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.3.99.98, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/10/20 ms

The following example shows how to verify the QoS and service flow information for a particular cable modem (CM) by entering the following command in privileged EXEC mode:

Router# show cable modem 1.3.99.98 qos
Load for five secs: 1%/0%; one minute: 1%; five minutes: 1%
Time source is hardware calendar, *23:01:41.873 pst Thu Mar 3 2011
Sfid  Dir Curr  Sid   Sched  Prio MaxSusRate  MaxBrst     MinRsvRate  Throughput
          State       Type
49    US  act   31    BE     7    300000000   1000000     0           1968000
50    DS  act   N/A   BE     0    300000000   3044        0           1969253

The following example shows how to verify the statistics and the configurations of the input and output service policies that are attached to an interface by entering the following command in privileged EXEC mode:

Router# show policy-map interface gigabitEthernet 1/2/0
Load for five secs: 1%/0%; one minute: 1%; five minutes: 1%
Time source is hardware calendar, *23:02:40.857 pst Thu Mar 3 2011
 GigabitEthernet1/2/0
  Service-policy input: policy-in
    Class-map: class-exp-0 (match-all)
      6647740 packets, 9304674796 bytes
      30 second offered rate 3234000 bps, drop rate 0 bps
      Match: mpls experimental topmost 0
      QoS Set
        precedence 3
          Packets marked 6647740
    Class-map: class-default (match-any)
      1386487 packets, 1903797872 bytes
      30 second offered rate 658000 bps, drop rate 0 bps
      Match: any
  Service-policy output: policy-out
    Class-map: class-pre-1 (match-all)
      2041355 packets, 2857897000 bytes
      30 second offered rate 986000 bps, drop rate 0 bps
      Match: ip precedence 1
      QoS Set
        mpls experimental topmost 1
          Packets marked 2041355
    Class-map: class-default (match-any)
      6129975 packets, 8575183331 bytes
      30 second offered rate 2960000 bps, drop rate 0 bps
      Match: any

The following example shows how to verify the Parallel eXpress Forwarding (PXF) CPU statistics and QoS for a particular interface by entering the following command in privileged EXEC mode:

Router# show pxf cpu statistics qos gigabitEthernet 1/2/0
Load for five secs: 1%/0%; one minute: 1%; five minutes: 1%
Time source is hardware calendar, *23:04:11.893 pst Thu Mar 3 2011
   Classmap           Match         Pkts           Bytes
    Index             Number        Matched        Matched
--------------- --------------- --------------- -------------
 policy-in (Input) service-policy :
class-exp-0     (0)     0               6674330         751960948
class-default   (1)     0               1392134         1911548970
 policy-out (Output) service-policy :
class-pre-1     (0)     0               2049682         2869554800
class-default   (1)     0               6154976         20224030

The following example shows how to verify the state of all virtual circuits associated with an MPLS pseudowire by entering the following command in privileged EXEC mode:

Router# show cable l2-vpn xconnect mpls-vc-map state
Load for five secs: 2%/0%; one minute: 2%; five minutes: 1%
Time source is hardware calendar, *23:05:30.061 pst Thu Mar 3 2011
MAC Address    Peer IP Address  VCID  Type  Prio  State  Customer Name/VPNID  State
54d4.6f88.7362  10.8.8.8        97    Prim*        UP                          UP

The following example shows how to verify the details about the mapping between an MPLS pseudowire and its virtual circuits by entering the following command in privileged EXEC mode:

Router# show cable l2-vpn xconnect mpls-vc-map 54d4.6f88.7362 verbose
Load for five secs: 2%/0%; one minute: 1%; five minutes: 2%
Time source is hardware calendar, *16:46:29.139 pst Thu Mar 3 2011
MAC Address                         : 54d4.6f88.7362
Customer Name                       : 
Prim Sid                            : 18
Cable Interface                     : Cable5/0/1
MPLS-EXP                            : 0
PW TYPE                             : Ethernet
Backup enable delay                 : 0 seconds
Backup disable delay                : 0 seconds
Primary peer
Peer IP Address (Active)            : 10.8.8.8
XConnect VCID                       : 97
Circuit  ID                         : Bu254:97
Local State                         : UP
Remote State                        : UP
Total US pkts                       : 418756
Total US bytes                      : 586227332
Total US pkts   discards            : 0
Total US bytes  discards            : 0
Total DS pkts                       : 417347
Total DS bytes                      : 591773612
Total DS pkts   discards            : 0
Total DS bytes  discards            : 0