Cisco Nexus 9000 Series Configuration Manual
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Switch
  5. Nexus 9000 Series
  6. Configuration manual

Cisco Nexus 9000 Series Configuration Manual

Nexus 9000 series data center switches
Hide thumbs Also See for Nexus 9000 Series:
Table of Contents

Advertisement

Quick Links

See also: Troubleshooting Manual , Configuration Manual
Cisco Nexus 9000 Series NX-OS Quality of Service Configuration
Guide, Release 7.x
First Published: 2015-01-31
Last Modified: 2017-01-31
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 9000 Series

Summary of Contents for Cisco Nexus 9000 Series

  • Page 1 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x First Published: 2015-01-31 Last Modified: 2017-01-31 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 This product includes software written by Tim Hudson (tjh@cryptsoft.com). http:// 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: www.cisco.com/go/trademarks .

  • Page 3: Table Of Contents

    High Availability Requirements for QoS Features QoS Feature Configuration with MQC QoS Statistics Default QoS Behavior Virtual Device Contexts Using Modular QoS CLI C H A P T E R 3 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 4 About QoS TCAM Carving About QoS TCAM Lite Regions Guidelines and Limitations Configuring QoS TCAM Carving Enabling Layer 3 QoS (IPv6) Enabling VLAN QoS (IPv4) Enabling FEX QoS (IPv4) Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 5 Licensing Requirements for Marking Prerequisites for Marking Guidelines and Limitations Configuring Marking Configuring DSCP Marking Configuring IP Precedence Marking Configuring CoS Marking Configuring CoS Marking for FEX Configuring DSCP Port Marking Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 6 Configuring Tail Drop on Egress Queues Configuring WRED on Egress Queues Configuring AFD on Egress Queues Configuring Congestion Management Configuring Bandwidth and Bandwidth Remaining Configuring Bandwidth and Bandwidth Remaining for FEX Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 7 How to Configure Link Level Flow Control Configuring Link Level Flow Control Receive Configuring Link Level Flow Control Transmit Configuration Examples for Link Level Flow Control Example: Configuring a No-Drop Policy Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 8 Clearing Micro-Burst Detection Verifying Micro-Burst Detection Example of Micro-Burst Detection Output FEX QoS Configuration A P P E N D I X A FEX QoS Configuration Information Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x viii...
  • Page 9 Contents TCAM Carving for FEX QoS FEX QoS Configuration Example Verifying the FEX QoS Configuration Additional References A P P E N D I X B RFCs Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 10 Contents Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 11: Preface

    • Documentation Feedback, page xii • Obtaining Documentation and Submitting a Service Request, page xiii Audience This publication is for network administrators who install, configure, and maintain Cisco Nexus switches. Document Conventions Command descriptions use the following conventions: Convention Description...

  • Page 12: Related Documentation For Cisco Nexus 9000 Series Switches

    An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line. Related Documentation for Cisco Nexus 9000 Series Switches The entire Cisco Nexus 9000 Series switch documentation set is available at the following URL: http://www.cisco.com/en/US/products/ps13386/tsd_products_support_series_home.html Documentation Feedback To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus9k-docfeedback@cisco.com.

  • Page 13: Obtaining Documentation And Submitting A Service Request

    Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
  • Page 14 Preface Obtaining Documentation and Submitting a Service Request Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 15: New And Changed Information

    New and Changed Information, page 1 New and Changed Information This table summarizes the new and changed features for the Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide and where they are documented. Table 1: New and Changed Features...
  • Page 16 Changed the behavior of the no 7.0(3)I4(2) Guidelines and Limitations for lldp tlv-select dcbxp command Priority Flow Control such that PFC mode will be disabled for interfaces on both sides of back-to-back switches. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 17 Enabling Egress QoS (IPv4) TCAM carving. Egress policing support Added support to apply the 7.0(3)I1(1) Configuring Ingress and Egress policing instructions in a QoS Policing policy map to egress packets. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 18 New and Changed Information New and Changed Information Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 19: Overview

    • QoS policies include policing features. • QoS policies include shaping, weighted random early detection (WRED), and explicit congestion notification (ECN) features. • Queuing policies use the queuing and scheduling features. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 20: Using Qos

    COS, IP precedence and DSCP, and internal labels (such as QoS groups) that can be used in subsequent actions. Marking QoS groups is used to identify the traffic type for queuing and scheduling traffic. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 21: Policing

    The system performs actions for QoS policies only if you define them under the type qos service policies. Sequencing of Ingress Traffic Actions The sequence of QoS actions on ingress traffic is as follows: 1 Classification 2 Marking 3 Policing Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 22: Sequencing Of Egress Traffic Actions

    1 Queuing and scheduling 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 Statistics

    Virtual Device Contexts Cisco NX-OS can segment operating system and hardware resources into virtual device contexts (VDCs) that emulate virtual devices. The Cisco Nexus 9000 Series device currently does not support multiple VDCs. All device resources are managed in the default VDC.
  • Page 24 Overview Virtual Device Contexts Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 25: About Mqc

    • policy-map—Defines a policy map that represents a set of policies to be applied on a class-by-class basis to class maps. The policy map defines a set of actions to take on the associated traffic class, such as limiting the bandwidth or dropping packets. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 26: System Classes

    4q mode or system-defined objects for 8q mode. On the Cisco Nexus device, a system class is uniquely identified by a qos-group value. A total of four system classes are supported. The device supports one default class which is always present on the device. Up to three additional system classes can be created by the administrator.

  • Page 27: Licensing Requirements For Using Mqc Objects

    The reserved class map class-default receives all traffic that is not matched in type qos policies, and the device applies the policy actions as it would for any other traffic class. Type qos Policies You use type qos policies to mark and to police packets. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 28: Type Queuing Policies

    Figure 1: QoS Policy Diagram Showing Type qos MQC Object Usage Type Queuing Policies You use type queuing policies to shape and queue packets. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 29: System-Defined Mqc Objects

    System-Defined MQC Objects When you configure QoS features, and the system requests MQC objects, you can use system-defined objects for 4q mode or system-defined objects for 8q mode. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 30: System-Defined Mqc Objects For 4Q Mode

    When you configure QoS features, and the system requests MQC objects, you can use the following system-defined objects: The Cisco Nexus 9000 series NX-OS system operates in 4q mode by default. System-defined MQC objects Note for 4q mode are the default MQC objects.
  • Page 31 1 class type queuing c-out-q2 bandwidth remaining percent 0 class type queuing c-out-q1 bandwidth remaining percent 0 class type queuing c-out-q-default bandwidth remaining percent 100 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 32: System-Defined Mqc Objects For 8Q Mode

    • Type queuing class maps Table 9: System-Defined Type queuing Class Maps for 8q Mode (Egress) Class Map Queue Name Description c-out-8q-q-default Egress default queue — QoS group 0 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 33 Table 11: System-Defined Type network-qos Class Maps for 8q Mode Class Map Network-QoS Description Name c-8q-nq-default Network-qos class — QoS group 0 c-8q-nq1 Network-qos class — QoS group 1 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 34 0 class type queuing c-out-8q-q2 bandwidth remaining percent 0 class type queuing c-out-8q-q1 bandwidth remaining percent 0 class type queuing c-out-8q-q-default bandwidth remaining percent 100 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 35: Changing To 8Q Mode

    0 mtu 1500 Changing to 8q Mode The Cisco Nexus 9000 series NX-OS system operates in 4q mode by default. Note Use the following guidelines to change to 8q mode: • Change the network-qos policy to 8q mode.

  • Page 36: Notes About 8Q Mode

    Example of Changing to 8q Mode The following is an example of changing to 8q mode: switch# qos copy policy-map type network-qos default-8q-nq-policy prefix my switch# show policy-map type network-qos Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 37 %IPQOSMGR-2-QOSMGR_NETWORK_QOS_POLICY_CHANGE: Policy my8q-nq is now active switch(config-sys-qos)# show policy-map system type network-qos Type network-qos policy-maps ============================ policy-map type network-qos my8q-nq class type network-qos c-8q-nq7 match qos-group 7 mtu 1500 class type network-qos c-8q-nq6 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 38 10 switch(config-pmap-c-que)# show policy-map type queuing my8q-out Type queuing policy-maps ======================== policy-map type queuing my8q-out class type queuing c-out-8q-q7 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 39: Example Of Set Qos-Groups

    4 switch(config-pmap-c-qos)# ex switch(config-pmap-qos)# class c3 switch(config-pmap-c-qos)# set qos-group 7 switch(config-pmap-c-qos)# ex switch(config-pmap-qos)# ex switch(config)# show policy-map p1 Type qos policy-maps Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 40: Changing From 8Q Mode To 4Q Mode

    To remove a class-map or policy-map object, use the no form of the command that you used to create the object. Configuring or Modifying a Class Map You can create or modify a class map. You can then reference class maps in policy maps. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 41 Example: switch(config)# class-map type queuing match-any c-out-q2 switch(config-cmap-que)# Step 5 exit Exits class map queuing mode and enters global configuration mode. Example: switch(config-cmap-que)# exit switch(config)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 42: Configuring Or Modifying A Policy Map

    Creates or accesses the policy map of type qos and then enters policy-map-name} policy-map mode. Policy-map names can contain alphabetic, hyphen, or underscore characters, are case sensitive, and can be up to 40 characters. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 43: Applying Descriptions To Mqc Objects

    (Optional) Saves the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Applying Descriptions to MQC Objects You can use the description command to add a description to a MQC object. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 44 40 characters. Example: • Class-map: switch(config-cmap)# class-map class1 switch(config-cmap)# • Policy-map: switch(config)# policy-map policy1 switch(config-pmap)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 45: Verifying An Mqc Object

    Displays information about all configured policy maps, all policy maps of type queuing, a selected | default-out-policy]] policy map of type queuing, or the default output queuing policy. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 46: Attaching And Detaching A Qos Policy Action

    • Present or not—Interface where a policy is either attached or not, but not applied. Table 13: QoS Policy Interfaces Port Policy Port-Channel Policy VLAN Policy Applied Not present Present or not Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 47: Configuring A Service Policy For A Layer 2 Interface

    Step 2 interface interface slot/port Enters configuration interface mode. Example: switch(config)# interface ethernet 1/1 switch(config-if)# Step 3 Selects the Layer 2 interface. switchport Example: switch(config-if)# switchport Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 48: Configuring A Service Policy For A Layer 3 Interface

    2. interface interface slot/port 3. no switchport 4. service-policy type {qos input | queuing output} policy-map-name [no-stats] 5. show policy-map interface interface slot/port type {qos | queuing} 6. copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 49: Attaching The System Service Policy

    Example: switch(config)# copy running-config startup-config Attaching the System Service Policy The service-policy command specifies the system class policy map as the service policy for the system. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

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

    Attaching a QoS Policy Action to a VLAN Before You Begin Ensure that the ternary content-addressable memory (TCAM) is carved for VLAN QoS. For more details, see the QoS TCAM carving chapter. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 51 Example: switch(config)# show policy-map vlan 2 Step 5 (Optional) Saves the running configuration to the startup copy running-config startup-config configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 52: Session Manager Support For Qos

    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 9000 Series NX-OS System Management Configuration Guide.

  • Page 53: Chapter 4 Configuring Qos Tcam Carving

    256 entries actually consumes 512 physical TCAM entries. On Cisco Nexus 9200 Series switches, the egress TCAM size is 2K, and the ingress TCAM size is 4K. The concepts of TCAM slices and single- and double-wide regions do not apply to these switches. For example, the ing-ifacl region can host IPv4, IPv6, or MAC type entries.
  • Page 54 Configuring QoS TCAM Carving About QoS TCAM Carving In addition to the above TCAM, for ALE enabled devices, a separate TCAM in the Cisco Nexus C9396PX Note (uplink ports) and Cisco Nexus C93128TX (uplink ports) ASIC is used for the QoS classification policies applied on 40G uplink ports.

  • Page 55: About Qos Tcam Lite Regions

    * The region is applicable only for ALE enabled devices and are required for classification policies applied Note on 40G uplink ports. ** The region is applicable only for 100G enabled devices (such as the Cisco Nexus 9300 Series switch Note with the N9K-M4PC-CFP2 GEM or the Cisco Nexus 9500 Series switch with the N9K-X9408PC-CFP2 line card) and are required for classification policies and QoS scheduling applied on 100G uplink ports.

  • Page 56: Guidelines And Limitations

    • show commands with the internal keyword are not supported. • After TCAM carving, you must save the configuration and reload the switch. • Cisco Nexus 9200 Series switches and Cisco Nexus 9300-EX Series switches are of the same type and therefore, they have the same TCAM regions.
  • Page 57 Configuring QoS TCAM Carving Guidelines and Limitations that are associated with the QoS classifications on the ALE ports and it is only supported on Cisco Nexus 9000 Series switches with Application Leaf Engine (ALE). For example, for Layer 2 Application Leaf Engine (ALE) port with IPv4 traffic, qos, and ns-qos TCAM carving is a must for the QoS classification to work.

  • Page 58: Configuring Qos Tcam Carving

    You can change the default QoS TCAM carving to accommodate your network requirements. The following sections contain examples of how to change the default QoS TCAM carving. You can use this procedure for all Cisco Nexus 9200, 9300, and 9500 Series switches and the Cisco Nexus Note The examples do not apply to NFE2-enabled devices (such as the X9432C-S 100G line card and the C9508-FM-S fabric module), which must use TCAM templates to configure TCAM region sizes.
  • Page 59 Configuring QoS TCAM Carving Enabling Layer 3 QoS (IPv6) Table 18: Default TCAM Region Configuration (Ingress) - For Layer 2-to-Layer 3 Configurations on Cisco Nexus 9200 Series Switches Region Name Size Width Total Size Ingress NAT Ingress port ACL Ingress VACL...
  • Page 60 Table 20: Updated TCAM Region Configuration After Reducing the IPv4 RACL (Ingress) Region Name Size Width Total Size IPv4 RACL 1536 1536 Layer 3 QoS (IPv6) Layer 3 QoS (IPv4) CoPP System Redirect SPAN Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 61: Enabling Vlan Qos (Ipv4)

    Also specify the reduced TCAM size for the region. Repeat this step for as many regions as necessary to free up sufficient Note resources to carve the new VLAN QoS (IPv4) TCAM region. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 62: Enabling Fex Qos (Ipv4)

    To enable FEX QoS (IPv4), you must decrease the TCAM size of another region and then increase the TCAM size to enable the new FEX QoS (IPv4) region. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 63: Enabling Egress Qos (Ipv4)

    • Violated and non-violated statistics are supported for policing action when a double-wide TCAM is configured. • Violated statistics are not supported for policing action only when the single-wide TCAM (e-qos-lite) is configured. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 64: Using Templates To Configure Tcam Region Sizes

    Using Templates to Configure TCAM Region Sizes Beginning with Cisco NX-OS Release 7.0(3)I3(1), you can use create and apply custom templates to configure TCAM region sizes. Once you apply a TCAM template, the hardware access-list tcam region command will not work. You Note must uncommit the template in order to use the command.
  • Page 65 Exits the TCAM template configuration mode. exit Example: switch(config-tcam-temp)# exit switch(config#) Step 5 [no] hardware profile tcam resource Applies the custom template to all line cards and fabric modules. service-template template-name Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 66: Verifying Qos Tcam Carving

    9500 Series, 3164Q, and 31128PQ devices. • nfe2—The default TCAM template for NFE2-enabled Cisco Nexus 9500, 3232C, and 3264Q devices. • l2-l3—The default TCAM template for Layer 2-to-Layer 3 configurations on Cisco Nexus 9200 Series switches. • l3—The default TCAM template for Layer 3 configurations on Cisco Nexus 9200 Series switches.
  • Page 67 If TCAM for a particular feature is not configured and you try to apply a feature that requires TCAM carving, the following message appears: ERROR: Module x returned status: TCAM region is not configured. Please configure TCAM region and retry the command. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 68 Configuring QoS TCAM Carving Verifying QoS TCAM Carving Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 69: Configuring Classification

    Differentiated Services Code Point (DSCP) DSCP value within the DiffServ field of the IP header. IP, IPv6, or MAC ACL name. Packet length Size range of Layer 3 packet lengths. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 70: Licensing Requirements For Classification

    • You are logged on to the device. Guidelines and Limitations Classification has the following configuration guidelines and limitations: • show commands with the internal keyword are not supported. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 71: Configuring Traffic Classes

    If both are present, the device acts on the port policy and ignores the VLAN policy. • When a Cisco Nexus Fabric Extender (FEX) is connected and in use, data traffic should not be marked with a CoS value of 7. CoS 7 is reserved for control traffic transiting the Fabric Extender.

  • Page 72: Configuring Dscp Classification

    List of DSCP Values af11 AF11 dscp (001010)—decimal value 10 af12 AF12 dscp (001100)—decimal value 12 af13 AF13 dscp (001110)—decimal value 14 af21 AF21 dscp (010010)—decimal value 18 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 73 EF dscp (101110)—decimal value 46 SUMMARY STEPS 1. configure terminal 2. class-map [type qos] [match-any | match-all] class-name 3. match [not] dscp dscp-values 4. exit 5. copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 74: 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 precedence values are listed in the following: Table 25: Precedence Values Value List of Precedence Values IP precedence value critical Critical precedence (5) Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 75 Values are shown in the following table. Use the not keyword to match on values that do not match the Example: specified range. switch(config-cmap-qos)# match precedence 1-2, 5-7 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 76: Configuring Protocol Classification

    1. configure terminal 2. class-map [type qos] [match-any | match-all] class-name 3. match [not] protocol {arp | bridging | cdp | dhcp | isis} 4. exit 5. copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 77: Configuring Layer 3 Packet Length 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 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 78: Configuring Cos Classification

    IEEE 802.1p to support QoS traffic classes. CoS is encoded in the high order 3 bits of the VLAN ID Tag field and is referred to as user_priority. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 79 (Optional) Saves the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config This example shows how to display the CoS class-map configuration: switch# show class-map class_cos Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 80: Configuring Cos Classification For Fex

    Exits global class-map queuing mode and enters global configuration exit mode. Example: switch(config-cmap-qos)# exit switch(config)# Step 5 copy running-config startup-config (Optional) Saves the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 81: Configuring Ip Rtp Classification

    Creates or accesses the class map named class-name and then class-name enters class-map mode. The class-map name can contain alphabetic, hyphen, or underscore characters, and can be up to 40 characters. Example: switch(config)# class-map class_rtp Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 82: Verifying The Classification Configuration

    Configuration Examples for Classification The following example shows how to configure classification for two classes of traffic: class-map class_dscp match dscp af21, af32 exit class-map class_cos match cos 4, 5-6 exit Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 83: Configuring Marking

    IP precedence uses only the lower three bits Note of the type of service (ToS) field. The device overwrites the first three bits of the ToS field to 0. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 84: Trust Boundaries

    When you enable Protocol Independent Multicast (PIM) in sparse mode on the switch virtual interface (SVI) for the VLAN in which traffic is received, PIM creates an S,G entry for any multicast traffic. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 85: Class Of Behavior

    Copied from 3 MSB of ToS Bridged multicast with no Layer 3 state for group Unchanged Licensing Requirements for Marking The following table shows the licensing requirements for this feature: Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 86: Prerequisites For Marking

    ◦ The FEX QoS policy supports only the set qos-group command. Other marking commands are not supported. set qos-group 0 is reserved for class default. It cannot be configured in user defined Note classes. ◦ Match on QoS-group is supported. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 87: Configuring Marking

    • Span traffic automatically gets classified into qos-group 9 and is scheduled at absolute low priority. • Egress QoS policies are not supported on Cisco Nexus 9200 Series switches (For 7.0(3)I3(1)). • QOS marking policies can be enabled on subinterfaces Configuring Marking You can combine one or more of the marking features in a policy map to control the setting of QoS values.
  • Page 88 For more information about DSCP, see RFC 2475. SUMMARY STEPS 1. configure terminal 2. policy-map [type qos] [match-first] policy-map-name 3. class [type qos] {class-name | class-default} [insert-before before-class-name] 4. set dscp dscp-value Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 89: Configuring Ip Precedence Marking

    The device rewrites the last 3 bits of the ToS field to 0 for packets that match this class. Note Table 31: Precedence Values Value List of Precedence Values IP precedence value critical Critical precedence (5) Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 90 The class is added to the end of the policy map unless insert-before is used to specify the class to insert before. Example: switch(config-pmap-qos)# class class1 switch(config-pmap-c-qos)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 91: Configuring Cos Marking

    Use the class-default keyword to select all traffic Example: that is not currently matched by classes in the policy map. switch(config-pmap-qos)# class class1 switch(config-pmap-c-qos)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 92: Configuring Cos Marking For Fex

    Use the class-default keyword to select all traffic that is Example: not currently matched by classes in the policy map. switch(config-pmap-qos)# class class1 switch(config-pmap-c-qos)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 93: Configuring Dscp Port Marking

    DSCP value is preserved. • You can attach only one policy type qos map to each interface in each direction. Note • The DSCP value is trust on the Layer 3 port of a Cisco NX-OS device. SUMMARY STEPS 1. configure terminal 2.
  • Page 94 Creates a reference to class-name and enters policy-map class [insert-before before-class-name] configuration mode. The class is added to the end of the policy map unless insert-before is used to specify the class to insert Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 95: Verifying The Marking Configuration

    Command Purpose show policy-map Displays all policy maps. Configuration Examples for Marking The following example shows how to configure marking: configure terminal policy-map type qos untrust_dcsp class class-default Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 96 Configuring Marking Configuration Examples for Marking set precedence 3 set qos-qroup 3 set dscp 0 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 97: Configuring Policing

    For more information about policers, see RFC 2697 and RFC 2698. Licensing Requirements for Policing The following table shows the licensing requirements for this feature: Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 98: Prerequisites For Policing

    • Does not support egress QoS policies on ALE uplink ports on top-of-rack (TOR) platforms. • When using egress QoS, Cisco recommends using the appropriate match criteria to match data traffic. (Avoid match criteria such as permit ip any any.) •...

  • Page 99: Configuring Policing

    1 to 80000000000; the range of policing values is from 8000 bps to 480 Gbps. The range of percentage values is from 1 to 100 percent. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 100 Table 34: Policer Actions for Exceed or Violate Action Description Drops the packet. This action is available only when drop the packet exceeds or violates the parameters. set-cos-transmit Sets CoS and transmits the packet. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 101 The data rates used in the police command are described in the following Data Rates for the police Command table. Table 36: Data Rates for the police Command Rate Description Bits per second (default) kbps 1,000 bits per seconds Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 102 [conform {transmit | set-prec-transmit | set-dscp-transmit | set-cos-transmit | set-qos-transmit} [exceed {drop} [violate {drop}]]} 5. exit 6. exit 7. show policy-map [type qos] [policy-map-name | qos-dynamic] 8. copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 103 Step 7 show policy-map [type qos] [policy-map-name | (Optional) Displays information about all configured policy maps qos-dynamic] or a selected policy map of type qos. Example: switch(config)# show policy-map Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 104: Configuring Ingress And Egress Policing

    [[be | peak-burst] peak-burst-rate [link-speed]] [conform conform-action [exceed [violate drop set dscp dscp table pir-markdown-map]]} 5. exit 6. exit 7. show policy-map [type qos] [policy-map-name] 8. copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 105 Example: switch(config)# show policy-map Step 8 (Optional) Saves the running configuration to the startup copy running-config startup-config configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 106: Verifying The Policing Configuration

    The following example shows how to configure policing for a 1-rate, 2-color policer with DSCP markdown: configure terminal policy-map policy2 class one_rate_2_color_policer_with_dscp_markdown police cir 256000 conform transmit violate drop Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 107: Configuring Queuing And Scheduling

    Traffic scheduling is the methodical output of packets at a desired frequency to accomplish a consistent flow of traffic. You can apply traffic scheduling to different traffic classes to weight the traffic by priority. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 108: Modifying Class Maps

    Note Enabling WRED and ECN on a class on a network-qos policy implies that WRED and ECN is enabled for all ports in the system. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 109: Approximate Fair Drop

    (Default age-period is 50 µsec. Default bandwidth-threshold is 500 bytes. Example: switch (config)# hardware qos etrap age-period 50 usec switch (config)# hardware qos etrap bandwidth-threshold 500 bytes switch (config)# hardware qos etrap byte-count 1048555 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 110 AFD and WRED cannot be applied at the same time. Only one can be used in a system. Note Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 111: Traffic Shaping

    Prerequisites for Queuing and Scheduling Queuing and scheduling have the following prerequisites: • You must be familiar with using modular QoS CLI. • You are logged on to the device. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 112: Guidelines And Limitations

    • Traffic shaping might increase the latency of packets due to queuing because it falls back to store-and-forward mode when packets are queued. • Traffic shaping is not supported on the Cisco Nexus 9300 ALE 40G ports. For more information on ALE 40G uplink ports, see the Limitations for ALE 40G Uplink Ports on the Cisco Nexus 9000 Series Switches.
  • Page 113 • The FEX QoS system level queuing policy does not support multiple priority levels. • Assigning a high alpha value on a Cisco Nexus 9200 Series switch uses more than the expected 50% of the available buffer space. Assigning a lower alpha value (7 or less) assures the usage of the expected 50% of the available buffer space.

  • Page 114: Configuring Queuing And Scheduling

    • Ingress queuing is not supported on devices with 100G ports. • The ingress queuing policy is supported only at the system level (and not at the interface level) for Cisco Nexus 9508 switches with the X9732C-EX line card and Cisco Nexus 93108TC-EX and 93180YC-EX switches.

  • Page 115: Configuring Type Queuing Policies

    If there are strict-priority queues, however, the strict-priority queues receive their share of the bandwidth first. The remaining bandwidth is shared in a weighted manner among the class Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 116: Configuring Congestion Avoidance

    (Optional) Specifies either the static or dynamic shared limit available to the queue dynamic threshold] for Cisco Nexus 9000 Series switches. The static queue limit defines the fixed size to which the queue can grow. The dynamic queue limit allows the queue's threshold size to be decided depending on the number of free cells available, in terms of the alpha value.
  • Page 117 Network Forwarding Leaf Spine Engine (LSE) enabled switches Engine (NFE) enabled alpha switches Definition Max % per Definition Max % per ASIC value queue queue 1/128 ~0.8% ~11% Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 118 It is not supported for the port level. Step 5 hardware qos q-noise percent value Tunes the random noise parameter. The default value is 20 percent. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 119: Configuring Wred On Egress Queues

    {packets | bytes | kbytes | mbytes} drop-probability value weight value] [threshold {burst-optimized | mesh-optimized}] [ecn|non-ecn] 5. (Optional) Repeat Steps 3 and 4 to configure WRED for other queuing classes. 6. (Optional) congestion-control random-detect forward-nonecn Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 120 Cisco Nexus 9508 switches with the X9732C-EX line card. Beginning with Cisco NX-OS Release 7.0(3)I4(5), this feature is supported on Cisco Nexus 9508 switches with the Cisco N9K-X9636PQ line cards and Cisco Nexus 3164Q switches. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 121: Configuring Afd On Egress Queues

    SUMMARY STEPS 1. configure terminal 2. policy-map type queuing afd_8q-out 3. class type queuing c-out-8q-q3 4. afd queue-desired <number> [bytes | kbytes | mbytes] [ecn] Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 122: Configuring Congestion Management

    • Taildrop thresholds based on the queue size and the queue limit usage. For more information, see the section. Configuring Tail Drop on Egress Queues, on page 102 • WRED for preferential packet drops. For more information, see the Configuring WRED on Egress Queues section. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 123: Configuring Bandwidth And Bandwidth Remaining

    Policy-map names can contain alphabetic, hyphen, or underscore characters, are case sensitive, and can be up to 40 Example: characters. switch(config)# policy-map type queuing shape_queues switch(config-pmap-que)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 124 Example: switch(config-pmap-c-que)# show policy-map type queuing shape_queues Step 8 copy running-config startup-config (Optional) Saves the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 125: Configuring Bandwidth And Bandwidth Remaining For Fex

    Policy-map names can contain alphabetic, hyphen, or underscore characters, are case sensitive, and can be up to 40 Example: characters. switch(config)# policy-map type queuing shape_queues switch(config-pmap-que)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 126 Example: switch(config-pmap-c-que)# show policy-map type queuing shape_queues Step 8 copy running-config startup-config (Optional) Saves the running configuration to the startup configuration. Example: switch(config)# copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 127: Configuring Priority

    7. (Optional) Repeat Steps 5 to 6 to assign the remaining bandwidth for the other nonpriority queues. 8. exit 9. show policy-map [type queuing [policy-map-name | default-out-policy]] 10. copy running-config startup-config Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 128 (Optional) Repeat Steps 5 to 6 to assign the remaining bandwidth for the other nonpriority queues. Step 8 exit Exits policy-map queue mode and enters global configuration mode. Example: switch(config-cmap-que)# exit switch(config)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 129: Configuring Priority For Fex

    SPQs, you have to configure the priority on QoS group 3 and on QoS group 2. Before You Begin Before configuring the FEX, enable feature-set fex. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 130 Choose a nonpriority queue where you want to configure the switch(config-pmap-c-que)# remaining bandwidth. By default, the system evenly distributes the remaining bandwidth among the nonpriority queues. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 131: Configuring Traffic Shaping

    You can configure traffic shaping on an egress queue to impose a minimum and maximum rate on it. Configuring traffic shaping for a queue is independent of priority or bandwidth in the same policy map. Note Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 132 Assigns a minimum and maximum bit rate on an output queue. value {bps | gbps | kbps | mbps | pps} The default bit rate is in bits per second (bps). Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 133: Applying A Queuing Policy On A System

    Step 1 configure terminal Enters global configuration mode. Example: switch# configure terminal switch(config)# Step 2 Enters system qos mode. system qos Example: switch (config)# system qos switch (config-sys-qos)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 134: Verifying The Queuing And Scheduling Configuration

    [all|default|none] • all Current behavior where all reservations are enabled ON). • default Enables reservations only for qos-group-0. • none Disables reservations for all qos-groups. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 135: Monitoring The Qos Packet Buffer

    Monitoring the QoS Packet Buffer The Cisco Nexus 9000 Series device has a 12-MB buffer memory that divides into a dedicated per port and dynamic shared memory. Each front-panel port has four unicast queues and four multicast queues in egress.

  • Page 136: Configuration Examples For Queuing And Scheduling

    The following example shows how to configure traffic shaping using 1000 packets per second (pps):: configure terminal class-map type queuing match-any c-out-q1 match qos-group 1 class-map type queuing match-any c-out-q2 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 137 100 pps max 500 pps class type queuing c-out-q2 shape min 200 pps max 1000 pps show policy-map type queuing pqu Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 138 Configuring Queuing and Scheduling Example: Configuring Traffic Shaping Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 139: Configuring Network Qos

    PFC per port. For more information about PFC, see the Configuring Priority Flow Control section. Licensing Requirements for Network QoS The following table shows the licensing requirements for this feature: Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 140: Prerequisites For Network Qos

    Default number of packets is120. Note • Maximum number of packets: ◦Application Spine Engine (ASE2) enabled switches — 256 ◦Leaf Spine Engine (LSE) enabled switches — 1024 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 141: Configuring Network Qos Policies

    • User-defined policy—You can create a network QoS policy that conforms to one of the system-defined policies. Copying a Predefined Network QoS Policy SUMMARY STEPS 1. qos copy policy-map type network-qos default-nq-policy {prefix prefix | suffix suffix} 2. show policy-map type network-qos my_nq Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 142: Configuring A User-Defined Network Qos Policy

    Configures the class map of the type network-qos and enters class-map mode. Class network-qos names are listed in previous System-Defined Type network-qos Class Maps table. Example: switch(config)# class-map type network-qos match-any c-nq2 switch(config-cmap-nqos)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 143: Applying A Network Qos Policy On A System

    You apply a network QoS policy globally on a system. Applying a network QoS policy also automatically applies the corresponding queuing policies. SUMMARY STEPS 1. configure terminal 2. system qos 3. service-policy type network-qos {policy-map-name | default-nq-policy} Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 144: Verifying The Network Qos

    Displays the type network-qos class maps. show class-map type network-qos show policy-map type network-qos Displays the type network-qos policy maps. show policy-map system type network-qos Displays the active type network-qos class maps. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 145: C H A P T E

    • Link-level flow control (LLFC) is supported on Cisco Nexus 9500 Series switches with Network Forwarding Engine (NFE) (and Cisco Nexus 3164Q switch with NFE). • Link-level flow control (LLFC) is supported on Cisco Nexus 9200 Series switches (7.0(3)I3(1) and later releases.

  • Page 146: Information About Link Level Flow Control

    MMU of the system may not get the expected treatment. • Beginning with NX-OS 7.0(3)I1(2), link level flow control and PFC are supported on Cisco Nexus 9300 Series switches and line cards that contain the ALE (Application Leaf Engine).

  • Page 147: Mismatched Link Level Flow Control Configurations

    2. interface ethernet 1/1 3. flowcontrol receive on 4. exit DETAILED STEPS Command or Action Purpose Step 1 configure terminal Enters global configuration mode. Example: Device# configure terminal Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 148: Configuring Link Level Flow Control Transmit

    QoS group. Instead, you should apply an interface QoS policy to the interfaces that having flow-control send-on enabled. SUMMARY STEPS 1. configure terminal 2. interface ethernet 1/1 3. flowcontrol send on 4. exit Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 149: Configuration Examples For Link Level Flow Control

    Device(config-cmap-nq)# match qos-group 1 Device(config-cmap-nq)# policy-map type network-qos my_network_policy Device(config-pmap-nq)# class type network-qos class1 Device(config-pmap-nq-c)# pause pfc-cos 2 Device(config-pmap-nq-c)# system qos Device(config-sys-qos)# service-policy type network-qos my_network_policy Device# show running ipqos Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 150: Example: Configuring Link Level Flow Control Receive And Send

    (Refer to the Configuring a No-Drop Policy example for information about configuring the no-drop class.) Device# configure terminal Device(config)# interface ethernet 1/1 Device(config-if)# flowcontrol send on Device(config-if)# exit Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 151: Configuring Priority Flow Control

    512 bits at the speed of the port. The range is from 0 to 65535. A pause frame with a pause quanta of 0 indicates a resume frame to restart the paused traffic. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 152: Licensing Requirements For Priority Flow Control

    This pause frame is a one-hop frame that is not forwarded when received by the peer. When the congestion is mitigated, PFC can request the peer to restart transmitting frames. RDMA over Converged Ethernet (RoCE) v1 and v2 protocols are supported on Cisco Nexus 9000 Series Note switches.
  • Page 153 • When a no-drop class is classified based on 802.1p CoS x and assigned a internal priority value (qos-group) of y, Cisco recommends that you use the internal priority value x to classify traffic on 802.1p CoS only, and not on any other field. The packet priority assigned is x if the classification is not based on CoS, which results in packets of internal priority x and y to map to the same priority x.
  • Page 154 • PFC is not supported for the N9K-X9408PC-CFP2 line card on Cisco Nexus 9500 Series switches. • Beginning with NX-OS 7.0(3)I1(2), link level flow control and PFC are supported on Cisco Nexus 9300 Series switches and line cards that contain the ALE (Application Leaf Engine).

  • Page 155: Default Settings For Priority Flow Control

    PFC without having to disable PFC on each interface. It is supported beginning with Cisco NX-OS Release 7.0(3)I4(2) and only for Cisco Nexus 9200 Series switches, Cisco Nexus 93108TC-EX and 93180YC-EX switches, and Cisco Nexus 9508 switches with the X9732C-EX line card.

  • Page 156: Enabling Priority Flow Control On A Traffic Class

    (Optional) Displays the status of PFC on all interfaces. Example: switch# show interface priority-flow-control Enabling Priority Flow Control on a Traffic Class You can enable PFC on a particular traffic class. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 157 You can configure a CoS value in the range of 0 to 7. Example: switch(config-cmap-qos)# match cos 2 Step 4 exit Exits class-map mode and enters global configuration mode. Example: switch(config-cmap-qos)# exit switch(config)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 158 Policy-map names can contain alphabetic, hyphen, or underscore characters, are case sensitive, and Example: can be up to 40 characters. switch(config)# policy-map type network-qos p1 switch(config-pmap-nqos)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 159 20480 bytes • The pause threshold value must be greater than the resume threshold value. Otherwise, the following message appears: ERROR: pause-threshold can't be less then resume-threshold Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 160: Configuring A Priority Flow Control Watchdog Interval

    When the time period is exceeded, all outgoing packets are dropped on interfaces that match the PFC queue that is not being drained. This feature is supported beginning with Cisco NX-OS Release 7.0(3)I4(2) and only for Cisco Nexus 9200 Series switches, Cisco Nexus 93108TC-EX and 93180YC-EX switches, and Cisco Nexus 9508 switches with the X9732C-EX line cards.
  • Page 161 Configuring Priority Flow Control Configuring Pause Buffer Thresholds and Queue Limit Using Ingress Queuing Policy About queue limits for 100G enabled devices (such as the Cisco Nexus 9300 Series switch with the Note N9K-M4PC-CFP2 GEM): • The maximum dynamic queue-limit alpha value supported by the device might be greater that 8.

  • Page 162: Verifying The Priority Flow Control Configuration

    3 switch(config-cmap-nqos)# exit switch(config)# policy-map type network-qos p1 switch(config-pmap-nqos)# class type network-qos c-nq1 switch(config-pmap-nqos-c)# pause buffer-size 20000 pause-threshold 100 resume-threshold 1000 pfc-cos 3 switch(config-pmap-nqos-c)# exit switch(config-pmap-nqos)# exit Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 163 Configuring Priority Flow Control Configuration Examples for Priority Flow Control switch(config)# system qos switch(config-sys-qos)# service-policy type network-qos p1 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 164 Configuring Priority Flow Control Configuration Examples for Priority Flow Control Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 165: C H A P T E

    NX-OS image and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 166: Prerequisites For Monitoring Qos Statistics

    Tx Pkts | 235775| Tx Byts | 22634400| Dropped Pkts | Dropped Byts | Q Depth Byts | +-------------------------------------------------------------------+ QOS GROUP 1 +-------------------------------------------------------------------+ Unicast | OOBFC Unicast Multicast Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 167 TxPPP: 0, RxPPP: ---------------------------------------------------------------------------- COS QOS Group TxPause TxCount RxPause RxCount Inactive Inactive Inactive Inactive Inactive Inactive Inactive Inactive Inactive Inactive Inactive Inactive Inactive Inactive Inactive Inactive ---------------------------------------------------------------------------- Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 168: Enabling Statistics

    • Disable QoS statistics: switch(config)# no qos statistics Step 3 show policy-map interface (Optional) Displays the statistics status and the configured policy maps on all interfaces. Example: switch(config)# show policy-map interface Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 169: Monitoring The Statistics

    You can clear QoS statistics for all interfaces or a selected interface, data direction, or QoS type. SUMMARY STEPS 1. clear qos statistics [interface [input | output] [type {qos | queuing}]] Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 170: Configuration Examples For Monitoring Qos Statistics

    Tx Pkts | Dropped Pkts | +-------------------------------------------------------------------+ QOS GROUP 2 +-------------------------------------------------------------------+ Tx Pkts | Dropped Pkts | +-------------------------------------------------------------------+ QOS GROUP 3 +-------------------------------------------------------------------+ Tx Pkts | Dropped Pkts | Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 171 Configuration Examples For Monitoring QoS Statistics +-------------------------------------------------------------------+ CONTROL QOS GROUP 4 +-------------------------------------------------------------------+ Tx Pkts | Dropped Pkts | +-------------------------------------------------------------------+ SPAN QOS GROUP 5 +-------------------------------------------------------------------+ Tx Pkts | Dropped Pkts | 948| +-------------------------------------------------------------------+ Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 172 Monitoring QoS Statistics Configuration Examples For Monitoring QoS Statistics Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 173: C H A P T E

    (NFE2). The minimum micro-burst that can be detected is 0.64 microseconds for 1 - 3 queues. On these switches, micro-burst monitoring is supported on unicast egress queues. It is not supported on multicast, CPU, or span queues. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 174 N9K-C92160YC-X 0x16 or later N9K-C92304QC 0x10 or later N9K-C9272Q 0x15 or later N9K-C9232C 0x6 or later N9K-C9236C 0x14 or later N9K-C93180YC-EX 0x8 or later N9K-C93108TC-EX 0x9 or later Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 175: Configuring Micro-Burst Detection

    Micro-Burst Monitoring Configuring Micro-Burst Detection For more information about EPLD programming to upgrade the FPGA, see the Cisco Nexus 9000 Series FPGA/EPLD Upgrade Release Notes. • The following are guidelines for micro-burst duration on TOR switches that contain a Network Forwarding...
  • Page 176 TOR switches with Range for rise-threshold Application Spine Engine bytes: 208 - 13319072. (ASE2, ASE3) or Leaf Range for fall-threshold Spine Engine (LSE) bytes: 208 - 13319072. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 177: Clearing Micro-Burst Detection

    Eth1/2 queue 7 Verifying Micro-Burst Detection The following displays micro-burst monitoring information: Command Purpose show queuing burst-detect Displays micro-burst counters information for all interfaces. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 178: Example Of Micro-Burst Detection Output

    Eth 1/2 • Example for a queue: show queuing burst-detect interface Eth 1/2 queue 7 Example of Micro-Burst Detection Output Example output of TOR switch. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 179: Fex Qos Configuration

    FEX QoS Configuration Information • Classification (system type qos policy) Type System Level Hardware Implementation Action Direction: IN Switch match ip access list dscp precedence protocol qos-group precedence dscp Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 180 • Input queuing System Level Hardware Implementation Action Direction: IN Switch Bandwidth Bandwidth Remaining Priority (only level 1) Interface Level Hardware Implementation Direction: IN Action Switch Bandwidth Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 181: Tcam Carving For Fex Qos

    As a best practice, you can use the hardware access-list tcam region fex-qos-lite 256 command when policers are not used. The fex-qos-lite region does not have conformed policer statistics support for IPv4. Note Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 182: Fex Qos Configuration Example

    1 switch(config-cmap-qos)# switch(config-cmap-qos)# class-map type qos match-all cos2 switch(config-cmap-qos)# match cos 2 switch(config-cmap-qos)# switch(config-cmap-qos)# class-map type qos match-all cos3 switch(config-cmap-qos)# match cos 3 switch(config-cmap-qos)# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 183 2 drop-type: drop cos: 0 1 2 3 4 5 6 xoff buffer-size ---------+---------+----------- 19200 24320 48640 Queueing: queue qos-group priority bandwidth mtu --------+------------+--------------+---------+---------+---- ctrl-hi 2400 ctrl-lo 2400 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 184 Last queueing config recvd from supId: 0 -----SUP 0 start ----- Queuing config per qos_group Interface queueing config valid: no Queueing per qos_group: 00006| |id|bw%|bw_unit|priority grp |00|100|0000000|00000000 grp |01|000|0000000|00000000 grp |02|000|0000000|00000000 grp |03|000|0000000|00000000 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 185 ----+---------+---------+----- Class CT-En MTU-Cells [Bytes] ------+----+------+----------------- [2400 ] [2400 ] 116 [9280 ] 116 [9280 ] 116 [9280 ] 116 [9280 ] 127 [10160] 127 [10160] FRH configuration: Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 186 ------+-----------------------+---------------------- Rx Discard (WR_DISC): Rx Multicast Discard (WR_DISC_MC): Rx Error (WR_RCV_ERR): OQ statistics: Packets flushed: Packets timed out: 0 Pause statistics: Rx PFC Xoff Tx PFC Xoff ------+-----------------------+---------------------- Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 187 Description: Classifier for Ingress queue 1 match qos-group 1 class-map type queuing match-any c-in-q-default Description: Classifier for Ingress default queue match qos-group 0 switch# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 188 0, ctrl_vntag 0 ctrl_vlan 0, vntag_etype 0 Untagged COS config valid: no Untagged COS dump: rx_cos_def[0]=0, tx_cos_def[0]=0 rx_cos_def[1]=3, tx_cos_def[1]=3 Last queueing config recvd from supId: 0 -----SUP 0 start ----- Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 189 ----- PFC 1 (enabled), net_port 0x0 END of PI SECTION NIF0/0/1 Default CoS: 0 Rx-Remap Tx-Remap Class ----+---------+---------+----- Class CT-En MTU-Cells [Bytes] ------+----+------+----------------- [2400 ] [2400 ] Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 190 PQ1 En: 0, PQ1 Class: 0 Class XoffToMap CrDec ------+----------+---+---+---+----+----+----+-----+---- SS statistics: Class Rx (WR_RCVD) Tx (RD_SENT) ------+-----------------------+---------------------- 68719476736 Rx Discard (WR_DISC): Rx Multicast Discard (WR_DISC_MC): Rx Error (WR_RCV_ERR): OQ statistics: Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 191 10 switch(config-pmap-c-que)# • Attach service policy to system target configuration: switch# conf t Enter configuration commands, one per line. End with CNTL/Z. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 192 ---------------+---------------+---------------+---------------+-------------- InActive Priority-flow-control enabled: no Flow-control status: rx 0x0, tx 0x0, rx_mask 0x0 qos-group rx pause tx pause masked rx pause Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 193 TX| 0x00|000000003|0000000 -----SUP 0 end ----- -----SUP 1 start ----- Queuing config per qos_group Interface queueing config valid: no Queueing per qos_group: 00006| |id|bw%|bw_unit|priority grp |00|100|0000000|00000000 grp |01|000|0000000|00000000 Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 194 Xoff Threshold: 0, Total Credits: 0 Pause configuration: PFC disabled Rx PFC CoS map: 0x00, Tx PFC CoS map: 0x00 Index CoS-to-Class Class-to-CoS------+-------------+------------ 0x00 0xff 0x00 0xff 0x00 0xff Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 195 Rx Xoff Status: 0x00 Tx Xoff Status: 0x00 RdPort Class Head Tail QCount RealQCountRx ---+-------+------+------+------+-------+------------ 3113 9348 11057 4864 5356 4257 12304 10048 11346 2368 14500 12314 9602 fex-101# Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 196: Verifying The Fex Qos Configuration

    [qos | queuing] Displays information about all configured policy maps of type qos or queuing on the system. show queuing interface ethernet Displays information about queuing on the ethernet interface. Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...

  • Page 197: Appendix B Additional References

    A P P E N D I X Additional References This appendix contains additional information related to implementing QoS on the Cisco NX-OS device. This appendix includes the following sections: • RFCs, page 183 RFCs RFCs Title RFC 2474 Differentiated Services Field...
  • Page 198 Additional References RFCs Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x...
  • Page 199 105, 106 hardware profile tcam resource service-template reload 51, 52 hardware profile tcam resource template show hardware access-list tcam template Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x IN-1...
  • Page 200 Index Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x IN-2...

Table of Contents