hit counter script
Cisco Nexus 7000 Series Configuration Manual
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Switch
  5. Nexus 7000 Series
  6. Configuration manual

Cisco Nexus 7000 Series Configuration Manual

Nx-os quality of service configuration guide
Hide thumbs Also See for Nexus 7000 Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, Configuration Manual
Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide
Last Modified: 2016-05-11
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883

Advertisement

Table of Contents
loading

Related Manuals for Cisco Nexus 7000 Series

Summary of Contents for Cisco Nexus 7000 Series

  • Page 1 Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide Last Modified: 2016-05-11 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883...
  • Page 2 Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company.

  • Page 3: Table Of Contents

    Sequencing of Ingress Traffic Actions Sequencing of Egress Traffic Actions High Availability Requirements for QoS Features QoS Feature Configuration with MQC QoS Statistics Default QoS Behavior QoS Policies on Fabric Extenders Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 4 Prerequisites for Classification Guidelines and Limitations Configuring Traffic Classes Configuring ACL Classification Configuring a Deny ACE Configuring DSCP Classification Configuring IP Precedence Classification Configuring Protocol Classification Configuring QoS Group Classification Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 5 Configuration Examples for Marking Feature History for Marking C H A P T E R 6 Configuring Mutation Mapping Finding Feature Information Information About Mutation Mapping Licensing Requirements Prerequisites for Mutation Mapping Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 6 Information About Fabric QoS Mapping COS-to-Queue Fabric Mapping Ingress Buffer Policy Egress Queue Bandwidth Allocation Guidelines and Limitations Configuring Fabric QoS Mapping Copying a Default Policy Configuring Cos2q Fabric Mapping Configuring Ingress Buffer Policy Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 7 Configuring Tail Drop by COS Values Configuring Tail Drop by DSCP Values Configuring WRED by COS Values Configuring WRED by DSCP Values Configuring Congestion Management Configuring Bandwidth and Bandwidth Remaining Configuring Priority Configuring Shaping Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 8 Example: Verifying the Status of DSCP-to-queue Mapping Feature History for Queuing and Scheduling for F-Series Modules C H A P T E R 1 1 Configuring Network QoS Finding Feature Information Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide viii...
  • Page 9 C H A P T E R 1 3 Configuring Local Policy-Based Routing Finding Feature Information Information About Local Policy-Based Routing Route Maps Match Criteria Set Changes Licensing Requirements Prerequisites for Local Policy-Based Routing Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 10 A P P E N D I X A Configuration Limits for Quality of Service Configuration Features Configuration Limits for QoS A P P E N D I X B Additional References Appendix Related Documents RFCs Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 11 Audience, on page xi • Document Conventions, on page xi • Related Documentation for Cisco Nexus 7000 Series NX-OS Software, on page xii • Documentation Feedback, on page xiv • Obtaining Documentation and Submitting a Service Request, on page xv Audience This publication is for network administrators who configure and maintain Cisco Nexus devices.
  • Page 12 Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Related Documentation for Cisco Nexus 7000 Series NX-OS Software The entire Cisco Nexus 7000 Series NX-OS documentation set is available at the following URL: http://www.cisco.com/en/us/products/ps9402/tsd_products_support_series_home.html Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 13 • Cisco Nexus 7000 Series NX-OS Virtual Device Context Quick Start • Cisco Nexus 7000 Series NX-OS OTV Quick Start Guide • Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 • Cisco Nexus 2000 Series Fabric Extender Software Configuration Guide...
  • Page 14 • Cisco Nexus 7000 Series NX-OS Unicast Routing Command Reference • Cisco Nexus 7000 Series NX-OS Virtual Device Context Command Reference • Cisco NX-OS FCoE Command Reference for Cisco Nexus 7000 and Cisco MDS 9500 Other Software Documents You can locate these documents starting at the following landing page: http://www.cisco.com/en/us/products/ps9402/tsd_products_support_series_home.html...
  • Page 15 What's New in Cisco Product Documentation. To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in Cisco Product Documentation RSS feed. RSS feeds are a free service.
  • Page 16 Preface Obtaining Documentation and Submitting a Service Request Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 17: New And Changed Information

    Nexus 7718 switch only. Local Policy-Based Routing (PBR) You can now configure local 6.2(2) policy-based routing. default-nq-8e-4q4q- policy The default-nq-8e-4q4q-policy 6.1.3 template for F2 modules template supports four ingress buffers. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 18 You can now match IPv6, as well 4.1(2) as IPv4, addresses. Only same variable for mutation You can match only the same 4.1(2) mapping variable with different values for mutation mapping. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 19: Chapter

    C H A P T E R Overview This chapter describes the configurable Cisco NX-OS quality of service (QoS) features on the Cisco NX-OS device. QoS allows you to classify the network traffic, police and prioritize the traffic flow, and help avoid traffic congestion in a network.

  • Page 20: Using Qos

    Using QoS Caution Before you attempt a downgrade from Cisco NX-OS Release 5.2(x) or newer release to any release prior to Release 5.2(1), you should clear the QoS MIB and MPLS QoS defaults by using the clear qos mpls-snmp command. The downgrade might fail if the defaults are not cleared.

  • Page 21: Mutation

    The default type of policy is qos. The Cisco NX-OS device processes the QoS policies that you define based on whether they are applied to ingress or egress packets. The system performs actions for QoS policies only if you define them under the type qos service policies.

  • Page 22: Sequencing Of Ingress Traffic Actions

    High Availability Requirements for QoS Features The Cisco NX-OS QoS software recovers its previous state after a software restart, and it is capable of a switchover from the active supervisor to the standby supervisor without a loss of state.

  • Page 23: Qos Feature Configuration With Mqc

    The QoS queuing features are enabled by default. Specific QoS-type features, policing and marking, are enabled only when a policy is attached to an interface. Specific policies are enabled when that policy is attached to an interface. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 24: Qos Policies On Fabric Extenders

    Nexus 7000 Series switch. The FEX has 48 1-Gbps front-panel or server-facing ports, which are satellite ports. The FEX has four uplink ports that you can use to connect it to the Cisco Nexus 7000 Series switch. The four ports on the Cisco Nexus 7000 Series switch that connect to the uplink ports are fabric ports. Only QoS policies can be configured on the server-facing FEX ports.

  • Page 25: Using Modular Qos Cli

    Feature History table in this chapter. Information About MQC MQC provides a language to define QoS policies. For more information about MQC commands, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference. You configure QoS policies by following these three steps: 1.

  • Page 26: Licensing Requirements

    In interface configuration mode, the Cisco Nexus 7000 Series switch might accept QoS and ACL commands irrespective of the line card on which the interface host is up or down. However, you cannot enter interface submode when the line card is down because the Cisco Nexus 7000 Series switch does not accept any preconfiguration information.

  • Page 27: Using An Mqc Object

    Using Modular QoS CLI Using an MQC Object For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Using an MQC Object You configure QoS and queuing policies using the MQC class-map, policy-map, and table-map objects. You cannot use table maps in queuing policies.
  • Page 28 Figure 2: QoS Policy Diagram Showing Type qos MQC Object Usage Without Mutation Note The MQC objects are shown in bold. The figure below shows the QoS policy structure with mutation. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 29: Type Queuing Policies

    The figure below shows the QoS policy structure with associated MQC objects of type queuing. The MQC objects are shown in bold. Note MQC table-map objects cannot be used in policies of type queuing. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 30: System-Defined Mqc Objects

    See "Queuing and Scheduling" for more information on configuring these parameters. System-Defined MQC Objects Note The system-defined MQC objects that are shown in the table below are the default. All of these values apply across all VDCs. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 31 Type queuing class maps that are defined by the system are listed in the table below. Table 6: System-Defined Type queuing Class Maps Class Map Queue Name Description Default CoS Values 1 Gigabit Module Ingress: 2 queues with 4 thresholds per queue Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 32 These are either priority or normal queues. If you use the priority keyword in your configuration, these queues are used as priority queues. Otherwise, they are used as normal queues. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 33 Table map used to map the discard-class value to the CoS value. discard-class-prec-map Table map used to map the discard-class value to the precedence value. discard-class-dscp-map Table map used to map the discard-class value to the DSCP value. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 34: Configuring An Mqc Object

    When you specify an MQC object command, the device creates the object if it does not exist and then enters map mode. To remove a class-map, table-map, or policy-map object, use the no form of the command that you used to create the object. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 35: Configuring Or Modifying A Class Map

    | exceed-color-in | exceed-color-out} This command is only used when Note color-aware policing is required. Step 5 switch(config-color-map)# exit Exits color-map mode, and then enters global configuration mode. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 36: Configuring Or Modifying A Table Map

    Table map names can contain alphabetic, hyphen, or underscore characters, are case sensitive, and can be up to 40 characters. Step 3 switch(config-tmap)# exit Exits table-map mode and enters global configuration mode. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 37: Configuring Or Modifying A Policy Map

    Step 7 (Optional) switch(config)# show policy-map Displays information about all configured type queuing [policy-map-name | policy maps or a selected policy map of type queuing. qos-dynamic] Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 38: Applying Descriptions To Mqc Objects

    [match-first] {qos-policy-map-name then enters policy-map mode. The policy-map | qos-dynamic} name can contain alphabetic, hyphen, or underscore characters, is case sensitive, and can be up to 40 characters. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 39: Verifying An Mqc Object

    For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference. Attaching and Detaching a QoS Policy Action The software does not allow you to enable or disable QoS features with a configuration command.
  • Page 40 Table 8: System-Defined Queuing Policy Maps, on page The interface where a QoS policy is applied is summarized in the table below. Each row represents the interface levels. The entry descriptions are as follows: Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 41: Attaching A Qos Policy Action To An Interface Or Tunnel

    [type qos | queuing] [class [type qos interface. You can limit what the device displays to input or output policies, qos or | queuing] class-map-name] queuing polices, and to a specific class. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 42: Attaching A Qos Policy Action To A Vlan

    Session Manager Support for QoS Beginning in Cisco NX-OS Release 4.2, Session Manger supports the configuration of QoS. This feature allows you to verify the QoS configuration and confirm that the resources required by the configuration are available prior to committing them to the running configuration. For information about Session Manager, see the Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Release 6.x.
  • Page 43 Feature Information No changes from Release 5.1(1) — 4.2(1) Support for Session Manager 4.2(1) Allows you to verify the configuration and required resources prior to committing them to the running configuration. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 44 Using Modular QoS CLI Feature History for Using Modular QoS CLI Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 45: Configuring Classification

    C H A P T E R Configuring Classification This chapter describes how to configure classification on the Cisco NX-OS device. • Finding Feature Information, on page 29 • Information About Classification, on page 29 • Licensing Requirements, on page 31 •...
  • Page 46 You can reuse class maps within the same virtual device context (VDC) when defining the QoS policies for different interfaces that process the same types of traffic. Note For more information on class maps, see “Using Modular QoS CLI”. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 47: Licensing Requirements

    Cisco NX-OS system images and is provided at no extra charge to you. Using virtual device contexts (VDCs) requires an Advanced Services license. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Prerequisites for Classification Classification has the following prerequisites: •...

  • Page 48: Configuring Traffic Classes

    QoS does not use the permit-deny functions of ACLs. You can classify by either IPv4 or IPv6. Support is available for controlling deny access control entry ([no] hardware access-list allow deny ace) in the CLI. For more information about this support, see the Cisco Nexus 7000 Series NX-OS Security Configuration Guide. Note Tunneled IP packets are matched unless the tunneling protocol is also IP, and then the match applies to the outer IP header and not the encapsulated IP header.

  • Page 49: Configuring A Deny Ace

    Enables support for deny ACEs in a sequence. allow deny ace Step 3 (Optional) switch(config)# show Displays the ACL configuration. running-config aclmgr Step 4 (Optional) switch(config)# copy Saves this configuration change. running-config startup-config Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 50: Configuring Dscp Classification

    CS4 (precedence 4) dscp (100000)—decimal value CS5 (precedence 5) dscp (101000)—decimal value CS6 (precedence 6) dscp (110000)—decimal value CS7 (precedence 7) dscp (111000)—decimal value default Default dscp (000000)—decimal value 0 EF dscp (101110)—decimal value 46 Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 51: Configuring Ip Precedence Classification

    You can classify traffic based on the precedence value in the type of service (ToS) byte field of the IP header. The table below shows the precedence values. Table 12: Precedence Values Value List of Precedence Values IP precedence value critical Critical precedence (5) flash Flash precedence (3) Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 52 Step 5 (Optional) switch(config)# copy Saves this configuration change. running-config startup-config Example This example shows how to display the IP precedence class-map configuration: switch# show class-map class_ip_precedence Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 53: Configuring Protocol Classification

    Step 4 switch(config-cmap-qos)# exit Exits global class-map queuing mode, and enters configuration mode. Step 5 (Optional) switch(config)# copy Saves this configuration change. running-config startup-config Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 54: Configuring Qos Group Classification

    Step 5 (Optional) switch(config)# copy Saves this configuration change. running-config startup-config Example This example shows how to to display the QoS group class-map configuration: switch# show class-map class_qos_group Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 55: Configuring Discard Class Classification

    Configuring Layer 3 Packet Length Classification You can classify Layer 3 traffic based on various packet lengths. Note This feature is designed for IP packets only. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 56: Configuring Cos Classification

    Enters global configuration mode. Step 2 switch(config)# class-map [type qos] Creates or accesses the class map named [match-any | match-all] class-map-name class-map-name and enters class-map mode. The class map name can contain alphabetic, Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 57: Configuring Ip Rtp Classification

    Configures the traffic class by matching packets udp-port-value based on a range of lower and upper UDP port numbers, which is likely to target applications using RTP. Values can range from 2000 to 65535. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 58: Configuring Class Map Classification

    Because match-all is the default for the class-map command, the match criteria specified in class_map3 are ANDed with the match criteria in class_class_map. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 59: Verifying The Classification Configuration

    Your software release might not support all the features in this document. For the latest caveats and feature information, see the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your software release. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 60 Feature History for Classification Table 14: Feature History for Classification Feature Name Release Feature Information No changes from Release 5.1(1) — 4.2(1) Classification 4.2(1) You can now match IPv4 and IPv6 ACLs. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 61: Configuring Marking

    C H A P T E R Configuring Marking This chapter describes how to configure the marking features on the Cisco NX-OS device that you can use to define the class of traffic to which the packet belongs. • Finding Feature Information, on page 45 •...

  • Page 62: Licensing Requirements

    Cisco NX-OS system images and is provided at no extra charge to you. Using virtual device contexts (VDCs) requires an Advanced Services license. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Prerequisites for Marking Marking has the following prerequisites: •...

  • Page 63: Guidelines And Limitations

    You can combine one or more of the marking features in a policy map to control the setting of QoS values. You can then apply policies to either incoming or outgoing packets on an interface. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 64: Configuring Dscp Marking

    AF43 dscp (100110)—decimal value 38 CS1 (precedence 1) dscp (001000)—decimal value 8 CS2 (precedence 2) dscp (010000)—decimal value CS3 (precedence 3) dscp (011000)—decimal value CS4 (precedence 4) dscp (100000)—decimal value Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 65 DSCP value derives the CoS value for bridged and routed traffic from the 3 most significant DSCP bits. Example This example shows how to display the policy-map configuration: switch# show policy-map policy1 Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 66: Configuring Ip Precedence Marking

    Use the class-default keyword to select all traffic that is not currently matched by classes in the policy map. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 67: Configuring Cos Marking

    Sets the CoS value to cos-value. The value can range from 0 to 7. Example This example shows how to display the policy-map configuration: switch# show policy-map policy1 Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 68: Configuring Qos Group Marking

    You can set the value of the internal label discard class, which is locally significant only. You can reference this value in subsequent policy actions or classify traffic that is referenced in egress policies by using the match discard-class class-map command. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 69: Configuring Ingress And Egress Marking

    QoS policy map to an interface. To select ingress or egress, you specify either the input or output keyword in the service-policy command. For detailed instructions, see the “Attaching and Detaching a QoS Policy Action” section. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 70: Configuring Dscp Port Marking

    • You can attach only one policy type qos map to each interface in each direction. • The DSCP value is trust on the Layer 3 port of a Cisco NX-OS device. • If the default policy-map policy is used, DSCP maps to a relevant CoS value and the queuing works correctly.

  • Page 71: Configuring Table Maps For Use In Marking

    The ignore variable for the default command is no longer supported. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 72: Configuring Marking Using Table Maps

    Marking down in the police command requires the use of a table map. For information on the police command, see “Configuring Policing.” Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 73: Verifying The Marking Configuration

    Verifying the Marking Configuration To display the marking configuration information, perform one of the following tasks: Command Purpose show table-map Displays all table maps. show policy-map Displays all policy maps. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 74: Configuration Examples For Marking

    Table 19: Feature History for Marking Feature Name Release Feature Information set cos command 5.0(3) Support for set cos command in ingress policies. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 75: Configuring Mutation Mapping

    You use a hierarchical policy map to configure mutation mapping. In the mutation mapping policy map, you specify the field to mutate and the policy map to apply with the mutation. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 76: Licensing Requirements

    Cisco NX-OS system images and is provided at no extra charge to you. Using virtual device contexts (VDCs) requires an Advanced Services license. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Prerequisites for Mutation Mapping Mutation mapping has the following prerequisites: •...

  • Page 77: Guidelines And Limitations

    • You can use only like parameters (for example, cos-cos) when you create a mutation map. Mutation maps with dissimilar types (for example, cos-dscp) are not supported. • On Layer 2 ports, hierarchial QoS policies are not applicable on ingress for Cisco Nexus M3 series modules and Cisco Nexus F4 series modules.

  • Page 78: Verifying The Mutation Mapping Configuration

    Step 7 (Optional) switch(config-pmap-c-qos)# copy Saves the running configuration to the startup configuration. running-config startup-config Verifying the Mutation Mapping Configuration To display the mutation mapping configuration information, perform the following task: Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 79: Configuration Examples For Mutation Mapping

    Displays information about all configured policy maps [policy-map-name | qos-dynamic] or the specified policy map. For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference. Configuration Examples for Mutation Mapping...
  • Page 80 Table 20: Feature History for Mutation Mapping Feature Name Release Feature Information No changes from Release 5.1(1) —— 4.1(2) Mutation Mapping 4.1(2) You can only use similar variables for mutation mapping. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 81: Configuring Policing

    C H A P T E R Configuring Policing This chapter describes how to configure policing of traffic classes on the Cisco NX-OS device. • Finding Feature Information, on page 65 • Information About Policing, on page 65 • Shared Policers, on page 66 •...

  • Page 82: Shared Policers

    Cisco NX-OS system images and is provided at no extra charge to you. Using virtual device contexts (VDCs) requires an Advanced Services license. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Prerequisites for Policing Policing has the following prerequisites: •...

  • Page 83: Guidelines And Limitations

    • When the policer is applied on M1 or F2 modules having Layer 2 and Layer 3 traffic with MAC and IP access list, only the Layer 2 traffic matched with MAC access list is classified if the mac packet-classify command is enabled. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 84: Configuring Policing

    Gigabit per second (gbps) rate is not supported for this parameter. You must specify a value for pir before Note the device displays this argument. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 85 The policer actions that you can specify are described in the following two tables. Table 23: Policer Actions for Exceed or Violate Action Description drop Drops the packet. This action is available only when the packet exceeds or violates the parameters. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 86 The policer can only drop or mark down packets that exceed or violate the specified parameters. For information on marking down packets, see “Configuring Marking.” The data rates used in the police command are described in the table below. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 87 Use the class-default keyword to select all traffic that is not currently matched by classes in the policy map. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 88: Configuring Color-Aware Policing

    The policer then takes the following action: • Packets that belong to the conform-color class are policed with the cir and pir arguments to the police command. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 89 CS2 (precedence 2) dscp (010000)—decimal value CS3 (precedence 3) dscp (011000)—decimal value CS4 (precedence 4) dscp (100000)—decimal value CS5 (precedence 5) dscp (101000)—decimal value CS6 (precedence 6) dscp (110000)—decimal value Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 90 [match-first] {qos-policy-map-name | qos-policy-map-name, and then enters policy-map mode. The policy-map name can qos-dynamic} contain alphabetic, hyphen, or underscore characters, is case sensitive, and can be up to 40 characters. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 91: Configuring Ingress And Egress Policing

    QoS policy map to an interface. To select ingress or egress, you specify either the input or output keyword in the service-policy command. For more information on attaching and detaching a QoS policy action from an interface, see “Using Modular QoS CLI.” Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 92: Configuring Markdown Policing

    [type qos] [policy-map-name | qos-dynamic] policy maps or a selected policy map of type qos. Step 8 (Optional) switch(config)# copy Saves the running configuration to the startup running-config startup-config configuration. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 93: Configuring Shared Policers

    {peak-rate [data-rate] | percent cir-link-percent} [be peak-burst-rate The conform action is taken if the data rate is ≤ cir. If be and pir are not specified, all other [link-speed]] {{conform conform-action Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 94: Verifying The Policing Configuration

    This example shows how to display the test1 shared-policer configurations: switch# show qos shared-policer test1 Verifying the Policing Configuration To display the policing configuration information, perform one of these tasks: Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 95: Configuration Examples For Policing

    10 mbps pir 20 mbps conform transmit exceed set dscp dscp table cir-markdown-map violate drop policy-map type qos udp_policy class type qos udp_qos police aggregate udp_10mbps Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 96: Feature History For Policing

    Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your software release. Table 28: Feature History for Policing Feature Name Release Feature Information No changes from Release 5.1(1) —— 4.1(2) Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 97: Configuring Fabric Qos Mapping

    The Fabric QoS Mapping feature allows copying the default configuration and modifying the copied system queues that perform flow control on fabric traffic within the Cisco NX-OS device, thus enabling the choice of parameters for fabric queuing based on the network, traffic, and requirements for traffic prioritization.

  • Page 98: Ingress Buffer Policy

    • When you are working with fabric QoS mapping, all the ports on M Series modules much be allocated to the default VDC. • M3 modules do not support fabric QoS mapping. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 99: Configuring Fabric Qos Mapping

    {prefix | defined output policy with the specified prefix suffix} prefix-or-suffix-name or suffix. Configuring Cos2q Fabric Mapping Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 100: Configuring Ingress Buffer Policy

    Exits policy-map class system mode and enters global configuration mode. Configuring Egress Queue Bandwidth Allocation Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 101: Configuring The New User-Defined Policy On Fabric

    Step 5 switch(config-sys-mfab)# exit Exits system fabric mode and enters global configuration mode. Step 6 (Optional) switch(config)# show policy-map Displays information about the system fabric system fabric configuration. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 102: Configuration Examples For Fabric Qos Mapping

    Example: Verifying System Fabric Configuration The following sample output from the show policy-map system fabric command displays the input and output policy applied on fabric: Switch# show policy-map system fabric Service-policy (queuing) input: system-in-policy-in Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 103: Example: Verifying The Qos Mapping On Fabric

    60 class type queuing system-pq1 class type queuing system-q2 class type queuing system-q3 policy-map type queuing fab_out-system-out-policy class type queuing system-q-default Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 104: Feature History For Fabric Qos Mapping

    Table 30: Feature History for Fabric QoS Mapping Feature Name Release Feature Information Fabric QoS Mapping 6.2(2) This feature was introduced. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 105: Configuring Queuing And Scheduling On M-Series I/O Modules

    The queuing and scheduling processes allow you to control the bandwidth that is allocated to the traffic classes, so that you achieve the desired trade-off between throughput and latency for your network. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 106 DSCP-to-queue mapping is disabled by default. Use the hardware qos dscp-to-queue ingress command to enable DSCP mapping on the modules. The table below describes the system-defined DSCP queuing class-maps with the default DSCP values. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 107: Setting Ingress Port Cos

    For information about configuring class maps, see the “Modifying Queuing Class Maps for COS” section. Note Starting from Cisco NX-OS Release 6.2(2), DSCP-to-queue mapping on ingress class maps is supported on M Series 10G modules. However, the DSCP-to-queue mapping on all egress class maps is not supported.

  • Page 108: Congestion Avoidance

    VDC where the commands are entered. For information about configuring class maps, see the “Modifying Queuing Class Maps for COS” section. For information about configuring VDCs, see the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide.

  • Page 109: Prerequisites For Queuing And Scheduling

    • On Cisco M1 series modules, it may not be possible to configure actual values for traffic shaping. For example, on a 1 Gigabit interface with 65% average shaping, the output rate on the interface goes only up to 450Mbps, whereas with 70%, it goes to 850Mbps.

  • Page 110: Configuring Queuing And Scheduling

    Configuring Queuing and Scheduling on M-Series I/O Modules Configuring Queuing and Scheduling • The Cisco M3 series module supports only the network-qos template. This template contains all the CoS values that match the MTU size. • All data traffic will be enqueued to the default queue of dot1q-tunnel port because this port is untrusted by default.

  • Page 111: Configuring Ingress Port Cos

    50 bandwidth percent 20 If you copy and paste this configuration into any Cisco NX-OS release, the device sends errors while executing all the commands starting from the policy-map type queuing default-in-policy command. You can ignore these errors because they do not affect the performance of the device.

  • Page 112: Modifying Queuing Class Maps For Cos

    VDCs that use the modified class map. Note When you modify a system-defined class map, the changes occur immediately and might disrupt traffic on all VDCs that use the modified class map. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 113: Modifying Queuing Class Maps For Dscp

    To allow the modifications to be implemented, the DSCP-to-queue mapping must be enabled. If you have not enabled the DSCP-to-queue mapping earlier, you can use the hardware qos dscp-to-queue ingress module type command to enable DSCP-to-queue mapping. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 114: Configuring Congestion Avoidance

    You can configure congestion avoidance with tail drop or WRED features. Both features can be used in ingress and egress policy maps. Note WRED and tail drop cannot be configured in the same class. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 115: Configuring Tail Drop By Cos Values

    1 to 100. Note Repeat Step 4 to assign tail drop thresholds for other CoS values. Repeat Steps 3 through 5 to assign tail drop thresholds for other queue classes. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 116: Configuring Tail Drop By Dscp Values

    Displays information about all configured type queuing [policy-map-name policy maps or a selected policy map of type queuing. Step 7 (Optional) switch(config)# copy Saves the running configuration to the startup running-config startup-config configuration. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 117: Configuring Wred By Cos Values

    The minimum and maximum thresholds must be of the same type. If no aggregate arguments are supplied, no aggregate WRED is configured. The default threshold is in packets. The thresholds are from Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 118: Configuring Wred By Dscp Values

    You cannot configure WRED on ingress 10-Gigabit Ethernet ports except for the 8-port 10-Gigabit Ethernet I/O module. You can configure WRED thresholds by the DSCP value, and configure a single WRED threshold to use on all DSCP values that you do not specifically configure. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 119 | ms | us] | percent min-percent-of-qsize}} The minimum and maximum thresholds must Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 120: Configuring Congestion Management

    When a guaranteed bandwidth is configured, the priority queue must be disabled in the same policy map. Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 121: Configuring Priority

    By default, the device evenly distributes the remaining bandwidth among the nonpriority queues. Note When a priority queue is configured, the other queues can only use the remaining bandwidth in the same policy map. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 122: Configuring Shaping

    Configuring Shaping Note The device forces the shape rate to the closest value in the following percentage intervals: 100, 50, 33, 25, 12.5, 6.25, 3.13, or 1.07. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 123 [policy-map-name | policy maps or a selected policy map of type queuing. que-dynamic] Step 7 (Optional) switch(config)# copy Saves the running configuration to the startup configuration. running-config startup-config Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 124: Configuring Queue Limits

    [policy-map-name | policy maps or a selected policy map of type que-dynamic] queuing. Step 8 (Optional) switch(config)# copy Saves the running configuration to the startup running-config startup-config configuration. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 125: Enabling Dscp To Queue Mapping

    Displays queuing information about the specified slot/port[.subinterface [module | summary] interface. For more information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 126: Configuration Examples For Queuing And Scheduling

    1p3q4t-out-pq1 priority class type queue 1p3q4t-out-q2 bandwidth remaining percent 60 queue-limit 1 mbytes class type queue 1p3q4t-out-q3 bandwidth remaining percent 40 queue-limit 2 mbytes Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 127: Example: Shaping And Tail Drop Configuration

    50 random-detect dscp-based random-detect dscp 5 minimum-threshold percent 10 maximum-threshold percent 30 random-detect dscp 6 minimum-threshold percent 40 maximum-threshold percent 60 class type queuing 8q2t-in-q2 bandwidth percent 25 Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 128: Example: Verifying The Status Of Dscp-To-Queue Mapping

    Updated the System-Defined Queue Types table with new system-defined queue types for 4q8q policy templates on the Cisco Nexus 7710 switch and the Cisco Nexus 7718 switch. No change from Release 5.1(1) — 4.1(2) Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 129: Configuring Queuing And Scheduling On F-Series I/O Modules

    In the ingress direction, either two or four queues (buffer pools) are formed depending on the policy template. In the egress direction, there are four physical queues for qos policy templates on Cisco Nexus 7000 Series devices, except on the Cisco Nexus 7710 switch and Cisco Nexus 7718 switch, where, beginning with Cisco Release 6.2(2), there is support for eight physical queues.

  • Page 130: Ingress Queuing

    Table 34: Predefined Class Maps for Ingress Queuing Ingress Policy Maps Ingress Class Map Names default-4q-8e-in-policy 2q4t-8e-in-q1 and 2q4t-8e-in-q-default default-4q-7e-in-policy 4q4t-7e-in-q1, 4q4t-7e-in-q-default, 4q4t-7e-in-q3, and 4q4t-7e-in-q4 default-4q-6e-in-policy 4q4t-6e-in-q1, 4q4t-6e-in-q-default, 4q4t-6e-in-q3, and 4q4t-6e-in-q4 Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 131 A network administrator user role is required to change CoS to IVL. Starting with the Cisco NX-OS 6.1 release, DSCP to IVL is supported on F2 modules, in the ingress direction, using the match dscp command with the 2q4t-8e-in-q1 class map and the 2q4t-8e-in-q-default class map.
  • Page 132 CoS value of the packet, including non-IP packets. If a CoS value does not exist, then all packets are accepted as CoS 0. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 133 DSCP values. Commands Description class-map type queuing match-any 2q4t-8e-in-q1 The values set by the match dscp command are displayed by the show run command. match cos 5-7 match dscp 40-45 Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 134 (CoS) that the peer sends. For more information about the bandwidth command, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference.
  • Page 135 8e 2q4t-8e-4q4q-in-q-default 0-39 2q4t-8e-4q4q-in-q1 40-63 default-nq-8e-4q4q-policy template 8e-4q4q 4q1t-8e-4q4q-in-q-default 0-15 4q1t-8e-4q4q-in-q1 40-63 4q1t-8e-4q4q-in-q3 24-39 4q1t-8e-4q4q-in-q4 16-23 Similarly, the default dscp values are mapped for ingress queues for Cisco 7710/7718 switches. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 136: Egress Queuing

    • Egress queues have a fixed size and are not user configurable. • The egress port has four queues, except for the Cisco Nexus 7710 switch and the Cisco Nexus 7718 switch, whereby, beginning with Cisco Release 6.2(2), has support for eight queues (4q8q mode).
  • Page 137 You can modify the bandwidth percentage, priority level, and shaper for a given port. You use the bandwidth command to control the bandwidth allocated to an egress queue (traffic class). For more information about the bandwidth command, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference.

  • Page 138: Shared Buffer Queuing On The F3 Series Module

    To achieve a smooth output rate, the excess packets are retained in the queue and then scheduled for transmission later. For more information about the shape command, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference.

  • Page 139: Prerequisites For Queuing And Scheduling

    (applicable for all types of interfaces, such as access, trunk, routed, and so on). • Egress policies on VLAN configurations do not support set match on CoS. • Egress policies on VLAN configurations do not support set QoS group or discard class. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 140 (ISSD). If an ISSD is not performed, unexpected results might occur. • The clear qos policies 8e-4q4q command is only supported in the default VDC. Using this command in the default VDC also clears the 8e-4q4q policy-maps in non-default VDCs. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 141 • The default 4q8q-policy templates are supported on F2e modules only. • DSCP queuing is enabled by default on the Cisco Nexus 7710/7718 switches. You must use the no hardware qos dscp-to-queue command to disable DSCP queuing on the switch. You can use the hardware qos dscp-to-queue command module type command to reenable DSCP queuing.

  • Page 142: Configuring Queuing And Scheduling

    • All data traffic will be enqueued to the default queue of dot1q-tunnel port because this port is untrusted by default. • Starting with Cisco NX-OS Release 8.0(1), the dscp-to-queue mapping for M3-Series modules is enabled by using the hardware qos dscp-to-queue ingress module type f-series command.
  • Page 143 [policy-map-name] queuing. Step 11 (Optional) switch(config)# show policy-map Displays information about the service policy interface ethernet [slot/port] on an Ethernet interface. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 144: Configuring An Egress Queuing Policy

    Applies a policy to an interface. input [policy-map-name] Step 11 (Optional) switch(config)# show policy-map Displays information about all configured type queuing [policy-map-name] policy maps or a selected policy map of type queuing. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 145: Enabling Dscp To Queue Mapping

    50:50 for dedicated:shared queues. The default value for shared buffer queuing is disabled. Use the no form of this command to disable shared buffer queuing on the specified module. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 146: Verifying The Queuing And Scheduling Configuration

    F-Series module and M3 interface because these policies will be inconsistent with the new network QoS template. For more information about the fields in the output of these commands, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference document.

  • Page 147: Configuration Examples For Queuing And Scheduling On F-Series Modules

    1q3p1t-6e-out-pq3 priority level 2 policy-map type queuing p-4que-6e-out class type queuing c-4q-6e-drop-out service-policy type queuing p-4que-6e-drop-out bandwidth percent 70 class type queuing c-4q-6e-ndrop-out service-policy type queuing p-4que-6e-ndrop-out bandwidth percent 30 Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 148: Example: Hierarchical Queuing Policy Configuration

    Your software release might not support all the features in this document. For the latest caveats and feature information, see the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your software release. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 149 6.1(1) Support for DSCP mapping for F2 modules. modules Scheduling and Queuing for 5.1(1) This chapter was added. (Chapter title F1 Series Modules subsequently changed to accommodate other F-Series Modules.) Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 150 Configuring Queuing and Scheduling on F-Series I/O Modules Feature History for Queuing and Scheduling for F-Series Modules Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 151: Configuring Network Qos

    C H A P T E R Configuring Network QoS This chapter describes how to configure a network qos policy for the Cisco NX-OS device in the Data Center Bridging (DCB) network. Note This chapter applies to the F-Series I/O modules only.

  • Page 152: Differences In Drop Cos And No-Drop Cos Values

    The table below shows the drop and no-drop CoS values for the different policy templates. Table 37: Differences in Drop CoS and No-Drop CoS Values Templates default-4q-8e-policy 0–7 — default-4q-7e-policy 0–2, 4–7 default-4q-6e-policy 0–2, 5–7 3, 4 Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 153: Queue Names And Default Mappings Of Cos Values To Egress/Ingress Queues

    Value Values default-4q-8e-policy 2q4t-8e-in-q1 5–7 1p3q1t-8e-out-pq1 5–7 5–7 2q4t-8e-in-q- 0–4 1p3q1t-8e-out-q2 3–4 default 1p3q1t-8e-out-q3 1p3q1t-8e-out-q- default default-4q-7e-policy 4q4t-7e-in-q1 5–7 1p3q1t-7e-out-pq1 5–7 5–7 4q4t-7e-in-q-default 0–1 1p3q1t-7e-out-q2 4q4t-7e-in-q3 1p3q1t-7e-out-q3 4q4t-7e-in-q4 1p3q1t-7e-out-q- default Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 154 1p3q1t-8e-4q4qout- q-default default-8e-4q8q-policy 8e-4q8q-in-q1 5–7 8e-4q8q-out-q1 (Cisco Nexus 7710/ (priority 8e-4q8q-in-q-default 0–4 (Drop 7718 switches only) queue) category) 8e-4q8q-in-q3 — 8e-4q8q-out-q2 8e-4q8q-in-q4 — 8e-4q8q-out-q3 8e-4q8q-out-q4 8e-4q8q-out-q5 8e-4q8q-out-q6 8e-4q8q-out-q7 8e-4q8q-out-q- default Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 155 (priority queue) 6e-4q8q-in-q-default 6e-4q8q-out-q2 6e-4q8q-out-q3 6e-4q8q-out-q6 6e-4q8q-out-q7 6e-4q8q-out-q- default default-6e-4q8qndrop- default-6e-4q8qndrop- 4 (no drop in-policy: out-policy: category, highest 6e-4q8q-in-q3 6e-4q8q-out-q4 priority) (priority queue) 6e-4q8q-in-q4 3 (2nd 6e-4q8q-out-q5 highest (priority queue) priority) Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 156: Default Dscp Mappings

    (priority queue) 4e-4q8q-out-q5 4e-4q8q-out-q6 4e-4q8q-out-q7 Default DSCP Mappings The table below shows the default DSCP values to Ingress queues for the Cisco Nexus 7710/7718 switches. Table 39: Default DSCP Mappings on Cisco Nexus 7710/7718 Switches Template Ingress Queue Default DSCP Mappings...

  • Page 157: Licensing Requirements

    In a default network policy template name, the numbers 4, 6, 7, and 8 denote the number of the drop CoS that is defined in the policy and e denotes Ethernet. Note The 4q8q policy templates are supported and enabled by default on the Cisco Nexus 7710 switch and the Cisco Nexus 7718 switch only. Note...

  • Page 158: Guidelines And Limitations

    • When the port MTU is configured on an interface, it overrides the network qos MTU. • In releases earlier than Cisco NX-OS Release 6.2(1), the Fabric Extender (FEX) interfaces do not support the MTU changes made to a QoS policy template.

  • Page 159: Configuring Network Qos Policies

    | suffix suffix} underscore characters, is case sensitive, and can be up to 40 characters. Step 3 switch(config)# show policy-map type Displays the type network qos policy map. network-qos Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 160: Configure A User-Defined Network

    | tail-drop{threshold [burst-optimized | mesh-optimized]}] Step 14 switch(config-pmap-nqos-c)# class type Configures the class map of type network-qos network-qos and specifies the class map name. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 161: Applying A Network Qos Policy On A Target

    Displays the active type network qos class maps. show policy-map system type network-qos For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 162: Configuration Examples For Network Qos

    Cisco Nexus 7718 switch only. Support for four ingress 6.1(3) Support for the default-8e-4q4q-policy buffers template that supports four ingress buffers. network-qos policy 5.1(1) This feature was introduced. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 163: Configuring Priority Flow Control

    C H A P T E R Configuring Priority Flow Control This chapter describes how to configure priority flow control (PFC) on the Cisco NX-OS device. • Finding Feature Information, on page 147 • Information About Priority Flow Control, on page 147 •...

  • Page 164: Licensing Requirements

    Cisco NX-OS system images and is provided at no extra charge to you. Using virtual device contexts (VDCs) requires an Advanced Services license. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Prerequisites for Priority Flow Control PFC has the following prerequisites: •...

  • Page 165: Default Settings For Priority Flow Control

    {auto | off | on} default, PFC mode is set to auto on all ports. Step 4 (Optional) switch(config-if)# show interface Displays the status of PFC on all interfaces. priority-flow-control Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 166: Verifying The Priority Flow Control Configuration

    Displays the status of PFC on all interfaces. show interface priority-flow-control For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference. Configuration Examples for Priority Flow Control...

  • Page 167: Configuring Local Policy-Based Routing

    C H A P T E R Configuring Local Policy-Based Routing This chapter describes how to configure local policy-based routing (PBR) on the Cisco NX-OS device. • Finding Feature Information, on page 151 • Information About Local Policy-Based Routing, on page 151 •...

  • Page 168: Route Maps

    Match Criteria You can use a variety of criteria to match a route or IP packet in a route map. When Cisco NX-OS processes a route or packet through a route map, it compares the route or packet to each of the match statements configured.

  • Page 169: Prerequisites For Local Policy-Based Routing

    • Assign an IP address on the interface and bring the interface up before you apply a route map on the interface for policy-based routing. • If you configure VDCs, install the appropriate license and enter the desired VDC (see the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide for configuration information and the Cisco NX-OS Licensing Guide for licensing information).

  • Page 170: Configuring Local Policy-Based Routing

    Command or Action Purpose Step 1 [no] set precedence {number | name} Sets the IPv6 precedence for policy-based routing. The options are as follows: • 0—routine • 1—priority • 2—immediate • 3—flash Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 171: Enabling The Policy-Based Routing Feature

    Step 3 switch(config)# [no] ipv6 local policy Assigns a route map for local policy-based routing to the interface. route-map map-name Use the no form of this command to disable the feature. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 172: Verifying The Local Policy-Based Routing Configuration

    Displays information about the local IPv6 policy. show route-map name Displays information about a route map. For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference. Configuration Example for Local Policy-Based Routing...

  • Page 173: Monitoring Qos Statistics

    C H A P T E R Monitoring QoS Statistics This chapter describes how to enable, display, and clear QoS statistics on the Cisco NX-OS device. • Finding Feature Information, on page 157 • Information About QoS Statistics, on page 157 •...

  • Page 174: Prerequisites For Monitoring Qos Statistics

    Saves the running configuration to the startup running-config startup-config configuration. Monitoring the Statistics You can display QoS statistics for all interfaces or a selected interface, data direction, or a QoS type. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 175: Clearing Statistics

    5 minute offered rate 0 bps, drop rate 0 bps Match: precedence 5 police cir 20 mbps bc 200 ms conformed 0 bytes, 0 bps action: transmit violated 0 bytes, 0 bps action: drop Class-map (qos): map3 (match-all) Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 176 The value of the counter must be non zero. The current depth indicates that there are packets waiting in the buffer to be forwarded. The value of the current depth is in bytes. For complete information on the show policy-map command, see the Cisco Nexus 7000 Series NX-OS Quality of Service Command Reference.

  • Page 177: Feature History For Statistics

    Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your software release. Table 45: Feature History for Statistics Feature Name Release Feature Information No changes from Release 5.1(1) — 4.1(2) Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 178 Monitoring QoS Statistics Feature History for Statistics Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 179: Configuration Limits For Quality Of Service Configuration Features

    Configuration Limits for Quality of Service Configuration Features • Configuration Limits for QoS, on page 163 Configuration Limits for QoS The configuration limits are documented in the Cisco Nexus 7000 Series NX-OS Verified Scalability Guide. Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...
  • Page 180 Configuration Limits for Quality of Service Configuration Features Configuration Limits for Quality of Service Configuration Features Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

  • Page 181: Additional References Appendix

    A P P E N D I X Additional References Appendix This appendix contains additional information related to implementing QoS on the Cisco NX-OS device. This appendix includes the following sections: • Related Documents, on page 165 • RFCs, on page 165...
  • Page 182 Additional References Appendix RFCs Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide...

Table of Contents