Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Cisco ME 2600X Series Ethernet Access Switch Software Configuration Guide

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco ME 2600X Series Ethernet Access Switch Software Configuration Guide

Chapter Title

Quality of Service

Results

Updated:
November 17, 2017

Chapter: Quality of Service

Contents

Quality of Service

This chapter describes the Quality of Service for Cisco ME 2600X and procedures to configure Quality of Service.

Quality of Service

Quality of Service (QoS) refers to the ability of a network to provide improved services to selected network traffic over various underlying technologies including Ethernet and IEEE 802.1 networks.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Toolkit and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http:/​/​www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

Prerequisites for QoS

The following two components are necessary to deliver QoS across a heterogeneous network:
  • QoS within a single network element, which includes queuing, scheduling, and traffic shaping features.
  • QoS policing and management functions to control and administer end-to-end traffic across a network.

Restrictions for QoS

The following are the general restrictions for the QoS feature:

  • Policing is not supported at egress level.
  • Only 0 to 6 queues can be used at egress. QoS-Group 3 is used for LLQ (Priority) traffic at egress.
  • Remarking does not happen if the outer or inner VLAN is configured with ANY, LIST, or RANGE.
  • COS marking fails with encapsulation VLAN range and match VLAN range.
  • The police cir command is not supported at the parent level in the hierarchical quality of service (HQoS). HQoS supports only the police rate command at parent level.
  • Parent level should always be class-default in HQoS.
  • An ingress policer does not support more than 8 classes.
  • An egress policer does not support more than 7 classes.

Information About QoS

The QoS mechanism has three basic steps. It classifies types of traffic, specifies what action to take against a type of traffic, and specifies where the action should take place. The following sections explain how the Cisco ME 2600X accomplishes these steps.

Classification Mechanism for IP and Ethernet

For any QoS service to be applied to data, there must be a way to classify an IP packet or an Ethernet frame. When identified, a specific priority can be assigned to each individual IP packet or Ethernet frame. The IP Precedence field or the IP Differentiated Services Code Point (DSCP) field can be used to classify IP packets, and the Ethernet class of service (IEEE 802.1p defined class of service [CoS]) can be used for classifying Ethernet frames. IP precedence, IP DSCP, and Ethernet CoS are further described in the following sections.

IP Precedence

Use of IP precedence enables you to specify the class of service (CoS) for a packet using the three precedence bits in the type of service (ToS) field of the IP version 4 (IPv4) header. By default, each precedence corresponds to a name. These names, which continue to evolve, are defined in RFC 791.
Number Name
0 routine
1 priority
2 immediate
3 flash
4 flash-override
5 critical
6 internet
7 networks

Note

IP precedence bit settings 6 and 7 are reserved for network control information, such as routing updates.

IP Differentiated Services Code Point

IP DSCP uses the six bits in the IPv4 header to specify class of service for each IP packet (IETF RFC 2474). The DSCP field classifies packets into any of the 64 possible classes. On the network edge, the IP DSCP is assigned by the client device or the switch, so that each subsequent network element can provide services based on the determined policy or the SLA.

IP Precedence and DSCP is illustrated in this figure.
Figure 1. IP Precedence and DSCP

Ethernet CoS

The Ethernet CoS refers to the three bits within a four byte IEEE 802.1Q (VLAN) header used to indicate the priority of the Ethernet frame as it passes through a switched network. The CoS bits in the IEEE 802.1Q header are commonly referred to as the IEEE 802.1p bits. There are three CoS bits that provide eight classes, matching the IP precedence number. In many real-world networks, a packet might traverse both Layer 2 and Layer 3 domains. To maintain QoS across the network, the IP ToS can be mapped to the Ethernet CoS and vice versa. For example, in a linear or one-to-one mapping where each mechanism supports eight classes. Similarly, a set of DSCP values (64 classes) can be mapped into each of the eight individual Ethernet CoS values. An IEEE 802.1Q Ethernet frame, which consists of a 2-byte Ethertype and a 2-byte tag (IEEE 802.1Q tag) on the Ethernet protocol header is shown in this figure.
Figure 2. Ethernet Frame and the CoS Bit (IEEE 802.1p)

Advantages of QoS

Enabling QoS in the network has the following advantages:

  • Control over resources—You can control resources like bandwidth that is being used.
  • Tailored services—If you are a service provider, the control and visibility that QoS provides enable you to offer carefully tailored grades of service differentiation to your customers.
  • Coexistence of mission-critical applications:
    • Your WAN is used efficiently by mission-critical applications that are most important to your business.
    • Bandwidth and minimum delays required by time-sensitive multimedia and voice applications are available.
    • Other applications using the link get their fair service without interfering with mission-critical traffic.

Cisco ME 2600X QoS

The Cisco ME 2600X QoS classifies each packet in the network based on its Ethernet CoS, IP precedence, IP DSCP, or VLAN ID. After they are classified into class flows, further QoS functions can be applied to each packet as it traverses the Cisco ME 2600X.

The policing feature of the Cisco ME 2600X system ensures that the attached equipment does not submit more than a predefined amount of bandwidth (Rate Limiting) into the network. The policing feature can be used to enforce the committed information rate (CIR) and the peak information rate (PIR) available to a customer at an interface. The policing action is applied per classification.

The marking feature can set the Ethernet CoS, IP precedence, or IP DSCP bits when packets enter the Cisco ME 2600X. The marking feature operates on the outer IEEE 802.1p tag, IP precedence, or IP DSCP bits and provides a mechanism for tagging packets at the ingress. The subsequent network elements can provide a QoS based only the QoS indicator that the service provider has created.

The per-class queuing allows various queuing applications to support SLA. For example, allocation of committed information rate, ensuring low latencies and rate limiting traffic to down stream nodes based on the configuration, and also enabling fair access to excess network bandwidth. The Cisco ME 2600X uses a combination of Strict Priority Queuing (SPQ) and Weighted Round Robin (WRR) scheduling process to guarantee throughput and latency requirements and to provide fair access to excess bandwidth. The Cisco ME 2600X QoS flow is illustrated in this figure.
Figure 3. Cisco ME 2600X QoS flow

Ingress QoS Functions

Ingress QoS on the Cisco ME 2600X system involves classification, marking, and policing. The ingress card classifies the packets and assigns a traffic-class to it. The traffic-class is used for internal queuing and congestion management, as well as classification at the egress. At ingress, policy application is supported on multiple targets, which are:
  • Ten Gigabit Ethernet (10 GE) and one Gigabit Ethernet (1 GE) interface
  • Port-channel interface
  • Port-channel member interface
  • Service instance on 10 GE and 1 GE interfaces
  • Service instance on port-channel

Ingress Classification

Classifying network traffic enables you to organize traffic into traffic classes or categories on the basis of whether the traffic matches specific criteria. Using the packet classification, you can partition network traffic into multiple priority levels or classes of service. Traffic is classified to determine whether it should be:

  • Marked for further processing
  • Policed to rate limit specific traffic types

The Cisco ME 2600X system supports ingress classification. The default class, named class-default, is the class to which any traffic that does not match any of the selection criteria in the configured class maps, is directed.

To configure ingress classification, see Configuring Ingress Classification.

Ingress Policing

Ingress policing ensures that an attached equipment does not submit more than a predefined amount of bandwidth (Rate Limiting) into the network. The policing feature can be used to enforce the committed information rate (CIR) and the peak information rate (PIR) available to a customer at an interface or a service instance on an interface. Policing enables to limit the data flow through the Cisco ME 2600X by dropping or marking down the QoS value according to the configuration.

The Cisco ME 2600X supports ingress policing. When policing is configured, traffic is placed in one of the following categories:

  • Conform
  • Exceed
  • Violate

Within these three categories, users can decide the actions to be applied. For instance, packets that conform to the policy rate can be configured to be transmitted, packets that exceed the policy rate can be configured to be sent with a decreased priority, and packets that violate the policy rate can be configured to be dropped. If no actions are specified, the default conform-action is transmit, and default exceed-action or violate-action is drop.

The table below contains the list of policing actions supported at the ingress:

Table 1 Policing Actions
Action Purpose

transmit

Transmits the packet.

drop

Drops the packet.

set-cos-transmit

Sets the CoS value and transmits the packet.

set-dscp-transmit

Sets the IP DSCP value and transmit the packet.

set-precedence-transmit

Sets the IP precedence value and transmits the packet.

set-qos-transmit

Sets the QoS-group value and transmits the packet.

The policing features supported are:

  • Individual actions
  • Multiple actions
  • Single rate, 2-color policer
  • Single rate, 3-color policer
  • Dual rate, 3-color policer
  • Color blind mode
  • Hierarchical policing (two levels)

To create a policy-map, see Configuring Ingress Policing.

To attach or remove a traffic policy from the interface, see Attaching or Removing a Traffic Policy from the Target.

Ingress Marking

Marking is a way to selectively modify QoS bits in a packet to identify traffic within the system and/or the network. The downstream devices in the network and the egress targets within the system can match the traffic based on the marking done at the ingress of the system. The Cisco ME 2600X supports ingress marking.

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

In most cases, the purpose of a packet mark is identification. After a packet is marked, downstream devices identify traffic based on the marking and categorize the traffic according to network needs. This categorization occurs when the match commands in the traffic class are configured to identify the packets by their marking (for example, match IP precedence, match IP DSCP, match CoS, and so on). The traffic policy using this traffic class can then set the appropriate QoS features for the marked traffic.

To configure ingress marking, see Configuring Ingress Marking.

Egress QoS Functions

For FTTH LAG QoS, service policy application can only happen at port-channel main interface. This policy application should in turn be mapped statically to member interfaces. No egress policy-map application allowed on port-channel member interface or EFP.

QoS for Multicast/Unicast Traffic

While applying QOS, there is no differentiation between unicast and multicast traffic at the queue level. Both the streams are treated equally at queue level for QoS. There are no specific classes available to apply the QoS specific to multicast traffic.

Traffic Handling in the Absence of an Output Policy

If there is no output policy configured on an EVC or an interface, the unicast traffic is queued at the egress based on the traffic class set at the ingress. In the absence of an output policy, all the egress queues are treated equally and scheduled according to the Round Robin method.

Unicast QoS Restrictions

Traffic is queued in separate queues at the egress based on the traffic-class set in the frame at the ingress. This is irrespective of whether there is an egress policy applied or not.


Note

The “class-default” classification does not work at the leaf level of an output policy. This works only at a parent level in a hierarchical policy. It must be ensured that all traffic that needs to be matched using “class-default” at the leaf level is set to “qos-group 0” at the ingress, which forces the traffic-class to 0 resulting in traffic being queued in queue 0 which corresponds to the class-default.

Egress Classification

The egress classification is limited to using a traffic class field in frames to categorize the frames and make them available for QoS handling. Therefore, classification based on frame fields, such as Ethernet CoS, IP DSCP, IP precedence, and so on, should be done at ingress, and the traffic class should be assigned to the corresponding frames using the ingress marking feature.

Traffic is classified to determine whether it should be:
  • Marked for further processing
  • Queued and scheduled

To configure classification at the egress, see Configuring Egress Classification.

Egress Queue Scheduling

The Cisco ME 2600X system supports Weighted Round Robin (WRR) and Low Latency Queueing (LLQ). Queueing is based on the class based classification done at egress. LLQ prioritizes and ensures low latency to the traffic in queues configured to be in LLQ, and the remaining traffic is scheduled using WRR.


Note

Queue depth is not configurable. Each queue has a minimum depth of 25600 bytes and maximum depth of 1048576 bytes.

For information on egress LLQ, see Egress LLQ.

For information on egress bandwidth, see Egress Bandwidth.

For information on egress shaping, see Egress Shaping.

For information egress Bandwidth Remaining Ratio (BRR) or Bandwidth Remaining Percent (BRP), see Egress Bandwidth Remaining Ratio and Bandwidth Remaining Percent.

Egress LLQ

Applications which are latency sensitive require handling of data with least possible delay within the system. In the Cisco ME 2600X system, low latencies are guaranteed by using strict priority scheduling at various congestion points and egress.

To configure LLQ, see Configuring Egress LLQ.

Egress Bandwidth

Applications that require committed information rate (CIR) should reserve the CIR on a per-target basis at the egress. After configuring the CIR, the traffic rates are guaranteed to be met in case of congestion at the egress.

To configure the egress bandwidth, see Configuring Egress Bandwidth.

Egress Shaping

Traffic shaping enables you to control the traffic going out of an interface in order to match its flow to the speed of the remote target interface and to ensure that the traffic conforms to policies contracted for it. Shaping can be used to meet downstream requirements, thereby eliminating bottlenecks in topologies with data-rate mismatches.

Shaping is the process of delaying packets in queues to make them conform to a specified profile.

To configure shaping at the egress, see Configuring Egress Shaping.

Egress Bandwidth Remaining Ratio and Bandwidth Remaining Percent

Bandwidth Remaining Ratio (BRR) or Bandwidth Remaining Percent (BRP) specifies the ratio or percentage of the bandwidth that is divided between targets when there is congestion. BRR indicates the ratio with which the various classes are serviced when parent target is scheduled. BRP indicates the bandwidth to be allocated to each class as a percentage of the allocation done to the parent target in a hierarchical QoS model.

To configure egress BRR or BRP, see Configuring Egress Bandwidth Remaining Ratio or Bandwidth Remaining Percent.

Hierarchical QoS

The Cisco ME 2600X system supports hierarchical quality-of-service (H-QoS) that includes QoS at multiple levels in a hierarchy.

Ingress H-QoS

An H-QoS policy can be attached to an interface or a service instance. The number of levels is limited to two for an input QoS policy, where the parent level denotes the policy target and the child level denotes the QoS traffic class:

  • Only the default class, that is, class-default is allowed at the parent level. User-defined classes are not supported at the parent level.
  • Only the police action command is allowed at the parent level. Marking action is not supported. Also, remarking actions are not supported for the parent policer. In effect, a hierarchical policy is configured to achieve only hierarchical metering.

EVCS QoS Support

The Ethernet Virtual Connection Services (EVCS) uses the concept of service instances and EVC (Ethernet Virtual Circuit). A service instance is the instantiation of an EVC on a given interface on a given device. An EVC is an end-to-end representation of a single instance of a Layer 2 service being offered by a provider to a customer. It embodies the different parameters on which the service is being offered.

QoS works with the following EVC combinations:

  • One TAG case
  • Two TAG case
  • One TAG to one TAG
  • One TAG to two TAG
  • Two TAG to one TAG
  • Two TAG to two TAG
  • One TAG termination
  • Two TAG termination
  • Tag to Tag translation

Restrictions for QoS on EVCS

  • CoS marking or remarking is not supported for service instances defined using VLAN ranges or “encapsulation default”.
  • CoS marking or remarking action applies to both inner and outer tags, when inner tag is modified within the system. In all other cases, the marking or remarking action that the user specifies is limited only to the outer tag.

Note
For information on EVC, see Understanding Ethernet Virtual Circuit.

QoS Support on Port-Channel

This section explains the QoS on the Port-Channel feature support for ingress and egress.

QoS Support on Port-Channel at Ingress

The QoS on the port-channel feature enables QoS service-policies to be applied at the ingress on the following targets:

  • Port-channel member link
  • Port-channel main interface
  • Port-channel EVC

For a policy-map attached to a port-channel main interface, ingress traffic coming from any member link is subjected to the same policy-map configured on the port-channel main interface. If no policy-map is configured on the port-channel main interface, ingress traffic from the member-link is subjected to the policy-map attached to the:

  • EVC through which the traffic is flowing.
  • Member link.

The QoS policy can be attached to a port-channel even if the member interfaces are on different cards. Policy-maps cannot coexist on a port-channel main interface, EVC, and member link at the same time.

Restrictions for QoS Support on Port-Channel at Ingress

The policer configuration is enforced only on a single card and not across cards in a distributed link aggregation group (LAG). However, member links might span across cards.

QoS Support on Port-Channel at Egress

The QoS on port-channel feature enables QoS service-policies to be applied at the egress on the port-channel main interface.


Note

Egress service policy is not supported on the port-channel member link.

Restrictions for QoS Support on Port-Channel at Egress

A policy that is applied on a port channel is not applicable to the aggregate port channel traffic. It is applicable only on a per port-channel member basis. Therefore, if a configuration that shapes all the traffic to x Mbps on the port-channel main interface exists, it gets translated to a configuration that shapes each member link to x Mbps. As a result, the aggregate traffic on the port channel could be up to n times x Mbps, where n is the number of links in the port-channel.

QoS Statistics

Enhanced performance monitoring displays QoS statistics on the Cisco ME 2600X interfaces. QoS statistics are supported at the 1GE interface, 10GE interface, and service instance levels. At the ingress, only byte counters are supported and at the egress, both packet and byte counters are supported.

Statistics supported at ingress are shown in the table below:
Table 2 Statistics at Ingress
Statistics Collected 1GE Interface 10GE Interface EVC Port Channel Interface
Classification statistics— Packet and Byte Counters Yes Yes Yes Yes
Marking Statistics—Byte Counters No No No No
Marking Statistics—Packet Counters Yes Yes Yes Yes
Policing Statistics—Packet and Byte Counters Supported with limitations:
  • In a 2-color policer, both green and red byte counters are supported.
  • In a 3-color policer, green/non-green or non-red/red are supported.
Supported with limitations:
  • In a 2-color policer, both green and red byte counters are supported.
  • In a 3-color policer, green and non-green or non-red and red are supported.
No Supported with limitations:
  • In a 2-color policer, both green and red byte counters are supported.
  • In a 3-color policer, green/non-green or non-red/red are supported.
Statistics supported at egress are shown in this table:
Table 3 Statistics at Egress
Statistics Collected 1GE Interface 10GE Interface EVC Port Channel Interface
Classification statistics - Packet and Byte Counters Yes Yes No Yes
Queuing Statistics— (Accepted or Dropped) Packet and Byte Counters Yes Yes No Yes
Match Statistics—Packet and Byte Counters Yes Yes No Yes

Scalability

The table below lists scalability for Cisco ME 2600X:

320 x 8 policiers
System supports 320 policymaps
System supports 512 unique class maps
System supports 1024 unique policymaps
160 policymaps on LAG interface
7 queues / classes per interface

Note

If all the FP entries are used under port-channel pool (LAG interface has maximum EFPs with maximum number of filters), then LAG works in double mode and you can not apply ingress policer on any interface or service instance.

How to Configure QoS

The following tasks describe how to configure QoS on the Cisco ME 2600X device:

Configuring QoS Features


Note

Users can create traffic policies and attach these policies to targets. A traffic policy contains a traffic class and one or more QoS features. A traffic class is used to classify traffic, while the QoS features in the traffic policy determine how to treat the classified traffic.

SUMMARY STEPS

    1.    Define a traffic class using the class-map command:

    2.    Create a traffic policy using the policy-map command to associate the traffic class with one or more QoS features (using the policy-map command):

    3.    Attach the traffic policy to the target using the service-policy command, see Attaching or Removing a Traffic Policy from the Target.

    4.    Monitor and verify the QoS configuration. See Monitoring and Verifying QoS Configuration.


DETAILED STEPS
    Step 1   Define a traffic class using the class-map command:
    1. To configure traffic classification at the ingress, see Configuring Ingress Classification.
    2. To configure traffic classification at the egress, see Configuring Egress Classification.
    Step 2   Create a traffic policy using the policy-map command to associate the traffic class with one or more QoS features (using the policy-map command):
    1. To configure policing at the ingress, see Configuring Ingress Policing.
    2. To configure marking at the ingress, see Configuring Ingress Marking.
    3. To configure shaping at the egress, see Configuring Egress Shaping.
    4. To configure the egress bandwidth, see Configuring Egress Bandwidth.
    5. To configure low-latency queuing (LLQ), see Configuring Egress LLQ.
    6. To configure bandwidth remaining ratio (BRR) or bandwidth remaining percent (BRP), see Configuring Egress Bandwidth Remaining Ratio or Bandwidth Remaining Percent.
    Step 3   Attach the traffic policy to the target using the service-policy command, see Attaching or Removing a Traffic Policy from the Target.
    Step 4   Monitor and verify the QoS configuration. See Monitoring and Verifying QoS Configuration.

    Configuring Ingress Classification

    • The match commands are used to specify various criteria for classifying packets. The packets are checked to determine whether they match the criteria specified in the match commands.
    • The match-all keyword is added to the match command and match-all is the default. This classification specifies that the traffic class must match all of the specified criteria within the class-map.
    • The CoS should be 0 by default for untagged traffic and it will be matched with a CoS 0 filter, if the class-map has the CoS 0 filter.

    To configure ingress classification on the device, complete the following steps:

    Before You Begin

    Note
    • Traffic classification based on multiple QoS fields (Ethernet class of service [CoS], IP precedence, and so on) for a single packet is not supported. Traffic classification is based only on the first matching parameter (in the user-specified order) of the QoS fields, if multiple match criteria are specified in a single class.
    • The match-all cannot have more than two combinations of the classification criteria. However, the class-map can be created with more than two combinations of classification criteria. The policy with such class-map does not work and reports an error message indicating the failure. You should rectify the class-map with one classification criteria and try again.
    • When using class-map, after you have added or removed a filter, do not immediately remove or add another filter as it may cause an error message to display. If you receive an error message, try again by increasing the time interval between removal or addition of the filter.
    SUMMARY STEPS

      1.    enable

      2.    configure terminal

      3.    class-map [match-any]| [match-all] class-map-name

      4.    match cos cos-number

      5.    end


    DETAILED STEPS
       Command or ActionPurpose
      Step 1enable


      Example:
      Switch> enable
       

      Enables privileged EXEC mode.

      • Enter your password if prompted.
       
      Step 2configure terminal


      Example:
      Switch# configure terminal
       

      Enters global configuration mode.

       
      Step 3class-map [match-any]| [match-all] class-map-name

      Example:
      Switch(config)# class-map match-any class1
       
      Creates a class to be used with a class map and enters the class-map configuration mode. The class map is used for matching packets to the specified class.
      • match-any— Specifies that one of the match criterion must be met. Use this keyword only if you have to specify more than one match command.
      • match-all— Specifies that the traffic class must match all of the specified criteria.
      • class-map-name— Class map name. This is the name of the class map and can have a maximum of 40 alphanumeric characters.
       
      Step 4match cos cos-number


      Example:
      Switch(config-cmap)# match cos 2
       
      Matches a packet on the basis of a Layer 2 CoS number.
      • cos-number— CoS value. The value can range from 0 to 7.
      Note   

      The match cos command is just an example of one of the match commands that can be used. For a list of other match commands, see Table 1

       
      Step 5end


      Example:
      Switch(config-cmap)# end
       

      Exits class-map configuration mode and returns to privileged EXEC mode.

       

      The table below provides the traffic class commands supported at the ingress:

      Table 4 Traffic Class Commands
      Command Description
      match cos cos-number

      Example:

      Switch(config-cmap)# match cos 2
      Matches a packet on the basis of a Layer 2 CoS number.
      • cos-number— CoS value. The value can range from 0 to 7.
      match ip precedence ip-precedence-value

      Example:

      Switch(config-cmap)# match ip precedence 5
      Identifies the IP precedence value as match criteria.
      • ip-precedence-value— IP precedence value. The value can range from 0 to 7.
      match ip dscp ip- dscp-value

      Example:

      Switch(config-cmap)# match ip dscp 6
      Identifies a specific IP DSCP value as a match criterion.
      • ip- dscp-value — IP DSCP value. The value can range from 0 to 63.
      match vlan [vlanid ]

      Example:

      Switch(config-cmap)# match vlan 100
      Specifies a VLAN ID or range of VLAN IDs in a class-map to match packets.
      • vlanid —VLAN ID. The value can range from 0 to 4096.

      Configuring Ingress Policing

      To configure ingress policing on the device, complete the following steps:
      Before You BeginConfiguring Ingress Classification

      Note
      • In a hierarchical QoS policy, only a single-rate, 2-color policer is supported at the parent level. This should be configured using the police [rate] bps-value action command. The police cir command is not supported at the parent level.
      • In a hierarchical QoS policy with policer configured at the parent level, only a single-rate, 2-color policer or a dual-rate, 3-color policer is supported at the child level.
      SUMMARY STEPS

        1.    enable

        2.    configure terminal

        3.    policy-map policy-map-name

        4.    class {class-name | class-default}

        5.    police [cir | rate] bps-value [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action

        6.    end


      DETAILED STEPS
         Command or ActionPurpose
        Step 1enable


        Example:
        Switch> enable
         

        Enables privileged EXEC mode.

        • Enter your password if prompted.
         
        Step 2configure terminal


        Example:
        Switch# configure terminal
         

        Enters global configuration mode.

         
        Step 3policy-map policy-map-name


        Example:
        Switch(config)# policy-map policy1
         
        Creates or specifies the name of the traffic policy and enters the policy-map configuration mode.
        • policy-map-name—Policy map name. This is the name of the policy map and can have a maximum of 40 alphanumeric characters.
         
        Step 4 class {class-name | class-default}


        Example:
        Switch(config-pmap)# class class1
         
        Specifies the name of a traffic class to which the policy applies and enters the policy-map class configuration mode.
        • Enter the previously configured class-map name.
          • class-name—User-defined class name to which the policy applies.
          • class-default—Specifies that the policy applies to the default traffic class.
        Note   

        This step associates the traffic class with the traffic policy.

         
        Step 5police [cir | rate] bps-value [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action


        Example:
        Switch(config-pmap-c)# police cir 5000000 bc 200000 be 400000 conform-action transmit exceed-action set-dscp-transmit violate-action drop
         
        Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm:
        • cir—Indicates that the committed information rate (CIR) is used for policing traffic.
        • rate—Indicates that the police rate is used for policing traffic.
        • bps value—Average rate in bits per second. The valid values range from 8000 to 10000000000.
        • bc—Indicates that the committed (conform) burst size is used for policing traffic.
        • burst—Indicates that the burst size is used for policing traffic.
        • bc—Committed (conform) burst size or burst size in bytes. The valid values range from 1000 to 256000000.
        • be—Indicates that the excess burst size is used for policing traffic.
        • peak-burst—Indicates that the peak-burst size is used for policing traffic.
        • be—Excess burst size or peak-burst size in bytes. The valid values range from 1000 to 256000000.
        • action—Action taken on a packet when it conforms, exceeds, or violates the interface bandwidth. The possible actions are shown in Table 1.
        Note   

        The police [cir | rate] bps-value [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action command is just an example of one of the policy commands that can be used. For a list of other policy commands, see Table 1.

         
        Step 6end

        Example:
        Switch(config-pmap)# end
         

        Exits policy-map configuration mode and returns to privileged EXEC mode.

         

        The table below provides the traffic policy commands supported at the Ingress:

        Table 5 Traffic Policy Commands
        Command Description
        police [cir | rate] bps-value [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action

        Example:

        Switch(config-pmap-c)# police cir 5000000  bc 200000 be 400000 conform-action transmit  exceed-action set-dscp-transmit violate-action drop
        Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm:
        • cir—Indicates that the committed information rate (CIR) is used for policing traffic.
        • rate—Indicates that the police rate is used for policing traffic.
        • bps value—Average rate in bits per second. The valid values range from 8000 to 10000000000.
        • bc—Indicates that the committed (conform) burst size is used for policing traffic.
        • burst—Indicates that the burst size is used for policing traffic.
        • bc—Committed (conform) burst size or burst size in bytes. The valid values range from 1000 to 256000000.
        • be—Indicates that the excess burst size is used for policing traffic.
        • peak-burst—Indicates that the peak-burst size is used for policing traffic.
        • be—Excess burst size or peak-burst size in bytes. The valid values range from 1000 to 256000000.
        • action—Action taken on a packet when it conforms, exceeds, or violates the interface bandwidth. The possible actions are shown in Table 1.
        police [cir | rate] percent % [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action

        Example:

        Switch(config-pmap-c)# police cir percent 10 bc 200000 be 400000 conform-action transmit exceed-action set-dscp-transmit 25 violate-action drop
        Configures traffic policing on the basis of a percentage of bandwidth available on an interface, where:
        • cir—Indicates that the committed information rate (CIR) is used for policing traffic.
        • rate—Indicates that the police rate is used for policing traffic.
        • percent—Indicates that a percentage of bandwidth is used for calculating CIR or rate.
        • %— CIR or rate bandwidth percentage. The valid values range from 1 to 100.
        • bc—Indicates that the committed (conform) burst size is used for policing traffic.
        • burst—Indicates that the burst size is used for policing traffic.
        • bc—Committed (conform) burst size or burst size in mill-seconds or micro-seconds.
        • be—Indicates that the excess burst size is used for policing traffic.
        • peak-burst—Indicates that the peak-burst size is used for policing traffic.
        • be—Excess burst size or peak-burst size in mill-seconds or micro-seconds.
        • action—Action taken on a packet when it conforms, exceeds, or violates the interface bandwidth. The possible actions are shown in Table 1.
        police [cir | rate] bps-value [bc | burst] bc [pir | peak-rate] pir [be | peak-burst] be conform-action action exceed-action action violate-action action

        Example:

        Switch(config-pmap-c)# police cir 500000000 bc 200000 pir 510000000 be 400000 conform-action transmit exceed-action set-dscp-transmit 50 violate-action drop
        Configures traffic policing using two rates (CIR and PIR) where:
        • cir—Indicates that the committed information rate (CIR) is used for policing traffic.
        • rate—Indicates that the police rate is used for policing traffic.
        • bps value—Average rate in bits per second. The valid values range from 8000 to 10000000000
        • bc—Indicates that the committed (conform) burst size is used for policing traffic.
        • burst—Indicates that the burst size is used for policing traffic.
        • bc—Committed (conform) burst size or burst size in bytes. The valid values range from 1000 to 256000000.
        • pir— Indicates that the peak information rate (PIR) is used for policing traffic.
        • peak-rate— Indicates that the peak rate is used for policing traffic.
        • pir—Peak information rate or peak rate in bits per second. The valid values range from 8000 to 10000000000
        • be—Indicates that the excess burst size is used for policing traffic.
        • peak-burst—Indicates that the peak-burst size is used for policing traffic.
        • be—Excess burst size or peak-burst size in bytes. The valid values range from 1000 to 256000000.
        • action—Action taken on a packet when it conforms, exceeds, or violates the interface bandwidth. The possible actions are shown in Table 1.

        Attaching or Removing a Traffic Policy from the Target

        Before a traffic policy can be enabled for a class of traffic, it must be configured on a target. Use the service-policy {input | output} configuration command to attach a traffic policy to a target and to specify the direction in which the policy should be applied (either on packets entering/ingressing the target or packets exiting/egressing the target). Only one traffic policy can be applied to an interface in a given direction. Use the no form of the command, that is, no service-policy {input | output} policy-map-name to detach a traffic policy from a target.

        Before You Begin

        Complete any one of the following tasks:

        SUMMARY STEPS

          1.    enable

          2.    configure terminal

          3.    interface type slot/port

          4.    service instance id ethernet

          5.    service-policy {input | output} policy-map-name

          6.    no service-policy {input | output} policy-map-name

          7.    end


        DETAILED STEPS
           Command or ActionPurpose
          Step 1enable


          Example:
          Switch> enable
           

          Enables privileged EXEC mode.

          • Enter your password if prompted.
           
          Step 2configure terminal


          Example:
          Switch# configure terminal
           

          Enters global configuration mode.

           
          Step 3interface type slot/port


          Example:
          Switch(config)# interface TenGigabitEthernet 0/45
           

          Configures an interface type and enters the interface configuration mode.

          • interface-type—Interface type
          • interface-number—Interface number.
           
          Step 4service instance id ethernet


          Example:
          Switch(config-if)# service instance 100  ethernet
           

          Enters the service instance mode.

          • id—Service instance ID.
           
          Step 5service-policy {input | output} policy-map-name


          Example:
          Switch(config-if-srv-instance)# service-policy input policy1
           

          Attaches a policy map to a target.

          • Enter either the input or output keyword and the policy map name.
          • policy-map-name—Name of the policy map.
           
          Step 6no service-policy {input | output} policy-map-name


          Example:
          Switch(config-if-srv-instance)# no  service-policy input policy1
           

          Removes the policy map from the target.

          • Enter either the input or output keyword and the policy map name.
           
          Step 7end


          Example:
          Switch(config-if-srv-instance)# end
           

          Exits the service instance mode.

           

          Configuring Ingress Marking

          Before You Begin

          Complete the following task:

          Configuring Ingress Policing


          Note

          Marking of the Layer 2 CoS bit for VPWS traffic is not supported.

          SUMMARY STEPS

            1.    enable

            2.    configure terminal

            3.    policy-map policy-map-name

            4.    class {class-name | class-default}

            5.    set ip precedence ip precedence value

            6.    end


          DETAILED STEPS
             Command or ActionPurpose
            Step 1enable


            Example:
            Switch> enable
             

            Enables privileged EXEC mode.

            • Enter your password if prompted.
             
            Step 2configure terminal


            Example:
            Switch# configure terminal
             

            Enters global configuration mode.

             
            Step 3policy-map policy-map-name


            Example:
            Switch(config)# policy-map policy1
             
            Creates or specifies the name of the traffic policy and enters the policy-map configuration mode.
            • policy-map-name— Policy map name. This is the name of the policy map and can have a maximum of 40 alphanumeric characters.
             
            Step 4 class {class-name | class-default}


            Example:
            Switch(config-pmap)# class class1
             
            Specifies the name of a traffic class to which the policy applies and enters the policy-map class configuration mode.
            • Enter the previously configured class-map name.
              • class-name—User-defined class name to which the policy applies.
              • class-default—Specifies that the policy applies to the default traffic class.
            Note   

            This step associates the traffic class with the traffic policy.

             
            Step 5 set ip precedence ip precedence value


            Example:
            Switch(config-pmap-c)# set ip precedence 2
             
            Marks the precedence value in the IP header with a value between 0 to 7.
            • ip precedence value— IP precedence value.
            Note   

            The set ip precedence command is just an example of one of the marking commands that can be used. For a list of other marking commands, see Table 1.

             
            Step 6end


            Example:
            Switch(config-pmap)# end
             

            Exits policy-map configuration mode and returns to privileged EXEC mode.

             

            The table below provides the traffic marking commands supported at Ingress.

            Table 6 Traffic Marking Commands
            Command Description
            set ip precedence ip-precedence-value

            Example:

            Switch(config-pmap-c)# set ip precedence 2
            Marks the precedence value in the IP header with a value between 0 to 7.
            • ip precedence value—IP precedence value.
            set cos cos-value

            Example:

            Switch(config-pmap-c)# set cos 2
            Marks the CoS value between 0 to 7 in an 802.1Q tagged frame
            • cos-value—CoS value.
            set ip dscp ip-dscp-value

            Example:

            Switch(config-pmap-c)# set ip dscp 22
            Marks the IP DSCP in the ToS byte with a value between 0 to 63.
            • ip-dscp-value—IP DSCP value.
            set qos group qos-group-value

            Example:

            Switch(config-pmap-c)# set qos group 3
            Marks a QoS group identifier (ID) with a value between 0 to 7 that can be used later to classify packets.
            • qos-group-value—QoS group value.

            Configuring Ingress Re-Marking

            To configure ingress re-marking on the device, complete the following steps:
            Before You Begin

            Complete the following task:

            Configuring Ingress Policing


            Note

            You cannot apply remarking for precedence and DSCP together.

            SUMMARY STEPS

              1.    enable

              2.    configure terminal

              3.    policy-map policy-map-name

              4.    class {class-name | class-default}

              5.    set ip precedence ip precedence value

              6.    police cir percent value

              7.    Confirm-action set-cos-transmit value

              8.    end


            DETAILED STEPS
               Command or ActionPurpose
              Step 1enable


              Example:
              Switch> enable
               

              Enables privileged EXEC mode.

              • Enter your password if prompted.
               
              Step 2configure terminal


              Example:
              Switch# configure terminal
               

              Enters global configuration mode.

               
              Step 3policy-map policy-map-name


              Example:
              Switch(config)# policy-map policy1
               
              Creates or specifies the name of the traffic policy and enters the policy-map configuration mode.
              • policy-map-name— Policy map name. This is the name of the policy map and can have a maximum of 40 alphanumeric characters.
               
              Step 4 class {class-name | class-default}


              Example:
              Switch(config-pmap)# class class1
               
              Specifies the name of a traffic class to which the policy applies and enters the policy-map class configuration mode.
              • Enter the previously configured class-map name.
                • class-name—User-defined class name to which the policy applies.
                • class-default—Specifies that the policy applies to the default traffic class.
              Note   

              This step associates the traffic class with the traffic policy.

               
              Step 5 set ip precedence ip precedence value


              Example:
              Switch(config-pmap-c)# set ip precedence 2
               
              Marks the precedence value in the IP header with a value between 0 to 7.
              • ip precedence value— IP precedence value.
              Note   

              The set ip precedence command is just an example of one of the marking commands that can be used. For a list of other marking commands, see Table 1.

               
              Step 6police cir percent value


              Example:
              Switch(config-pmap-c)# police cir percent 2


              Example:
               Switch(config-pmap-c)# police 100m
               

              Specifies the bandwidth to confirm traffic at ingress.

               
              Step 7Confirm-action set-cos-transmit value


              Example:
              Switch(config-pmap-c-police)# Confirm-action set-cos-transmit 4
               

              Remarks the cos value in the vlan header with a value between 0 to 7.

               
              Step 8end


              Example:
              Switch(config-pmap)# end
               

              Exits policy-map configuration mode and returns to privileged EXEC mode.

               

              The table below provides the traffic marking commands supported at Ingress:

              Table 7 Traffic Marking Commands
              Command Description
              set-prec-transmit ip-precedence-value

              Example:

              Switch(config-pmap-c)# set-prec-transmit 2
              Marks the precedence value in the IP header with a value between 0 to 7.
              • ip precedence value—IP precedence value.
              set-cos-transmit cos-value

              Example:

              Switch(config-pmap-c)# set-cos-transmit 2
              Marks the CoS value between 0 to 7 in an 802.1Q tagged frame
              • cos-value—CoS value.
              set-dscp-transmit ip-dscp-value

              Example:

              Switch(config-pmap-c)# set-dscp-transmit 22
              Marks the IP DSCP in the ToS byte with a value between 0 to 63.
              • ip-dscp-value—IP DSCP value.
              set-qos-transmit qos-group-value

              Example:

              Switch(config-pmap-c)# set-qos-transmit 3
              Marks a QoS group identifier (ID) with a value between 0 to 6 that can be used later to classify packets.
              • qos-group-value—QoS group value.

              Configuring Egress Classification

              To configure egress classification on the device, complete the following steps:

              Before You Begin

              Note
              • Only one match filter is supported for each class-map.
              • Only QoS-group based matching is supported for user-defined classes.
              • Match based on QoS-group 3 and QoS-group 7 is used only for low latency queuing across the system.
              • Match based on the class-default in the output policy suggests that matching is based on the QoS-group 0 and not the class where traffic, which does not match any selection criteria in the configured class maps, is directed.
              SUMMARY STEPS

                1.    enable

                2.    configure terminal

                3.    class-map [match-any] class-map-name

                4.    match qos-group qos-group-number

                5.    end


              DETAILED STEPS
                 Command or ActionPurpose
                Step 1enable


                Example:
                Switch> enable
                 

                Enables privileged EXEC mode.

                • Enter your password if prompted.
                 
                Step 2configure terminal


                Example:
                Switch# configure terminal
                 

                Enters global configuration mode.

                 
                Step 3class-map [match-any] class-map-name


                Example:
                Switch(config)# class-map match-any class1
                 
                Creates a class to be used with a class map and enters the class-map configuration mode. The class map is used for matching packets to the specified class.
                • class-map-name—Class name. This is the name of the class map and can have a maximum of 40 alphanumeric characters.

                The match-any keyword specifies that one of the match criteria must be met. Use this keyword only if you have to specify more than one match command.

                 
                Step 4match qos-group qos-group-number


                Example:
                Switch(config-cmap)# match qos-group 2
                 
                Matches a packet on the basis of traffic class represented by the qos-group.
                • qos-group-number—QoS-group value. The value can range from 0 to 7.
                 
                Step 5end


                Example:
                Switch(config-cmap)# end
                 

                Exits class-map configuration mode and returns to privileged EXEC mode.

                 

                Configuring Egress LLQ

                To configure egress LLQ on the device, complete the following steps:
                Before You Begin

                Complete step 1 to step 5 of Configuring Ingress Policing


                Note
                • The priority command enables the rate-limit option to ensure that a particular rate is not exceeded. However, in the Cisco ME 2600X system, egress rate limiting is achieved using shapers that can cause additional delays. Therefore, it is advised to ensure that for LLQ traffic, rate limiting is done at ingress, and the rates specified at egress are just placeholders that are never exceeded. Exceeding the rate limit at egress would mean increased latencies for LLQ traffic.
                • The priority command is supported only under class-map with qos-group 3 or 7 as the match criteria and multicast-priority class.
                SUMMARY STEPS

                  1.    enable

                  2.    configure terminal

                  3.    policy map policy-map-name

                  4.    class {class-name | class-default}

                  5.    priority bandwidth value

                  6.    end


                DETAILED STEPS
                   Command or ActionPurpose
                  Step 1enable


                  Example:
                  Switch> enable
                   

                  Enables privileged EXEC mode.

                  • Enter your password if prompted.
                   
                  Step 2configure terminal


                  Example:
                  Switch# configure terminal
                   

                  Enters global configuration mode.

                   
                  Step 3policy map policy-map-name


                  Example:
                  Switch(config)# policy-map policy1
                   

                  Creates or modifies a traffic policy and enters the policy-map configuration mode. The policy-map-name specifies the name of the traffic policy, which can have a maximum of 40 alphanumeric characters.

                   
                  Step 4 class {class-name | class-default}


                  Example:
                  Switch(config-pmap)# class class_qos_1
                   

                  Specifies the name of the traffic class to which this policy applies and enters the policy-map class configuration mode, where:

                  • class-name—Name of a predefined class included in the service policy.
                  • class-default—Specifies that the policy applies to the default traffic class.
                   
                  Step 5 priority bandwidth value


                  Example:
                  Switch(config-pmap-c)# priority 10000
                   

                  Provides strict priority to a class of traffic belonging to the policy-map. Specifies the maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. The bandwidth value is in kbps, and can range from 1 to 10000000.

                  Note   

                  The priority bandwidth value command is just an example of one of the priority commands that can be used. For a list of other priority commands, see Table 1.

                   
                  Step 6end


                  Example:
                  Switch(config-pmap-c)# end
                   

                  Exits the configuration mode and returns to privileged EXEC mode.

                   

                  The table below lists the priority commands:

                  Table 8 Priority (LLQ) Commands
                  Command Description
                  priority bandwidth value

                  Example:

                  Switch(config-pmap-c)# priority 10000

                  Provides strict priority to a class of traffic belonging to the policy-map. Specifies the maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. The bandwidth value is in kbps, and can range from 1 to 10000000.

                  priority

                  Example:

                  Switch(config-pmap-c)# priority

                  This command provides low-latency queuing without specifying the rate limiter.
                  priority percent x%

                  Example:

                  Switch(config-pmap-c)# priority 10%

                  Indicates that the rate of traffic that is given low latency handling is x% of the parent interface bandwidth or x% parent class CIR if policy not applied on an interface. The percentage can be a number from 1 to 100.

                  Configuring Egress Bandwidth

                  To configure egress bandwidth on the device, complete the following steps:
                  Before You Begin

                  Complete step 1 to step 5 of Configuring Ingress Policing


                  Note
                  • Bandwidth action is not supported on classes with qos-group 3 or 7 as the match criteria.
                  • The bandwidth command cannot be used in combination with BRR or BRP in a class-map or a policy-map.
                  • The system does not validate the total CIR configured on all the targets for various congestion points. Therefore, it should be ensured that the total CIR configured does not exceed the total bandwidth available.
                    • Total CIR configured for a 1 Gbps interface should not exceed 1 Gbps, which includes CIR in the policy applied on the interface and services on that interface.
                    • Total CIR configured for a 10 Gbps interface should not exceed 10 Gbps, which includes CIR in the policy applied on the interface and services on that interface.
                    • Total CIR for all the targets on a Cisco ME 2600X shelf should not exceed 9.882 Gbps; this is the least bandwidth for a Cisco ME 2600X shelf in a scenario where only one of the interconnects for a Cisco ME 2600X shelf is functional.
                  SUMMARY STEPS

                    1.    enable

                    2.    configure terminal

                    3.    policy map policy-map-name

                    4.    class {class-name | class-default}

                    5.    bandwidth bandwidth value

                    6.    end


                  DETAILED STEPS
                     Command or ActionPurpose
                    Step 1enable


                    Example:
                    Switch> enable
                     

                    Enables privileged EXEC mode.

                    • Enter your password if prompted.
                     
                    Step 2configure terminal


                    Example:
                    Switch# configure terminal
                     

                    Enters global configuration mode.

                     
                    Step 3policy map policy-map-name


                    Example:
                    Switch(config)# policy-map policy1
                     

                    Creates or modifies a traffic policy and enters the policy-map configuration mode. The policy-map-name specifies the name of the traffic policy that can have a maximum of 40 alphanumeric characters.

                     
                    Step 4 class {class-name | class-default}


                    Example:
                    Switch(config)# class c3
                     

                    Specifies the name of the traffic class to which this policy applies and enters the policy-map class configuration mode, where:

                    • class-name—User-defined class name to which the policy applies.
                    • class-default—Specifies that the policy applies to the default traffic class.
                     
                    Step 5bandwidth bandwidth value


                    Example:
                    Switch(config-pmap-c)# bandwidth 10000
                     
                    Specifies the amount of bandwidth in kbps to be assigned to the class. Implies that the class where this is applied is given a minimum bandwidth guarantee of bandwidth value in kbps. The amount of bandwidth configured should be large enough to also accommodate Layer 2 overheads.
                    Note   

                    The bandwidth bandwidth value command is just an example of one of the bandwidth commands that can be used. For a list of other bandwidth commands, see Table 1.

                     
                    Step 6end


                    Example:
                    Switch(config-pmap-c)# end
                     

                    Exits the configuration mode and returns to privileged EXEC mode.

                     

                    The table below lists the bandwidth commands:

                    Table 9 Bandwidth Commands
                    Command Description
                    bandwidth bandwidth-value

                    Example:

                    Switch(config-pmap-c)# bandwidth 10000

                    Specifies the amount of bandwidth in kbps to be assigned to the class. Implies that the class where this is applied is given a minimum bandwidth guarantee of bandwidth-value kbps. The amount of bandwidth configured should be large enough to also accommodate Layer 2 overhead.
                    bandwidth percent %

                    Example:

                    Switch(config-pmap-c)# bandwidth percent 20

                    Specifies the amount of bandwidth, in percentage from the available bandwidth, to be assigned to the class. The value ranges from 1 to 100.

                    Configuring Egress Shaping

                    To configure shaping at the egress on the device, complete the following steps:
                    Before You Begin

                    Complete step 1 to step 5 of Configuring Ingress Policing.


                    Note
                    • The shaping command is not supported on classes with qos-group 3 or 7 as the match criteria.
                    • Shape on a traffic class would mean buffering of traffic in the system memory, which could result in increased latencies for these streams.
                    SUMMARY STEPS

                      1.    enable

                      2.    configure terminal

                      3.    class-map [match-any] class-map-name

                      4.    policy map policy-map-name

                      5.    class class-name

                      6.    shape average cir value

                      7.    end


                    DETAILED STEPS
                       Command or ActionPurpose
                      Step 1enable


                      Example:
                      Switch> enable
                       

                      Enables privileged EXEC mode.

                      • Enter your password if prompted.
                       
                      Step 2configure terminal


                      Example:
                      Switch# configure terminal
                       

                      Enters global configuration mode.

                       
                      Step 3class-map [match-any] class-map-name


                      Example:
                      Switch(config)# class-map class-interface-all
                       

                      Creates a class map to be used for matching packets to a class.

                       
                      Step 4policy map policy-map-name


                      Example:
                      Switch(config)# policy-map test2
                       

                      policy-map-name—Name of the policy-map to configure.

                       
                      Step 5class class-name


                      Example:
                      Switch(config-pmap)# class classtest
                       

                      class-name—Name of a predefined class included in the service policy.

                       
                      Step 6shape average cir value


                      Example:
                      Switch(config-pmap-c)# shape average 10000000
                       

                      cir value—Average rate traffic shaping. The committed information rate (CIR) value ranges from 8000 to 10000000000 bps.

                      Note   

                      The shape average cir value command is just an example of one of the shape commands that can be used. For a list of other shape commands, see Table 1.

                       
                      Step 7end


                      Example:
                      Switch(config-pmap-c)# end
                       

                      Exits the configuration mode and returns to privileged EXEC mode.

                       

                      Table 1 provides the traffic shaping commands:

                      Table 10 Traffic Shaping Commands
                      Command Description
                      shape average percent %

                      Example:

                      Switch(config-pmap-c)# shape average percent 20
                      Shapes a class to a percent of visible bandwidth.
                      • %—Percentage. The value should range from 1 to 100.
                      shape average cir value

                      Example:

                      Switch(config-pmap-c)# shape average 10000000
                      		 Specifies the average rate traffic shaping.
                      • cir value—CIR value in bps. The committed information rate (CIR) value ranges from 8000 to 10000000000 bps.

                      Configuring Egress Bandwidth Remaining Ratio or Bandwidth Remaining Percent

                      BRR is implemented on logical interfaces using hierarchical policy-maps.

                      To configure QoS egress BRR or BRP on the device, complete the following steps:

                      Before You Begin

                      Complete step 1 to step 5 of Configuring Ingress Policing


                      Note
                      • The BRR and BRP commands are not supported in combination with the bandwidth action in a class-map or a policy-map.
                      • The BRR and BRP command are not supported on classes with qos-group 3 or 7 as the match criteria.
                      SUMMARY STEPS

                        1.    enable

                        2.    configure terminal

                        3.    policy map policy-map-name

                        4.    class {class-name | class-default}

                        5.    bandwidth remaining ratio ratio

                        6.    end


                      DETAILED STEPS
                         Command or ActionPurpose
                        Step 1enable


                        Example:
                        Switch> enable
                         

                        Enables privileged EXEC mode.

                        • Enter your password if prompted.
                         
                        Step 2configure terminal


                        Example:
                        Switch# configure terminal
                         

                        Enters global configuration mode.

                         
                        Step 3policy map policy-map-name


                        Example:
                        Switch(config)# policy-map policy1
                         

                        Creates or modifies a traffic policy and enters the policy-map configuration mode. The policy-map-name specifies the name of the traffic policy, which can have a maximum of 40 alphanumeric characters.

                         
                        Step 4 class {class-name | class-default}


                        Example:
                        Switch(config-pmap)# class c3
                         

                        Specifies the name of the predefined traffic class to which this policy applies and enters the policy-map class configuration mode, where:

                        • class-name—User-defined class name to which the policy applies.
                        • class-default—Specifies that the policy applies to the default traffic class.
                         
                        Step 5bandwidth remaining ratio ratio


                        Example:
                        Switch(config-pmap-c)# bandwidth remaining ratio 2
                         

                        Specifies a bandwidth-remaining ratio for class-level or subinterface-level queues to be used during congestion to determine the amount of excess bandwidth (unused by priority traffic) to allocate to non priority queues. The value should be between 1 to 127.

                        Note   

                        The bandwidth remaining percent x% can be used instead of the bandwidth remaining ratio ratio command to configure BRP. For details on bandwidth remaining percent command, see Table 1.

                         
                        Step 6end


                        Example:
                        Switch(config-pmap-c)# end
                         

                        Exits the configuration mode and returns to privileged EXEC mode.

                         

                        The table below provides the bandwidth remaining ratio or percent commands:

                        Table 11 Bandwidth Remaining Ratio and Bandwidth Remaining Percent Commands
                        Command Description
                        bandwidth remaining percent x%

                        Example:

                        Switch(config-pmap-c)# bandwidth remaining percent 20

                        Specifies that the class where the command is specified should be given x% of the excess bandwidth, where excess bandwidth is the bandwidth in excess of all the minimum bandwidth guarantees of all the classes at the same level. The value should range from 1 to 100.
                        bandwidth remaining ratio ratio

                        Example:

                        Switch(config-pmap-c)# bandwidth remaining ratio 2

                        Specifies a bandwidth-remaining ratio for class-level or subinterface-level queues to be used during congestion to determine the amount of excess bandwidth (unused by priority traffic) to allocate to non priority queues. The value should be between 1 to 127.

                        Troubleshooting Tips

                        The commands listed in this section can be used to see the policies and class-maps that are configured and applied on the Cisco ME 2600X .

                        Use the following commands to display configured policies and class-maps:
                        • Show policy-map [policy-map-name]
                        • Show class-map [class-map-name]

                        Configuration Examples for QoS

                        Configuring Ingress Classification

                        The following example shows how to configure a class-map named ipp5, and enter a match statement for IP precedence 5:

                        Switch> enable
Switch# configure terminal
Switch(config)# class-map ipp5
Switch(config-cmap)# match ip precedence 5
Switch(config-cmap)# exit

                        The following example shows how to configure a class-map on multiple match statements:

                        Switch> enable
Switch# configure terminal
Switch(config)# class-map match-any IPP
Switch(config-cmap)# match ip precedence 3
Switch(config-cmap)# match ip precedence 4
Switch(config-cmap)# exit

                        The following example shows how to a configure a class-map using match-all and match-any keywords:

                        Switch> enable
Switch# configure terminal
Switch(config)# class-map match-any class1
Switch(config-cmap)# match vlan 100 200 400-500
Switch(config-cmap)# match cos 1
Switch(config-cmap)# exit
Switch(config)# class-map match-any class2
Switch(config-cmap)# match vlan 1000 1100-1120
Switch(config-cmap)# match cos 3
Switch(config-cmap)# exit

                        The match-all criteria with multiple VLANs and CoS marking gets translated to a combination of match criteria. Therefore matching is based on the following incoming packet:

                        VLAN 1000 AND COS 3
VLAN 1100-1200 AND COS 3

                        The match-any criteria gets translated to individual match criteria. Therefore matching is based on VLAN 100, VLAN 200, VLAN 400-500, or COS 1.

                        The following example shows how to configure a hierarchical ingress policy:

                        Switch> enable
Switch# configure terminal
Switch(config)# class-map match-any childOR
Switch(config-cmap)# match cos 5
Switch(config)# policy-map testchildOR
Switch(config-pmap)# class childOR
Switch(config-pmap-c)# police cir percent 10
Switch(config)# policy-map parentOR
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police rate 500000
Switch(config-pmap-c)# service-policy testchildOR
Switch(config-pmap-c)# exit

                        Configuring Ingress Policing

                        The following example shows how to configure policing actions:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map ABC
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police 10000000 8000 8000
Switch(config-pmap-c-police)# conform-action set-cos-transmit 2
Switch(config-pmap-c-police)# exceed-action set-cos-transmit 1
Switch(config-pmap-c-police)# end

                        The following example shows how to configure a single rate 2-color policer:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map 1r2c
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police 2000000
Switch(config-pmap-c-police)# conform-action transmit
Switch(config-pmap-c-police)# exceed-action drop
Switch(config-pmap-c-police)# end

                        The following example shows how to configure a single rate, 2-color policer with percent:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map 1r2c_percent
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir percent 20
Switch(config-pmap-c-police)# conform-action set-cos-transmit 0
Switch(config-pmap-c-police)# exceed-action drop
Switch(config-pmap-c-police)# end

                        The following example shows how to configure a dual rate, 3-color policer:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map 2r3c
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir 2000000 pir 3000000
Switch(config-pmap-c-police)# conform-action set-prec-transmit 3
Switch(config-pmap-c-police)# exceed-action set-prec-transmit 2
Switch(config-pmap-c-police)# violate-action set-prec-transmit 1
Switch(config-pmap-c-police)# end

                        The following example shows how to configure a dual rate, 3-color policer with percent:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map 2r3c_percent
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir percent 10 pir percent 20
Switch(config-pmap-c-police)# conform-action transmit
Switch(config-pmap-c-police)# xceed-action set-cos-transmit 0
Switch(config-pmap-c-police)# violate-action drop
Switch(config-pmap-c-police)# end

                        The following example shows how to configure a single rate, 2-color policer in class-default and a child policy:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map police5
Switch(config-pmap)# class test18
Switch(config-pmap-c)# service policy child-level
Switch(config-pmap-c)# police cir 64000 50
Switch(config-pmap-c-police)# end

                        The following example shows how to configure a dual rate, 3-color policer configuration in a class and policy-map:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map test
Switch(config-pmap)# class cos2
Switch(config-pmap-c)# police 1000000 pir 2000000 conform-action set-cos-transmit 3 exceed-action set-cos-transmit 1 violate-action drop

                        The following example shows how to configure a dual rate, 3-color policer in class-default with a CIR of 64 Kbps, and PIR doubled the CIR rate, a conform action of transmit, and an exceed action mark dscp af 11:

                        Switch> enable
Switch# configure terminal
Switch(config)# olicy-map qos_test
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir 64000 bc 2000 pir 128000 be 2000 conform-action transmit exceed-action set-dscp-transmit af11 violate-action set-dscp-transmit cs1

                        The following example shows how to configure a dual rate, 3-color policer in class-default:

                        Switch> enable
Switch# configure terminal
Switch(config)# olicy-map qos_test
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir 64000 bc 2000 pir 128000 be 2000 conform-action transmit exceed-action set-dscp-transmit af11 violate-action set-dscp- transmit cs1

                        Attaching or Removing a QoS Traffic Policy for a Target

                        The following example shows how to attach a traffic policy to a target:

                        Switch> enable
Switch# configure terminal
Switch(config)# interface TenGigabitEthernet 0/45
Switch(config-if)# service instance 100 ethernet
Switch(config-if-srv-instance)# service-policy input policy1
Switch(config-if-srv-instance)# end

                        The following example shows how to remove a traffic policy from a target:

                        Switch> enable
Switch# configure terminal
Switch(config)# interface TenGigabitEthernet 0/45
Switch(config-if)# service instance 100 ethernet
Switch(config-if-srv-instance)# no service-policy input policy1
Switch(config-if-srv-instance)# end

                        Configuring Ingress Marking

                        The following example 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. This example configures marking to set the IP precedence value:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip precedence 1

                        The following example shows how to configure marking to set the CoS value:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map test
Switch(config-pmap)# lass test
Switch(config-pmap-c)# set cos 1

                        Configuring Egress Classification

                        The following example shows how to create a class map:

                        Switch> enable
Switch# configure terminal
Switch(config)# class-map c1
Switch(config-cmap)# match qos-group 1

                        The following example shows how to configure priority queue at the egress:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map Test1
Switch(config-pmap)# class test
Switch(config-pmap-c)# priority 10000

                        Configuring Egress Bandwidth

                        The following example shows how to configure minimum bandwidth guarantee at the egress:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map Test
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# bandwidth 10000
Switch(config-pmap-c)# exit

                        Configuring Egress Shaping

                        The following example shows how to shape traffic on a main interface; traffic leaving interface gi36/1 is shaped at the rate of 10 Mb/s:

                        Switch> enable
Switch# configure terminal
Switch(config)# class-map class-interface-all
Switch(config-cmap)# match qos-group 1
Switch(config-cmap)# exit
Switch(config)# policy-map dts-interface-all-action
Switch(config-pmap)# class class-interface-all
Switch(config-pmap-c)# shape average 10000000
Switch(config-pmap-c)# exit
Switch(config)# interface gi36/1
Switch(config-if)# service-policy output dts-interface-all-action

                        Configuring Egress Bandwidth Remaining Ratio

                        The following example shows how to configure bandwidth remaining ratio at the egress:

                        Switch> enable
Switch# configure terminal
Switch(config)# policy-map BRR
Switch(config-pmap)# class Test1
Switch(config-pmap-c)# bandwidth remaining ratio 10
Switch(config-pmap-c)# exit
Switch(config-pmap)# class Test2
Switch(config-pmap-c)# bandwidth remaining ratio 20
Switch(config-pmap-c)# exit
Switch(config-pmap)# class Test3
Switch(config-pmap-c)# bandwidth remaining ratio 30
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# bandwidth remaining ratio 40

                        Verifying the QoS Configuration

                        Use the following show commands to verify the QoS configuration:
                        • show class-map
                        • show class-map class-map-name
                        • show policy-map
                        • show policy-map policy-map-name
                        • show policy-map policy-map-name class class-name
                        • show run class-map
                        • show policy-map BRR
                        • show policy-map interface interface type slot/port
                        • show policy-map interface interface type slot/port service instance number

                        Class Map

                        Use the following command to show class-map information for a specific class map:

                        Switch# show class-map ipp5
                        class Map match-any ipp5 (id 1)
match ip precedence 5

                        Use the following command to show class-map information for a specific class map using the show run class-map command:

                        Switch# show run class-map
                        Building configuration...
Current configuration : 275 bytes
!
class-map match-any EgressClassmap
match qos-group 3
class-map match-any IngressClassMap
match cos 1
end

                        Policy Map

                        Use the following command to show policy map information:

                        Switch# show policy-map
                        policy-map testchildOR
class childOR
police 100000000
policy-map parentOR
class class-default
police 500000000
service-policy testchildOR

                        Use the following command to show information for a specific policy map:

                        Switch# show policy-map ABC
                        Policy Map ABC
class class-default
police cir 10000000 bc 8000 be 8000
conform-action set-cos-transmit 2
exceed-action set-cos-transmit 1

                        Use the following command to verify the bandwidth remaining ratio at the egress:

                        Switch# show policy-map BRR
                        Building configuration...
Current configuration : 209 bytes
!
policy-map BRR
class Test1
bandwidth remaining ratio 10
class Test2
bandwidth remaining ratio 20
class Test3
bandwidth remaining ratio 30
class class-default
bandwidth remaining ratio 40
!
end

                        Additional References for QoS

                        The following sections provide references related to the QoS feature.

                        Related Documents

                        Related Topic Document Title

                        Cisco IOS commands

                        Cisco IOS Master Commands List, All Releases

                        QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples

                        Cisco IOS Quality of Service Solutions Command Reference

                        Technical Assistance

                        Description Link

                        The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

                        To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

                        Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

                        		 http:/​/​www.cisco.com/​cisco/​web/​support/​index.html
                        Quality of Service

                        Contents

                        Quality of Service

                        This chapter describes the Quality of Service for Cisco ME 2600X and procedures to configure Quality of Service.

                        Quality of Service

                        Quality of Service (QoS) refers to the ability of a network to provide improved services to selected network traffic over various underlying technologies including Ethernet and IEEE 802.1 networks.

                        Finding Feature Information

                        Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Toolkit and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

                        Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http:/​/​www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

                        Prerequisites for QoS

                        The following two components are necessary to deliver QoS across a heterogeneous network:
                        • QoS within a single network element, which includes queuing, scheduling, and traffic shaping features.
                        • QoS policing and management functions to control and administer end-to-end traffic across a network.

                        Restrictions for QoS

                        The following are the general restrictions for the QoS feature:

                        • Policing is not supported at egress level.
                        • Only 0 to 6 queues can be used at egress. QoS-Group 3 is used for LLQ (Priority) traffic at egress.
                        • Remarking does not happen if the outer or inner VLAN is configured with ANY, LIST, or RANGE.
                        • COS marking fails with encapsulation VLAN range and match VLAN range.
                        • The police cir command is not supported at the parent level in the hierarchical quality of service (HQoS). HQoS supports only the police rate command at parent level.
                        • Parent level should always be class-default in HQoS.
                        • An ingress policer does not support more than 8 classes.
                        • An egress policer does not support more than 7 classes.

                        Information About QoS

                        The QoS mechanism has three basic steps. It classifies types of traffic, specifies what action to take against a type of traffic, and specifies where the action should take place. The following sections explain how the Cisco ME 2600X accomplishes these steps.

                        Classification Mechanism for IP and Ethernet

                        For any QoS service to be applied to data, there must be a way to classify an IP packet or an Ethernet frame. When identified, a specific priority can be assigned to each individual IP packet or Ethernet frame. The IP Precedence field or the IP Differentiated Services Code Point (DSCP) field can be used to classify IP packets, and the Ethernet class of service (IEEE 802.1p defined class of service [CoS]) can be used for classifying Ethernet frames. IP precedence, IP DSCP, and Ethernet CoS are further described in the following sections.

                        IP Precedence

                        Use of IP precedence enables you to specify the class of service (CoS) for a packet using the three precedence bits in the type of service (ToS) field of the IP version 4 (IPv4) header. By default, each precedence corresponds to a name. These names, which continue to evolve, are defined in RFC 791.
                        Number Name
                        0 routine
                        1 priority
                        2 immediate
                        3 flash
                        4 flash-override
                        5 critical
                        6 internet
                        7 networks

                        Note

                        IP precedence bit settings 6 and 7 are reserved for network control information, such as routing updates.

                        IP Differentiated Services Code Point

                        IP DSCP uses the six bits in the IPv4 header to specify class of service for each IP packet (IETF RFC 2474). The DSCP field classifies packets into any of the 64 possible classes. On the network edge, the IP DSCP is assigned by the client device or the switch, so that each subsequent network element can provide services based on the determined policy or the SLA.

                        IP Precedence and DSCP is illustrated in this figure.
                        Figure 1. IP Precedence and DSCP

                        Ethernet CoS

                        The Ethernet CoS refers to the three bits within a four byte IEEE 802.1Q (VLAN) header used to indicate the priority of the Ethernet frame as it passes through a switched network. The CoS bits in the IEEE 802.1Q header are commonly referred to as the IEEE 802.1p bits. There are three CoS bits that provide eight classes, matching the IP precedence number. In many real-world networks, a packet might traverse both Layer 2 and Layer 3 domains. To maintain QoS across the network, the IP ToS can be mapped to the Ethernet CoS and vice versa. For example, in a linear or one-to-one mapping where each mechanism supports eight classes. Similarly, a set of DSCP values (64 classes) can be mapped into each of the eight individual Ethernet CoS values. An IEEE 802.1Q Ethernet frame, which consists of a 2-byte Ethertype and a 2-byte tag (IEEE 802.1Q tag) on the Ethernet protocol header is shown in this figure.
                        Figure 2. Ethernet Frame and the CoS Bit (IEEE 802.1p)

                        Advantages of QoS

                        Enabling QoS in the network has the following advantages:

                        • Control over resources—You can control resources like bandwidth that is being used.
                        • Tailored services—If you are a service provider, the control and visibility that QoS provides enable you to offer carefully tailored grades of service differentiation to your customers.
                        • Coexistence of mission-critical applications:
                          • Your WAN is used efficiently by mission-critical applications that are most important to your business.
                          • Bandwidth and minimum delays required by time-sensitive multimedia and voice applications are available.
                          • Other applications using the link get their fair service without interfering with mission-critical traffic.

                        Cisco ME 2600X QoS

                        The Cisco ME 2600X QoS classifies each packet in the network based on its Ethernet CoS, IP precedence, IP DSCP, or VLAN ID. After they are classified into class flows, further QoS functions can be applied to each packet as it traverses the Cisco ME 2600X.

                        The policing feature of the Cisco ME 2600X system ensures that the attached equipment does not submit more than a predefined amount of bandwidth (Rate Limiting) into the network. The policing feature can be used to enforce the committed information rate (CIR) and the peak information rate (PIR) available to a customer at an interface. The policing action is applied per classification.

                        The marking feature can set the Ethernet CoS, IP precedence, or IP DSCP bits when packets enter the Cisco ME 2600X. The marking feature operates on the outer IEEE 802.1p tag, IP precedence, or IP DSCP bits and provides a mechanism for tagging packets at the ingress. The subsequent network elements can provide a QoS based only the QoS indicator that the service provider has created.

                        The per-class queuing allows various queuing applications to support SLA. For example, allocation of committed information rate, ensuring low latencies and rate limiting traffic to down stream nodes based on the configuration, and also enabling fair access to excess network bandwidth. The Cisco ME 2600X uses a combination of Strict Priority Queuing (SPQ) and Weighted Round Robin (WRR) scheduling process to guarantee throughput and latency requirements and to provide fair access to excess bandwidth. The Cisco ME 2600X QoS flow is illustrated in this figure.
                        Figure 3. Cisco ME 2600X QoS flow

                        Ingress QoS Functions

                        Ingress QoS on the Cisco ME 2600X system involves classification, marking, and policing. The ingress card classifies the packets and assigns a traffic-class to it. The traffic-class is used for internal queuing and congestion management, as well as classification at the egress. At ingress, policy application is supported on multiple targets, which are:
                        • Ten Gigabit Ethernet (10 GE) and one Gigabit Ethernet (1 GE) interface
                        • Port-channel interface
                        • Port-channel member interface
                        • Service instance on 10 GE and 1 GE interfaces
                        • Service instance on port-channel

                        Ingress Classification

                        Classifying network traffic enables you to organize traffic into traffic classes or categories on the basis of whether the traffic matches specific criteria. Using the packet classification, you can partition network traffic into multiple priority levels or classes of service. Traffic is classified to determine whether it should be:

                        • Marked for further processing
                        • Policed to rate limit specific traffic types

                        The Cisco ME 2600X system supports ingress classification. The default class, named class-default, is the class to which any traffic that does not match any of the selection criteria in the configured class maps, is directed.

                        To configure ingress classification, see Configuring Ingress Classification.

                        Ingress Policing

                        Ingress policing ensures that an attached equipment does not submit more than a predefined amount of bandwidth (Rate Limiting) into the network. The policing feature can be used to enforce the committed information rate (CIR) and the peak information rate (PIR) available to a customer at an interface or a service instance on an interface. Policing enables to limit the data flow through the Cisco ME 2600X by dropping or marking down the QoS value according to the configuration.

                        The Cisco ME 2600X supports ingress policing. When policing is configured, traffic is placed in one of the following categories:

                        • Conform
                        • Exceed
                        • Violate

                        Within these three categories, users can decide the actions to be applied. For instance, packets that conform to the policy rate can be configured to be transmitted, packets that exceed the policy rate can be configured to be sent with a decreased priority, and packets that violate the policy rate can be configured to be dropped. If no actions are specified, the default conform-action is transmit, and default exceed-action or violate-action is drop.

                        The table below contains the list of policing actions supported at the ingress:

                        Table 1 Policing Actions
                        Action Purpose

                        transmit

                        Transmits the packet.

                        drop

                        Drops the packet.

                        set-cos-transmit

                        Sets the CoS value and transmits the packet.

                        set-dscp-transmit

                        Sets the IP DSCP value and transmit the packet.

                        set-precedence-transmit

                        Sets the IP precedence value and transmits the packet.

                        set-qos-transmit

                        Sets the QoS-group value and transmits the packet.

                        The policing features supported are:

                        • Individual actions
                        • Multiple actions
                        • Single rate, 2-color policer
                        • Single rate, 3-color policer
                        • Dual rate, 3-color policer
                        • Color blind mode
                        • Hierarchical policing (two levels)

                        To create a policy-map, see Configuring Ingress Policing.

                        To attach or remove a traffic policy from the interface, see Attaching or Removing a Traffic Policy from the Target.

                        Ingress Marking

                        Marking is a way to selectively modify QoS bits in a packet to identify traffic within the system and/or the network. The downstream devices in the network and the egress targets within the system can match the traffic based on the marking done at the ingress of the system. The Cisco ME 2600X supports ingress marking.

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

                        In most cases, the purpose of a packet mark is identification. After a packet is marked, downstream devices identify traffic based on the marking and categorize the traffic according to network needs. This categorization occurs when the match commands in the traffic class are configured to identify the packets by their marking (for example, match IP precedence, match IP DSCP, match CoS, and so on). The traffic policy using this traffic class can then set the appropriate QoS features for the marked traffic.

                        To configure ingress marking, see Configuring Ingress Marking.

                        Egress QoS Functions

                        For FTTH LAG QoS, service policy application can only happen at port-channel main interface. This policy application should in turn be mapped statically to member interfaces. No egress policy-map application allowed on port-channel member interface or EFP.

                        QoS for Multicast/Unicast Traffic

                        While applying QOS, there is no differentiation between unicast and multicast traffic at the queue level. Both the streams are treated equally at queue level for QoS. There are no specific classes available to apply the QoS specific to multicast traffic.

                        Traffic Handling in the Absence of an Output Policy

                        If there is no output policy configured on an EVC or an interface, the unicast traffic is queued at the egress based on the traffic class set at the ingress. In the absence of an output policy, all the egress queues are treated equally and scheduled according to the Round Robin method.

                        Unicast QoS Restrictions

                        Traffic is queued in separate queues at the egress based on the traffic-class set in the frame at the ingress. This is irrespective of whether there is an egress policy applied or not.


                        Note

                        The “class-default” classification does not work at the leaf level of an output policy. This works only at a parent level in a hierarchical policy. It must be ensured that all traffic that needs to be matched using “class-default” at the leaf level is set to “qos-group 0” at the ingress, which forces the traffic-class to 0 resulting in traffic being queued in queue 0 which corresponds to the class-default.

                        Egress Classification

                        The egress classification is limited to using a traffic class field in frames to categorize the frames and make them available for QoS handling. Therefore, classification based on frame fields, such as Ethernet CoS, IP DSCP, IP precedence, and so on, should be done at ingress, and the traffic class should be assigned to the corresponding frames using the ingress marking feature.

                        Traffic is classified to determine whether it should be:
                        • Marked for further processing
                        • Queued and scheduled

                        To configure classification at the egress, see Configuring Egress Classification.

                        Egress Queue Scheduling

                        The Cisco ME 2600X system supports Weighted Round Robin (WRR) and Low Latency Queueing (LLQ). Queueing is based on the class based classification done at egress. LLQ prioritizes and ensures low latency to the traffic in queues configured to be in LLQ, and the remaining traffic is scheduled using WRR.


                        Note

                        Queue depth is not configurable. Each queue has a minimum depth of 25600 bytes and maximum depth of 1048576 bytes.

                        For information on egress LLQ, see Egress LLQ.

                        For information on egress bandwidth, see Egress Bandwidth.

                        For information on egress shaping, see Egress Shaping.

                        For information egress Bandwidth Remaining Ratio (BRR) or Bandwidth Remaining Percent (BRP), see Egress Bandwidth Remaining Ratio and Bandwidth Remaining Percent.

                        Egress LLQ

                        Applications which are latency sensitive require handling of data with least possible delay within the system. In the Cisco ME 2600X system, low latencies are guaranteed by using strict priority scheduling at various congestion points and egress.

                        To configure LLQ, see Configuring Egress LLQ.

                        Egress Bandwidth

                        Applications that require committed information rate (CIR) should reserve the CIR on a per-target basis at the egress. After configuring the CIR, the traffic rates are guaranteed to be met in case of congestion at the egress.

                        To configure the egress bandwidth, see Configuring Egress Bandwidth.

                        Egress Shaping

                        Traffic shaping enables you to control the traffic going out of an interface in order to match its flow to the speed of the remote target interface and to ensure that the traffic conforms to policies contracted for it. Shaping can be used to meet downstream requirements, thereby eliminating bottlenecks in topologies with data-rate mismatches.

                        Shaping is the process of delaying packets in queues to make them conform to a specified profile.

                        To configure shaping at the egress, see Configuring Egress Shaping.

                        Egress Bandwidth Remaining Ratio and Bandwidth Remaining Percent

                        Bandwidth Remaining Ratio (BRR) or Bandwidth Remaining Percent (BRP) specifies the ratio or percentage of the bandwidth that is divided between targets when there is congestion. BRR indicates the ratio with which the various classes are serviced when parent target is scheduled. BRP indicates the bandwidth to be allocated to each class as a percentage of the allocation done to the parent target in a hierarchical QoS model.

                        To configure egress BRR or BRP, see Configuring Egress Bandwidth Remaining Ratio or Bandwidth Remaining Percent.

                        Hierarchical QoS

                        The Cisco ME 2600X system supports hierarchical quality-of-service (H-QoS) that includes QoS at multiple levels in a hierarchy.

                        Ingress H-QoS

                        An H-QoS policy can be attached to an interface or a service instance. The number of levels is limited to two for an input QoS policy, where the parent level denotes the policy target and the child level denotes the QoS traffic class:

                        • Only the default class, that is, class-default is allowed at the parent level. User-defined classes are not supported at the parent level.
                        • Only the police action command is allowed at the parent level. Marking action is not supported. Also, remarking actions are not supported for the parent policer. In effect, a hierarchical policy is configured to achieve only hierarchical metering.

                        EVCS QoS Support

                        The Ethernet Virtual Connection Services (EVCS) uses the concept of service instances and EVC (Ethernet Virtual Circuit). A service instance is the instantiation of an EVC on a given interface on a given device. An EVC is an end-to-end representation of a single instance of a Layer 2 service being offered by a provider to a customer. It embodies the different parameters on which the service is being offered.

                        QoS works with the following EVC combinations:

                        • One TAG case
                        • Two TAG case
                        • One TAG to one TAG
                        • One TAG to two TAG
                        • Two TAG to one TAG
                        • Two TAG to two TAG
                        • One TAG termination
                        • Two TAG termination
                        • Tag to Tag translation

                        Restrictions for QoS on EVCS

                        • CoS marking or remarking is not supported for service instances defined using VLAN ranges or “encapsulation default”.
                        • CoS marking or remarking action applies to both inner and outer tags, when inner tag is modified within the system. In all other cases, the marking or remarking action that the user specifies is limited only to the outer tag.

                        Note
                        For information on EVC, see Understanding Ethernet Virtual Circuit.

                        QoS Support on Port-Channel

                        This section explains the QoS on the Port-Channel feature support for ingress and egress.

                        QoS Support on Port-Channel at Ingress

                        The QoS on the port-channel feature enables QoS service-policies to be applied at the ingress on the following targets:

                        • Port-channel member link
                        • Port-channel main interface
                        • Port-channel EVC

                        For a policy-map attached to a port-channel main interface, ingress traffic coming from any member link is subjected to the same policy-map configured on the port-channel main interface. If no policy-map is configured on the port-channel main interface, ingress traffic from the member-link is subjected to the policy-map attached to the:

                        • EVC through which the traffic is flowing.
                        • Member link.

                        The QoS policy can be attached to a port-channel even if the member interfaces are on different cards. Policy-maps cannot coexist on a port-channel main interface, EVC, and member link at the same time.

                        Restrictions for QoS Support on Port-Channel at Ingress

                        The policer configuration is enforced only on a single card and not across cards in a distributed link aggregation group (LAG). However, member links might span across cards.

                        QoS Support on Port-Channel at Egress

                        The QoS on port-channel feature enables QoS service-policies to be applied at the egress on the port-channel main interface.


                        Note

                        Egress service policy is not supported on the port-channel member link.

                        Restrictions for QoS Support on Port-Channel at Egress

                        A policy that is applied on a port channel is not applicable to the aggregate port channel traffic. It is applicable only on a per port-channel member basis. Therefore, if a configuration that shapes all the traffic to x Mbps on the port-channel main interface exists, it gets translated to a configuration that shapes each member link to x Mbps. As a result, the aggregate traffic on the port channel could be up to n times x Mbps, where n is the number of links in the port-channel.

                        QoS Statistics

                        Enhanced performance monitoring displays QoS statistics on the Cisco ME 2600X interfaces. QoS statistics are supported at the 1GE interface, 10GE interface, and service instance levels. At the ingress, only byte counters are supported and at the egress, both packet and byte counters are supported.

                        Statistics supported at ingress are shown in the table below:
                        Table 2 Statistics at Ingress
                        Statistics Collected 1GE Interface 10GE Interface EVC Port Channel Interface
                        Classification statistics— Packet and Byte Counters Yes Yes Yes Yes
                        Marking Statistics—Byte Counters No No No No
                        Marking Statistics—Packet Counters Yes Yes Yes Yes
                        Policing Statistics—Packet and Byte Counters Supported with limitations:
                        • In a 2-color policer, both green and red byte counters are supported.
                        • In a 3-color policer, green/non-green or non-red/red are supported.
                        		Supported with limitations:
                        • In a 2-color policer, both green and red byte counters are supported.
                        • In a 3-color policer, green and non-green or non-red and red are supported.
                        		No Supported with limitations:
                        • In a 2-color policer, both green and red byte counters are supported.
                        • In a 3-color policer, green/non-green or non-red/red are supported.
                        Statistics supported at egress are shown in this table:
                        Table 3 Statistics at Egress
                        Statistics Collected 1GE Interface 10GE Interface EVC Port Channel Interface
                        Classification statistics - Packet and Byte Counters Yes Yes No Yes
                        Queuing Statistics— (Accepted or Dropped) Packet and Byte Counters Yes Yes No Yes
                        Match Statistics—Packet and Byte Counters Yes Yes No Yes

                        Scalability

                        The table below lists scalability for Cisco ME 2600X:

                        320 x 8 policiers
                        System supports 320 policymaps
                        System supports 512 unique class maps
                        System supports 1024 unique policymaps
                        160 policymaps on LAG interface
                        7 queues / classes per interface

                        Note

                        If all the FP entries are used under port-channel pool (LAG interface has maximum EFPs with maximum number of filters), then LAG works in double mode and you can not apply ingress policer on any interface or service instance.

                        How to Configure QoS

                        Configuring QoS Features


                        Note

                        Users can create traffic policies and attach these policies to targets. A traffic policy contains a traffic class and one or more QoS features. A traffic class is used to classify traffic, while the QoS features in the traffic policy determine how to treat the classified traffic.

                        SUMMARY STEPS

                          1.    Define a traffic class using the class-map command:

                          2.    Create a traffic policy using the policy-map command to associate the traffic class with one or more QoS features (using the policy-map command):

                          3.    Attach the traffic policy to the target using the service-policy command, see Attaching or Removing a Traffic Policy from the Target.

                          4.    Monitor and verify the QoS configuration. See Monitoring and Verifying QoS Configuration.


                        DETAILED STEPS
                          Step 1   Define a traffic class using the class-map command:
                          1. To configure traffic classification at the ingress, see Configuring Ingress Classification.
                          2. To configure traffic classification at the egress, see Configuring Egress Classification.
                          Step 2   Create a traffic policy using the policy-map command to associate the traffic class with one or more QoS features (using the policy-map command):
                          1. To configure policing at the ingress, see Configuring Ingress Policing.
                          2. To configure marking at the ingress, see Configuring Ingress Marking.
                          3. To configure shaping at the egress, see Configuring Egress Shaping.
                          4. To configure the egress bandwidth, see Configuring Egress Bandwidth.
                          5. To configure low-latency queuing (LLQ), see Configuring Egress LLQ.
                          6. To configure bandwidth remaining ratio (BRR) or bandwidth remaining percent (BRP), see Configuring Egress Bandwidth Remaining Ratio or Bandwidth Remaining Percent.
                          Step 3   Attach the traffic policy to the target using the service-policy command, see Attaching or Removing a Traffic Policy from the Target.
                          Step 4   Monitor and verify the QoS configuration. See Monitoring and Verifying QoS Configuration.

                          Configuring Ingress Classification

                          • The match commands are used to specify various criteria for classifying packets. The packets are checked to determine whether they match the criteria specified in the match commands.
                          • The match-all keyword is added to the match command and match-all is the default. This classification specifies that the traffic class must match all of the specified criteria within the class-map.
                          • The CoS should be 0 by default for untagged traffic and it will be matched with a CoS 0 filter, if the class-map has the CoS 0 filter.

                          To configure ingress classification on the device, complete the following steps:

                          Before You Begin

                          Note
                          • Traffic classification based on multiple QoS fields (Ethernet class of service [CoS], IP precedence, and so on) for a single packet is not supported. Traffic classification is based only on the first matching parameter (in the user-specified order) of the QoS fields, if multiple match criteria are specified in a single class.
                          • The match-all cannot have more than two combinations of the classification criteria. However, the class-map can be created with more than two combinations of classification criteria. The policy with such class-map does not work and reports an error message indicating the failure. You should rectify the class-map with one classification criteria and try again.
                          • When using class-map, after you have added or removed a filter, do not immediately remove or add another filter as it may cause an error message to display. If you receive an error message, try again by increasing the time interval between removal or addition of the filter.
                          SUMMARY STEPS

                            1.    enable

                            2.    configure terminal

                            3.    class-map [match-any]| [match-all] class-map-name

                            4.    match cos cos-number

                            5.    end


                          DETAILED STEPS
                             Command or ActionPurpose
                            Step 1enable


                            Example:
                            Switch> enable
                             

                            Enables privileged EXEC mode.

                            • Enter your password if prompted.
                             
                            Step 2configure terminal


                            Example:
                            Switch# configure terminal
                             

                            Enters global configuration mode.

                             
                            Step 3class-map [match-any]| [match-all] class-map-name

                            Example:
                            Switch(config)# class-map match-any class1
                             
                            Creates a class to be used with a class map and enters the class-map configuration mode. The class map is used for matching packets to the specified class.
                            • match-any— Specifies that one of the match criterion must be met. Use this keyword only if you have to specify more than one match command.
                            • match-all— Specifies that the traffic class must match all of the specified criteria.
                            • class-map-name— Class map name. This is the name of the class map and can have a maximum of 40 alphanumeric characters.
                             
                            Step 4match cos cos-number


                            Example:
                            Switch(config-cmap)# match cos 2
                             
                            Matches a packet on the basis of a Layer 2 CoS number.
                            • cos-number— CoS value. The value can range from 0 to 7.
                            Note   

                            The match cos command is just an example of one of the match commands that can be used. For a list of other match commands, see Table 1

                             
                            Step 5end


                            Example:
                            Switch(config-cmap)# end
                             

                            Exits class-map configuration mode and returns to privileged EXEC mode.

                             

                            The table below provides the traffic class commands supported at the ingress:

                            Table 4 Traffic Class Commands
                            Command Description
                            match cos cos-number

                            Example:

                            Switch(config-cmap)# match cos 2
                            Matches a packet on the basis of a Layer 2 CoS number.
                            • cos-number— CoS value. The value can range from 0 to 7.
                            match ip precedence ip-precedence-value

                            Example:

                            Switch(config-cmap)# match ip precedence 5
                            Identifies the IP precedence value as match criteria.
                            • ip-precedence-value— IP precedence value. The value can range from 0 to 7.
                            match ip dscp ip- dscp-value

                            Example:

                            Switch(config-cmap)# match ip dscp 6
                            Identifies a specific IP DSCP value as a match criterion.
                            • ip- dscp-value — IP DSCP value. The value can range from 0 to 63.
                            match vlan [vlanid ]

                            Example:

                            Switch(config-cmap)# match vlan 100
                            Specifies a VLAN ID or range of VLAN IDs in a class-map to match packets.
                            • vlanid —VLAN ID. The value can range from 0 to 4096.

                            Configuring Ingress Policing

                            To configure ingress policing on the device, complete the following steps:
                            Before You BeginConfiguring Ingress Classification

                            Note
                            • In a hierarchical QoS policy, only a single-rate, 2-color policer is supported at the parent level. This should be configured using the police [rate] bps-value action command. The police cir command is not supported at the parent level.
                            • In a hierarchical QoS policy with policer configured at the parent level, only a single-rate, 2-color policer or a dual-rate, 3-color policer is supported at the child level.
                            SUMMARY STEPS

                              1.    enable

                              2.    configure terminal

                              3.    policy-map policy-map-name

                              4.    class {class-name | class-default}

                              5.    police [cir | rate] bps-value [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action

                              6.    end


                            DETAILED STEPS
                               Command or ActionPurpose
                              Step 1enable


                              Example:
                              Switch> enable
                               

                              Enables privileged EXEC mode.

                              • Enter your password if prompted.
                               
                              Step 2configure terminal


                              Example:
                              Switch# configure terminal
                               

                              Enters global configuration mode.

                               
                              Step 3policy-map policy-map-name


                              Example:
                              Switch(config)# policy-map policy1
                               
                              Creates or specifies the name of the traffic policy and enters the policy-map configuration mode.
                              • policy-map-name—Policy map name. This is the name of the policy map and can have a maximum of 40 alphanumeric characters.
                               
                              Step 4 class {class-name | class-default}


                              Example:
                              Switch(config-pmap)# class class1
                               
                              Specifies the name of a traffic class to which the policy applies and enters the policy-map class configuration mode.
                              • Enter the previously configured class-map name.
                                • class-name—User-defined class name to which the policy applies.
                                • class-default—Specifies that the policy applies to the default traffic class.
                              Note   

                              This step associates the traffic class with the traffic policy.

                               
                              Step 5police [cir | rate] bps-value [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action


                              Example:
                              Switch(config-pmap-c)# police cir 5000000 bc 200000 be 400000 conform-action transmit exceed-action set-dscp-transmit violate-action drop
                               
                              Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm:
                              • cir—Indicates that the committed information rate (CIR) is used for policing traffic.
                              • rate—Indicates that the police rate is used for policing traffic.
                              • bps value—Average rate in bits per second. The valid values range from 8000 to 10000000000.
                              • bc—Indicates that the committed (conform) burst size is used for policing traffic.
                              • burst—Indicates that the burst size is used for policing traffic.
                              • bc—Committed (conform) burst size or burst size in bytes. The valid values range from 1000 to 256000000.
                              • be—Indicates that the excess burst size is used for policing traffic.
                              • peak-burst—Indicates that the peak-burst size is used for policing traffic.
                              • be—Excess burst size or peak-burst size in bytes. The valid values range from 1000 to 256000000.
                              • action—Action taken on a packet when it conforms, exceeds, or violates the interface bandwidth. The possible actions are shown in Table 1.
                              Note   

                              The police [cir | rate] bps-value [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action command is just an example of one of the policy commands that can be used. For a list of other policy commands, see Table 1.

                               
                              Step 6end

                              Example:
                              Switch(config-pmap)# end
                               

                              Exits policy-map configuration mode and returns to privileged EXEC mode.

                               

                              The table below provides the traffic policy commands supported at the Ingress:

                              Table 5 Traffic Policy Commands
                              Command Description
                              police [cir | rate] bps-value [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action

                              Example:

                              Switch(config-pmap-c)# police cir 5000000  bc 200000 be 400000 conform-action transmit  exceed-action set-dscp-transmit violate-action drop
                              Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm:
                              • cir—Indicates that the committed information rate (CIR) is used for policing traffic.
                              • rate—Indicates that the police rate is used for policing traffic.
                              • bps value—Average rate in bits per second. The valid values range from 8000 to 10000000000.
                              • bc—Indicates that the committed (conform) burst size is used for policing traffic.
                              • burst—Indicates that the burst size is used for policing traffic.
                              • bc—Committed (conform) burst size or burst size in bytes. The valid values range from 1000 to 256000000.
                              • be—Indicates that the excess burst size is used for policing traffic.
                              • peak-burst—Indicates that the peak-burst size is used for policing traffic.
                              • be—Excess burst size or peak-burst size in bytes. The valid values range from 1000 to 256000000.
                              • action—Action taken on a packet when it conforms, exceeds, or violates the interface bandwidth. The possible actions are shown in Table 1.
                              police [cir | rate] percent % [bc | burst] bc [be | peak-burst] be conform-action action exceed-action action violate-action action

                              Example:

                              Switch(config-pmap-c)# police cir percent 10 bc 200000 be 400000 conform-action transmit exceed-action set-dscp-transmit 25 violate-action drop
                              Configures traffic policing on the basis of a percentage of bandwidth available on an interface, where:
                              • cir—Indicates that the committed information rate (CIR) is used for policing traffic.
                              • rate—Indicates that the police rate is used for policing traffic.
                              • percent—Indicates that a percentage of bandwidth is used for calculating CIR or rate.
                              • %— CIR or rate bandwidth percentage. The valid values range from 1 to 100.
                              • bc—Indicates that the committed (conform) burst size is used for policing traffic.
                              • burst—Indicates that the burst size is used for policing traffic.
                              • bc—Committed (conform) burst size or burst size in mill-seconds or micro-seconds.
                              • be—Indicates that the excess burst size is used for policing traffic.
                              • peak-burst—Indicates that the peak-burst size is used for policing traffic.
                              • be—Excess burst size or peak-burst size in mill-seconds or micro-seconds.
                              • action—Action taken on a packet when it conforms, exceeds, or violates the interface bandwidth. The possible actions are shown in Table 1.
                              police [cir | rate] bps-value [bc | burst] bc [pir | peak-rate] pir [be | peak-burst] be conform-action action exceed-action action violate-action action

                              Example:

                              Switch(config-pmap-c)# police cir 500000000 bc 200000 pir 510000000 be 400000 conform-action transmit exceed-action set-dscp-transmit 50 violate-action drop
                              Configures traffic policing using two rates (CIR and PIR) where:
                              • cir—Indicates that the committed information rate (CIR) is used for policing traffic.
                              • rate—Indicates that the police rate is used for policing traffic.
                              • bps value—Average rate in bits per second. The valid values range from 8000 to 10000000000
                              • bc—Indicates that the committed (conform) burst size is used for policing traffic.
                              • burst—Indicates that the burst size is used for policing traffic.
                              • bc—Committed (conform) burst size or burst size in bytes. The valid values range from 1000 to 256000000.
                              • pir— Indicates that the peak information rate (PIR) is used for policing traffic.
                              • peak-rate— Indicates that the peak rate is used for policing traffic.
                              • pir—Peak information rate or peak rate in bits per second. The valid values range from 8000 to 10000000000
                              • be—Indicates that the excess burst size is used for policing traffic.
                              • peak-burst—Indicates that the peak-burst size is used for policing traffic.
                              • be—Excess burst size or peak-burst size in bytes. The valid values range from 1000 to 256000000.
                              • action—Action taken on a packet when it conforms, exceeds, or violates the interface bandwidth. The possible actions are shown in Table 1.

                              Attaching or Removing a Traffic Policy from the Target

                              Before a traffic policy can be enabled for a class of traffic, it must be configured on a target. Use the service-policy {input | output} configuration command to attach a traffic policy to a target and to specify the direction in which the policy should be applied (either on packets entering/ingressing the target or packets exiting/egressing the target). Only one traffic policy can be applied to an interface in a given direction. Use the no form of the command, that is, no service-policy {input | output} policy-map-name to detach a traffic policy from a target.

                              Before You Begin

                              Complete any one of the following tasks:

                              SUMMARY STEPS

                                1.    enable

                                2.    configure terminal

                                3.    interface type slot/port

                                4.    service instance id ethernet

                                5.    service-policy {input | output} policy-map-name

                                6.    no service-policy {input | output} policy-map-name

                                7.    end


                              DETAILED STEPS
                                 Command or ActionPurpose
                                Step 1enable


                                Example:
                                Switch> enable
                                 

                                Enables privileged EXEC mode.

                                • Enter your password if prompted.
                                 
                                Step 2configure terminal


                                Example:
                                Switch# configure terminal
                                 

                                Enters global configuration mode.

                                 
                                Step 3interface type slot/port


                                Example:
                                Switch(config)# interface TenGigabitEthernet 0/45
                                 

                                Configures an interface type and enters the interface configuration mode.

                                • interface-type—Interface type
                                • interface-number—Interface number.
                                 
                                Step 4service instance id ethernet


                                Example:
                                Switch(config-if)# service instance 100  ethernet
                                 

                                Enters the service instance mode.

                                • id—Service instance ID.
                                 
                                Step 5service-policy {input | output} policy-map-name


                                Example:
                                Switch(config-if-srv-instance)# service-policy input policy1
                                 

                                Attaches a policy map to a target.

                                • Enter either the input or output keyword and the policy map name.
                                • policy-map-name—Name of the policy map.
                                 
                                Step 6no service-policy {input | output} policy-map-name


                                Example:
                                Switch(config-if-srv-instance)# no  service-policy input policy1
                                 

                                Removes the policy map from the target.

                                • Enter either the input or output keyword and the policy map name.
                                 
                                Step 7end


                                Example:
                                Switch(config-if-srv-instance)# end
                                 

                                Exits the service instance mode.

                                 

                                Configuring Ingress Marking

                                Before You Begin

                                Complete the following task:

                                Configuring Ingress Policing


                                Note

                                Marking of the Layer 2 CoS bit for VPWS traffic is not supported.

                                SUMMARY STEPS

                                  1.    enable

                                  2.    configure terminal

                                  3.    policy-map policy-map-name

                                  4.    class {class-name | class-default}

                                  5.    set ip precedence ip precedence value

                                  6.    end


                                DETAILED STEPS
                                   Command or ActionPurpose
                                  Step 1enable


                                  Example:
                                  Switch> enable
                                   

                                  Enables privileged EXEC mode.

                                  • Enter your password if prompted.
                                   
                                  Step 2configure terminal


                                  Example:
                                  Switch# configure terminal
                                   

                                  Enters global configuration mode.

                                   
                                  Step 3policy-map policy-map-name


                                  Example:
                                  Switch(config)# policy-map policy1
                                   
                                  Creates or specifies the name of the traffic policy and enters the policy-map configuration mode.
                                  • policy-map-name— Policy map name. This is the name of the policy map and can have a maximum of 40 alphanumeric characters.
                                   
                                  Step 4 class {class-name | class-default}


                                  Example:
                                  Switch(config-pmap)# class class1
                                   
                                  Specifies the name of a traffic class to which the policy applies and enters the policy-map class configuration mode.
                                  • Enter the previously configured class-map name.
                                    • class-name—User-defined class name to which the policy applies.
                                    • class-default—Specifies that the policy applies to the default traffic class.
                                  Note   

                                  This step associates the traffic class with the traffic policy.

                                   
                                  Step 5 set ip precedence ip precedence value


                                  Example:
                                  Switch(config-pmap-c)# set ip precedence 2
                                   
                                  Marks the precedence value in the IP header with a value between 0 to 7.
                                  • ip precedence value— IP precedence value.
                                  Note   

                                  The set ip precedence command is just an example of one of the marking commands that can be used. For a list of other marking commands, see Table 1.

                                   
                                  Step 6end


                                  Example:
                                  Switch(config-pmap)# end
                                   

                                  Exits policy-map configuration mode and returns to privileged EXEC mode.

                                   

                                  The table below provides the traffic marking commands supported at Ingress.

                                  Table 6 Traffic Marking Commands
                                  Command Description
                                  set ip precedence ip-precedence-value

                                  Example:

                                  Switch(config-pmap-c)# set ip precedence 2
                                  Marks the precedence value in the IP header with a value between 0 to 7.
                                  • ip precedence value—IP precedence value.
                                  set cos cos-value

                                  Example:

                                  Switch(config-pmap-c)# set cos 2
                                  Marks the CoS value between 0 to 7 in an 802.1Q tagged frame
                                  • cos-value—CoS value.
                                  set ip dscp ip-dscp-value

                                  Example:

                                  Switch(config-pmap-c)# set ip dscp 22
                                  Marks the IP DSCP in the ToS byte with a value between 0 to 63.
                                  • ip-dscp-value—IP DSCP value.
                                  set qos group qos-group-value

                                  Example:

                                  Switch(config-pmap-c)# set qos group 3
                                  Marks a QoS group identifier (ID) with a value between 0 to 7 that can be used later to classify packets.
                                  • qos-group-value—QoS group value.

                                  Configuring Ingress Re-Marking

                                  To configure ingress re-marking on the device, complete the following steps:
                                  Before You Begin

                                  Complete the following task:

                                  Configuring Ingress Policing


                                  Note

                                  You cannot apply remarking for precedence and DSCP together.

                                  SUMMARY STEPS

                                    1.    enable

                                    2.    configure terminal

                                    3.    policy-map policy-map-name

                                    4.    class {class-name | class-default}

                                    5.    set ip precedence ip precedence value

                                    6.    police cir percent value

                                    7.    Confirm-action set-cos-transmit value

                                    8.    end


                                  DETAILED STEPS
                                     Command or ActionPurpose
                                    Step 1enable


                                    Example:
                                    Switch> enable
                                     

                                    Enables privileged EXEC mode.

                                    • Enter your password if prompted.
                                     
                                    Step 2configure terminal


                                    Example:
                                    Switch# configure terminal
                                     

                                    Enters global configuration mode.

                                     
                                    Step 3policy-map policy-map-name


                                    Example:
                                    Switch(config)# policy-map policy1
                                     
                                    Creates or specifies the name of the traffic policy and enters the policy-map configuration mode.
                                    • policy-map-name— Policy map name. This is the name of the policy map and can have a maximum of 40 alphanumeric characters.
                                     
                                    Step 4 class {class-name | class-default}


                                    Example:
                                    Switch(config-pmap)# class class1
                                     
                                    Specifies the name of a traffic class to which the policy applies and enters the policy-map class configuration mode.
                                    • Enter the previously configured class-map name.
                                      • class-name—User-defined class name to which the policy applies.
                                      • class-default—Specifies that the policy applies to the default traffic class.
                                    Note   

                                    This step associates the traffic class with the traffic policy.

                                     
                                    Step 5 set ip precedence ip precedence value


                                    Example:
                                    Switch(config-pmap-c)# set ip precedence 2
                                     
                                    Marks the precedence value in the IP header with a value between 0 to 7.
                                    • ip precedence value— IP precedence value.
                                    Note   

                                    The set ip precedence command is just an example of one of the marking commands that can be used. For a list of other marking commands, see Table 1.

                                     
                                    Step 6police cir percent value


                                    Example:
                                    Switch(config-pmap-c)# police cir percent 2


                                    Example:
                                     Switch(config-pmap-c)# police 100m
                                     

                                    Specifies the bandwidth to confirm traffic at ingress.

                                     
                                    Step 7Confirm-action set-cos-transmit value


                                    Example:
                                    Switch(config-pmap-c-police)# Confirm-action set-cos-transmit 4
                                     

                                    Remarks the cos value in the vlan header with a value between 0 to 7.

                                     
                                    Step 8end


                                    Example:
                                    Switch(config-pmap)# end
                                     

                                    Exits policy-map configuration mode and returns to privileged EXEC mode.

                                     

                                    The table below provides the traffic marking commands supported at Ingress:

                                    Table 7 Traffic Marking Commands
                                    Command Description
                                    set-prec-transmit ip-precedence-value

                                    Example:

                                    Switch(config-pmap-c)# set-prec-transmit 2
                                    Marks the precedence value in the IP header with a value between 0 to 7.
                                    • ip precedence value—IP precedence value.
                                    set-cos-transmit cos-value

                                    Example:

                                    Switch(config-pmap-c)# set-cos-transmit 2
                                    Marks the CoS value between 0 to 7 in an 802.1Q tagged frame
                                    • cos-value—CoS value.
                                    set-dscp-transmit ip-dscp-value

                                    Example:

                                    Switch(config-pmap-c)# set-dscp-transmit 22
                                    Marks the IP DSCP in the ToS byte with a value between 0 to 63.
                                    • ip-dscp-value—IP DSCP value.
                                    set-qos-transmit qos-group-value

                                    Example:

                                    Switch(config-pmap-c)# set-qos-transmit 3
                                    Marks a QoS group identifier (ID) with a value between 0 to 6 that can be used later to classify packets.
                                    • qos-group-value—QoS group value.

                                    Configuring Egress Classification

                                    To configure egress classification on the device, complete the following steps:

                                    Before You Begin

                                    Note
                                    • Only one match filter is supported for each class-map.
                                    • Only QoS-group based matching is supported for user-defined classes.
                                    • Match based on QoS-group 3 and QoS-group 7 is used only for low latency queuing across the system.
                                    • Match based on the class-default in the output policy suggests that matching is based on the QoS-group 0 and not the class where traffic, which does not match any selection criteria in the configured class maps, is directed.
                                    SUMMARY STEPS

                                      1.    enable

                                      2.    configure terminal

                                      3.    class-map [match-any] class-map-name

                                      4.    match qos-group qos-group-number

                                      5.    end


                                    DETAILED STEPS
                                       Command or ActionPurpose
                                      Step 1enable


                                      Example:
                                      Switch> enable
                                       

                                      Enables privileged EXEC mode.

                                      • Enter your password if prompted.
                                       
                                      Step 2configure terminal


                                      Example:
                                      Switch# configure terminal
                                       

                                      Enters global configuration mode.

                                       
                                      Step 3class-map [match-any] class-map-name


                                      Example:
                                      Switch(config)# class-map match-any class1
                                       
                                      Creates a class to be used with a class map and enters the class-map configuration mode. The class map is used for matching packets to the specified class.
                                      • class-map-name—Class name. This is the name of the class map and can have a maximum of 40 alphanumeric characters.

                                      The match-any keyword specifies that one of the match criteria must be met. Use this keyword only if you have to specify more than one match command.

                                       
                                      Step 4match qos-group qos-group-number


                                      Example:
                                      Switch(config-cmap)# match qos-group 2
                                       
                                      Matches a packet on the basis of traffic class represented by the qos-group.
                                      • qos-group-number—QoS-group value. The value can range from 0 to 7.
                                       
                                      Step 5end


                                      Example:
                                      Switch(config-cmap)# end
                                       

                                      Exits class-map configuration mode and returns to privileged EXEC mode.

                                       

                                      Configuring Egress LLQ

                                      To configure egress LLQ on the device, complete the following steps:
                                      Before You Begin

                                      Complete step 1 to step 5 of Configuring Ingress Policing


                                      Note
                                      • The priority command enables the rate-limit option to ensure that a particular rate is not exceeded. However, in the Cisco ME 2600X system, egress rate limiting is achieved using shapers that can cause additional delays. Therefore, it is advised to ensure that for LLQ traffic, rate limiting is done at ingress, and the rates specified at egress are just placeholders that are never exceeded. Exceeding the rate limit at egress would mean increased latencies for LLQ traffic.
                                      • The priority command is supported only under class-map with qos-group 3 or 7 as the match criteria and multicast-priority class.
                                      SUMMARY STEPS

                                        1.    enable

                                        2.    configure terminal

                                        3.    policy map policy-map-name

                                        4.    class {class-name | class-default}

                                        5.    priority bandwidth value

                                        6.    end


                                      DETAILED STEPS
                                         Command or ActionPurpose
                                        Step 1enable


                                        Example:
                                        Switch> enable
                                         

                                        Enables privileged EXEC mode.

                                        • Enter your password if prompted.
                                         
                                        Step 2configure terminal


                                        Example:
                                        Switch# configure terminal
                                         

                                        Enters global configuration mode.

                                         
                                        Step 3policy map policy-map-name


                                        Example:
                                        Switch(config)# policy-map policy1
                                         

                                        Creates or modifies a traffic policy and enters the policy-map configuration mode. The policy-map-name specifies the name of the traffic policy, which can have a maximum of 40 alphanumeric characters.

                                         
                                        Step 4 class {class-name | class-default}


                                        Example:
                                        Switch(config-pmap)# class class_qos_1
                                         

                                        Specifies the name of the traffic class to which this policy applies and enters the policy-map class configuration mode, where:

                                        • class-name—Name of a predefined class included in the service policy.
                                        • class-default—Specifies that the policy applies to the default traffic class.
                                         
                                        Step 5 priority bandwidth value


                                        Example:
                                        Switch(config-pmap-c)# priority 10000
                                         

                                        Provides strict priority to a class of traffic belonging to the policy-map. Specifies the maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. The bandwidth value is in kbps, and can range from 1 to 10000000.

                                        Note   

                                        The priority bandwidth value command is just an example of one of the priority commands that can be used. For a list of other priority commands, see Table 1.

                                         
                                        Step 6end


                                        Example:
                                        Switch(config-pmap-c)# end
                                         

                                        Exits the configuration mode and returns to privileged EXEC mode.

                                         

                                        The table below lists the priority commands:

                                        Table 8 Priority (LLQ) Commands
                                        Command Description
                                        priority bandwidth value

                                        Example:

                                        Switch(config-pmap-c)# priority 10000

                                        Provides strict priority to a class of traffic belonging to the policy-map. Specifies the maximum bandwidth usage by a traffic class through the use of a token bucket algorithm. The bandwidth value is in kbps, and can range from 1 to 10000000.

                                        priority

                                        Example:

                                        Switch(config-pmap-c)# priority

                                        This command provides low-latency queuing without specifying the rate limiter.
                                        priority percent x%

                                        Example:

                                        Switch(config-pmap-c)# priority 10%

                                        Indicates that the rate of traffic that is given low latency handling is x% of the parent interface bandwidth or x% parent class CIR if policy not applied on an interface. The percentage can be a number from 1 to 100.

                                        Configuring Egress Bandwidth

                                        To configure egress bandwidth on the device, complete the following steps:
                                        Before You Begin

                                        Complete step 1 to step 5 of Configuring Ingress Policing


                                        Note
                                        • Bandwidth action is not supported on classes with qos-group 3 or 7 as the match criteria.
                                        • The bandwidth command cannot be used in combination with BRR or BRP in a class-map or a policy-map.
                                        • The system does not validate the total CIR configured on all the targets for various congestion points. Therefore, it should be ensured that the total CIR configured does not exceed the total bandwidth available.
                                          • Total CIR configured for a 1 Gbps interface should not exceed 1 Gbps, which includes CIR in the policy applied on the interface and services on that interface.
                                          • Total CIR configured for a 10 Gbps interface should not exceed 10 Gbps, which includes CIR in the policy applied on the interface and services on that interface.
                                          • Total CIR for all the targets on a Cisco ME 2600X shelf should not exceed 9.882 Gbps; this is the least bandwidth for a Cisco ME 2600X shelf in a scenario where only one of the interconnects for a Cisco ME 2600X shelf is functional.
                                        SUMMARY STEPS

                                          1.    enable

                                          2.    configure terminal

                                          3.    policy map policy-map-name

                                          4.    class {class-name | class-default}

                                          5.    bandwidth bandwidth value

                                          6.    end


                                        DETAILED STEPS
                                           Command or ActionPurpose
                                          Step 1enable


                                          Example:
                                          Switch> enable
                                           

                                          Enables privileged EXEC mode.

                                          • Enter your password if prompted.
                                           
                                          Step 2configure terminal


                                          Example:
                                          Switch# configure terminal
                                           

                                          Enters global configuration mode.

                                           
                                          Step 3policy map policy-map-name


                                          Example:
                                          Switch(config)# policy-map policy1
                                           

                                          Creates or modifies a traffic policy and enters the policy-map configuration mode. The policy-map-name specifies the name of the traffic policy that can have a maximum of 40 alphanumeric characters.

                                           
                                          Step 4 class {class-name | class-default}


                                          Example:
                                          Switch(config)# class c3
                                           

                                          Specifies the name of the traffic class to which this policy applies and enters the policy-map class configuration mode, where:

                                          • class-name—User-defined class name to which the policy applies.
                                          • class-default—Specifies that the policy applies to the default traffic class.
                                           
                                          Step 5bandwidth bandwidth value


                                          Example:
                                          Switch(config-pmap-c)# bandwidth 10000
                                           
                                          Specifies the amount of bandwidth in kbps to be assigned to the class. Implies that the class where this is applied is given a minimum bandwidth guarantee of bandwidth value in kbps. The amount of bandwidth configured should be large enough to also accommodate Layer 2 overheads.
                                          Note   

                                          The bandwidth bandwidth value command is just an example of one of the bandwidth commands that can be used. For a list of other bandwidth commands, see Table 1.

                                           
                                          Step 6end


                                          Example:
                                          Switch(config-pmap-c)# end
                                           

                                          Exits the configuration mode and returns to privileged EXEC mode.

                                           

                                          The table below lists the bandwidth commands:

                                          Table 9 Bandwidth Commands
                                          Command Description
                                          bandwidth bandwidth-value

                                          Example:

                                          Switch(config-pmap-c)# bandwidth 10000

                                          Specifies the amount of bandwidth in kbps to be assigned to the class. Implies that the class where this is applied is given a minimum bandwidth guarantee of bandwidth-value kbps. The amount of bandwidth configured should be large enough to also accommodate Layer 2 overhead.
                                          bandwidth percent %

                                          Example:

                                          Switch(config-pmap-c)# bandwidth percent 20

                                          Specifies the amount of bandwidth, in percentage from the available bandwidth, to be assigned to the class. The value ranges from 1 to 100.

                                          Configuring Egress Shaping

                                          To configure shaping at the egress on the device, complete the following steps:
                                          Before You Begin

                                          Complete step 1 to step 5 of Configuring Ingress Policing.


                                          Note
                                          • The shaping command is not supported on classes with qos-group 3 or 7 as the match criteria.
                                          • Shape on a traffic class would mean buffering of traffic in the system memory, which could result in increased latencies for these streams.
                                          SUMMARY STEPS

                                            1.    enable

                                            2.    configure terminal

                                            3.    class-map [match-any] class-map-name

                                            4.    policy map policy-map-name

                                            5.    class class-name

                                            6.    shape average cir value

                                            7.    end


                                          DETAILED STEPS
                                             Command or ActionPurpose
                                            Step 1enable


                                            Example:
                                            Switch> enable
                                             

                                            Enables privileged EXEC mode.

                                            • Enter your password if prompted.
                                             
                                            Step 2configure terminal


                                            Example:
                                            Switch# configure terminal
                                             

                                            Enters global configuration mode.

                                             
                                            Step 3class-map [match-any] class-map-name


                                            Example:
                                            Switch(config)# class-map class-interface-all
                                             

                                            Creates a class map to be used for matching packets to a class.

                                             
                                            Step 4policy map policy-map-name


                                            Example:
                                            Switch(config)# policy-map test2
                                             

                                            policy-map-name—Name of the policy-map to configure.

                                             
                                            Step 5class class-name


                                            Example:
                                            Switch(config-pmap)# class classtest
                                             

                                            class-name—Name of a predefined class included in the service policy.

                                             
                                            Step 6shape average cir value


                                            Example:
                                            Switch(config-pmap-c)# shape average 10000000
                                             

                                            cir value—Average rate traffic shaping. The committed information rate (CIR) value ranges from 8000 to 10000000000 bps.

                                            Note   

                                            The shape average cir value command is just an example of one of the shape commands that can be used. For a list of other shape commands, see Table 1.

                                             
                                            Step 7end


                                            Example:
                                            Switch(config-pmap-c)# end
                                             

                                            Exits the configuration mode and returns to privileged EXEC mode.

                                             

                                            Table 1 provides the traffic shaping commands:

                                            Table 10 Traffic Shaping Commands
                                            Command Description
                                            shape average percent %

                                            Example:

                                            Switch(config-pmap-c)# shape average percent 20
                                            Shapes a class to a percent of visible bandwidth.
                                            • %—Percentage. The value should range from 1 to 100.
                                            shape average cir value

                                            Example:

                                            Switch(config-pmap-c)# shape average 10000000
                                            		 Specifies the average rate traffic shaping.
                                            • cir value—CIR value in bps. The committed information rate (CIR) value ranges from 8000 to 10000000000 bps.

                                            Configuring Egress Bandwidth Remaining Ratio or Bandwidth Remaining Percent

                                            BRR is implemented on logical interfaces using hierarchical policy-maps.

                                            To configure QoS egress BRR or BRP on the device, complete the following steps:

                                            Before You Begin

                                            Complete step 1 to step 5 of Configuring Ingress Policing


                                            Note
                                            • The BRR and BRP commands are not supported in combination with the bandwidth action in a class-map or a policy-map.
                                            • The BRR and BRP command are not supported on classes with qos-group 3 or 7 as the match criteria.
                                            SUMMARY STEPS

                                              1.    enable

                                              2.    configure terminal

                                              3.    policy map policy-map-name

                                              4.    class {class-name | class-default}

                                              5.    bandwidth remaining ratio ratio

                                              6.    end


                                            DETAILED STEPS
                                               Command or ActionPurpose
                                              Step 1enable


                                              Example:
                                              Switch> enable
                                               

                                              Enables privileged EXEC mode.

                                              • Enter your password if prompted.
                                               
                                              Step 2configure terminal


                                              Example:
                                              Switch# configure terminal
                                               

                                              Enters global configuration mode.

                                               
                                              Step 3policy map policy-map-name


                                              Example:
                                              Switch(config)# policy-map policy1
                                               

                                              Creates or modifies a traffic policy and enters the policy-map configuration mode. The policy-map-name specifies the name of the traffic policy, which can have a maximum of 40 alphanumeric characters.

                                               
                                              Step 4 class {class-name | class-default}


                                              Example:
                                              Switch(config-pmap)# class c3
                                               

                                              Specifies the name of the predefined traffic class to which this policy applies and enters the policy-map class configuration mode, where:

                                              • class-name—User-defined class name to which the policy applies.
                                              • class-default—Specifies that the policy applies to the default traffic class.
                                               
                                              Step 5bandwidth remaining ratio ratio


                                              Example:
                                              Switch(config-pmap-c)# bandwidth remaining ratio 2
                                               

                                              Specifies a bandwidth-remaining ratio for class-level or subinterface-level queues to be used during congestion to determine the amount of excess bandwidth (unused by priority traffic) to allocate to non priority queues. The value should be between 1 to 127.

                                              Note   

                                              The bandwidth remaining percent x% can be used instead of the bandwidth remaining ratio ratio command to configure BRP. For details on bandwidth remaining percent command, see Table 1.

                                               
                                              Step 6end


                                              Example:
                                              Switch(config-pmap-c)# end
                                               

                                              Exits the configuration mode and returns to privileged EXEC mode.

                                               

                                              The table below provides the bandwidth remaining ratio or percent commands:

                                              Table 11 Bandwidth Remaining Ratio and Bandwidth Remaining Percent Commands
                                              Command Description
                                              bandwidth remaining percent x%

                                              Example:

                                              Switch(config-pmap-c)# bandwidth remaining percent 20

                                              Specifies that the class where the command is specified should be given x% of the excess bandwidth, where excess bandwidth is the bandwidth in excess of all the minimum bandwidth guarantees of all the classes at the same level. The value should range from 1 to 100.
                                              bandwidth remaining ratio ratio

                                              Example:

                                              Switch(config-pmap-c)# bandwidth remaining ratio 2

                                              Specifies a bandwidth-remaining ratio for class-level or subinterface-level queues to be used during congestion to determine the amount of excess bandwidth (unused by priority traffic) to allocate to non priority queues. The value should be between 1 to 127.

                                              Troubleshooting Tips

                                              The commands listed in this section can be used to see the policies and class-maps that are configured and applied on the Cisco ME 2600X .

                                              Use the following commands to display configured policies and class-maps:
                                              • Show policy-map [policy-map-name]
                                              • Show class-map [class-map-name]

                                              Configuration Examples for QoS

                                              Configuring Ingress Classification

                                              The following example shows how to configure a class-map named ipp5, and enter a match statement for IP precedence 5:

                                              Switch> enable
Switch# configure terminal
Switch(config)# class-map ipp5
Switch(config-cmap)# match ip precedence 5
Switch(config-cmap)# exit

                                              The following example shows how to configure a class-map on multiple match statements:

                                              Switch> enable
Switch# configure terminal
Switch(config)# class-map match-any IPP
Switch(config-cmap)# match ip precedence 3
Switch(config-cmap)# match ip precedence 4
Switch(config-cmap)# exit

                                              The following example shows how to a configure a class-map using match-all and match-any keywords:

                                              Switch> enable
Switch# configure terminal
Switch(config)# class-map match-any class1
Switch(config-cmap)# match vlan 100 200 400-500
Switch(config-cmap)# match cos 1
Switch(config-cmap)# exit
Switch(config)# class-map match-any class2
Switch(config-cmap)# match vlan 1000 1100-1120
Switch(config-cmap)# match cos 3
Switch(config-cmap)# exit

                                              The match-all criteria with multiple VLANs and CoS marking gets translated to a combination of match criteria. Therefore matching is based on the following incoming packet:

                                              VLAN 1000 AND COS 3
VLAN 1100-1200 AND COS 3

                                              The match-any criteria gets translated to individual match criteria. Therefore matching is based on VLAN 100, VLAN 200, VLAN 400-500, or COS 1.

                                              The following example shows how to configure a hierarchical ingress policy:

                                              Switch> enable
Switch# configure terminal
Switch(config)# class-map match-any childOR
Switch(config-cmap)# match cos 5
Switch(config)# policy-map testchildOR
Switch(config-pmap)# class childOR
Switch(config-pmap-c)# police cir percent 10
Switch(config)# policy-map parentOR
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police rate 500000
Switch(config-pmap-c)# service-policy testchildOR
Switch(config-pmap-c)# exit

                                              Configuring Ingress Policing

                                              The following example shows how to configure policing actions:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map ABC
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police 10000000 8000 8000
Switch(config-pmap-c-police)# conform-action set-cos-transmit 2
Switch(config-pmap-c-police)# exceed-action set-cos-transmit 1
Switch(config-pmap-c-police)# end

                                              The following example shows how to configure a single rate 2-color policer:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map 1r2c
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police 2000000
Switch(config-pmap-c-police)# conform-action transmit
Switch(config-pmap-c-police)# exceed-action drop
Switch(config-pmap-c-police)# end

                                              The following example shows how to configure a single rate, 2-color policer with percent:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map 1r2c_percent
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir percent 20
Switch(config-pmap-c-police)# conform-action set-cos-transmit 0
Switch(config-pmap-c-police)# exceed-action drop
Switch(config-pmap-c-police)# end

                                              The following example shows how to configure a dual rate, 3-color policer:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map 2r3c
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir 2000000 pir 3000000
Switch(config-pmap-c-police)# conform-action set-prec-transmit 3
Switch(config-pmap-c-police)# exceed-action set-prec-transmit 2
Switch(config-pmap-c-police)# violate-action set-prec-transmit 1
Switch(config-pmap-c-police)# end

                                              The following example shows how to configure a dual rate, 3-color policer with percent:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map 2r3c_percent
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir percent 10 pir percent 20
Switch(config-pmap-c-police)# conform-action transmit
Switch(config-pmap-c-police)# xceed-action set-cos-transmit 0
Switch(config-pmap-c-police)# violate-action drop
Switch(config-pmap-c-police)# end

                                              The following example shows how to configure a single rate, 2-color policer in class-default and a child policy:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map police5
Switch(config-pmap)# class test18
Switch(config-pmap-c)# service policy child-level
Switch(config-pmap-c)# police cir 64000 50
Switch(config-pmap-c-police)# end

                                              The following example shows how to configure a dual rate, 3-color policer configuration in a class and policy-map:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map test
Switch(config-pmap)# class cos2
Switch(config-pmap-c)# police 1000000 pir 2000000 conform-action set-cos-transmit 3 exceed-action set-cos-transmit 1 violate-action drop

                                              The following example shows how to configure a dual rate, 3-color policer in class-default with a CIR of 64 Kbps, and PIR doubled the CIR rate, a conform action of transmit, and an exceed action mark dscp af 11:

                                              Switch> enable
Switch# configure terminal
Switch(config)# olicy-map qos_test
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir 64000 bc 2000 pir 128000 be 2000 conform-action transmit exceed-action set-dscp-transmit af11 violate-action set-dscp-transmit cs1

                                              The following example shows how to configure a dual rate, 3-color policer in class-default:

                                              Switch> enable
Switch# configure terminal
Switch(config)# olicy-map qos_test
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# police cir 64000 bc 2000 pir 128000 be 2000 conform-action transmit exceed-action set-dscp-transmit af11 violate-action set-dscp- transmit cs1

                                              Attaching or Removing a QoS Traffic Policy for a Target

                                              The following example shows how to attach a traffic policy to a target:

                                              Switch> enable
Switch# configure terminal
Switch(config)# interface TenGigabitEthernet 0/45
Switch(config-if)# service instance 100 ethernet
Switch(config-if-srv-instance)# service-policy input policy1
Switch(config-if-srv-instance)# end

                                              The following example shows how to remove a traffic policy from a target:

                                              Switch> enable
Switch# configure terminal
Switch(config)# interface TenGigabitEthernet 0/45
Switch(config-if)# service instance 100 ethernet
Switch(config-if-srv-instance)# no service-policy input policy1
Switch(config-if-srv-instance)# end

                                              Configuring Ingress Marking

                                              The following example 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. This example configures marking to set the IP precedence value:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip precedence 1

                                              The following example shows how to configure marking to set the CoS value:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map test
Switch(config-pmap)# lass test
Switch(config-pmap-c)# set cos 1

                                              Configuring Egress Classification

                                              The following example shows how to create a class map:

                                              Switch> enable
Switch# configure terminal
Switch(config)# class-map c1
Switch(config-cmap)# match qos-group 1

                                              The following example shows how to configure priority queue at the egress:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map Test1
Switch(config-pmap)# class test
Switch(config-pmap-c)# priority 10000

                                              Configuring Egress Bandwidth

                                              The following example shows how to configure minimum bandwidth guarantee at the egress:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map Test
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# bandwidth 10000
Switch(config-pmap-c)# exit

                                              Configuring Egress Shaping

                                              The following example shows how to shape traffic on a main interface; traffic leaving interface gi36/1 is shaped at the rate of 10 Mb/s:

                                              Switch> enable
Switch# configure terminal
Switch(config)# class-map class-interface-all
Switch(config-cmap)# match qos-group 1
Switch(config-cmap)# exit
Switch(config)# policy-map dts-interface-all-action
Switch(config-pmap)# class class-interface-all
Switch(config-pmap-c)# shape average 10000000
Switch(config-pmap-c)# exit
Switch(config)# interface gi36/1
Switch(config-if)# service-policy output dts-interface-all-action

                                              Configuring Egress Bandwidth Remaining Ratio

                                              The following example shows how to configure bandwidth remaining ratio at the egress:

                                              Switch> enable
Switch# configure terminal
Switch(config)# policy-map BRR
Switch(config-pmap)# class Test1
Switch(config-pmap-c)# bandwidth remaining ratio 10
Switch(config-pmap-c)# exit
Switch(config-pmap)# class Test2
Switch(config-pmap-c)# bandwidth remaining ratio 20
Switch(config-pmap-c)# exit
Switch(config-pmap)# class Test3
Switch(config-pmap-c)# bandwidth remaining ratio 30
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class-default
Switch(config-pmap-c)# bandwidth remaining ratio 40

                                              Verifying the QoS Configuration

                                              Use the following show commands to verify the QoS configuration:
                                              • show class-map
                                              • show class-map class-map-name
                                              • show policy-map
                                              • show policy-map policy-map-name
                                              • show policy-map policy-map-name class class-name
                                              • show run class-map
                                              • show policy-map BRR
                                              • show policy-map interface interface type slot/port
                                              • show policy-map interface interface type slot/port service instance number

                                              Class Map

                                              Use the following command to show class-map information for a specific class map:

                                              Switch# show class-map ipp5
                                              class Map match-any ipp5 (id 1)
match ip precedence 5

                                              Use the following command to show class-map information for a specific class map using the show run class-map command:

                                              Switch# show run class-map
                                              Building configuration...
Current configuration : 275 bytes
!
class-map match-any EgressClassmap
match qos-group 3
class-map match-any IngressClassMap
match cos 1
end

                                              Policy Map

                                              Use the following command to show policy map information:

                                              Switch# show policy-map
                                              policy-map testchildOR
class childOR
police 100000000
policy-map parentOR
class class-default
police 500000000
service-policy testchildOR

                                              Use the following command to show information for a specific policy map:

                                              Switch# show policy-map ABC
                                              Policy Map ABC
class class-default
police cir 10000000 bc 8000 be 8000
conform-action set-cos-transmit 2
exceed-action set-cos-transmit 1

                                              Use the following command to verify the bandwidth remaining ratio at the egress:

                                              Switch# show policy-map BRR
                                              Building configuration...
Current configuration : 209 bytes
!
policy-map BRR
class Test1
bandwidth remaining ratio 10
class Test2
bandwidth remaining ratio 20
class Test3
bandwidth remaining ratio 30
class class-default
bandwidth remaining ratio 40
!
end

                                              Additional References for QoS

                                              The following sections provide references related to the QoS feature.

                                              Related Documents

                                              Related Topic Document Title

                                              Cisco IOS commands

                                              Cisco IOS Master Commands List, All Releases

                                              QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples

                                              Cisco IOS Quality of Service Solutions Command Reference

                                              Technical Assistance

                                              Description Link

                                              The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

                                              To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

                                              Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

                                              		 http:/​/​www.cisco.com/​cisco/​web/​support/​index.html

                                              Was this Document Helpful?

                                              FeedbackFeedback

                                              Contact Cisco

                                              Related Cisco Community Discussions

                                              About Us
                                              Contact Us
                                              Work with Us