Table of Contents

New and Changed Information

Preface

Overview

Configuring QoS Classification

Configuring QoS Marking Policies

Configuring QoS Policing

Configuring QoS Statistics

Configuring QoS Weighted Fair Queuing

DSCP and Precedence Values

Configuration Limits

Title Page

New and Changed Information

This chapter describes new or was changed content in this document by software release number.

To find additional information, go to the following locations on Cisco.com:

- Configuration Guides

- Release Notes

Feature

Description

Changed in R

elease

Where Documented

Class Based Weighted Fair Queuing

Added configuration chapter for Class Based Weighted Fair Queuing

4.2(1)SV1(4)

Chapter 6, “Configuring Class Based Weighted Fair Queueing”

Configuration limits.

Added configuration limits for QoS policy-maps, QoS class-maps, and QoS interfaces.

4.0(4)SV1(2)

Preface

The Quality of Service (QoS) Configuration document describes the features that are used to prevent traffic congestion, and provides procedures to configure these features.

Audience

This guide is for network administrators with the following experience and knowledge:

- An understanding of virtualization

- Using VMware tools to configure a vswitch

Note Knowledge of VMware vNetwork Distributed Switch is not a prerequisite.

Organization

This publication is organized as follows:

Chapter

Description

Chapter 1, “Overview”

Provides an overview of QoS features and lists supported RFPs.

Chapter 2, “Configuring QoS Classification”

Describes how to classify network traffic.

Chapter 3, “Configuring QoS Marking Policies”

Describes how to mark network traffic.

Chapter 4, “Configuring QoS Policing”

Describes how to police network traffic.

Chapter 5, “Monitoring QoS Statistics”

Describes how to enable and view QoS statistics.

Chapter 6, “Configuring Class Based Weighted Fair Queueing”

Describes how to configure Class Based Weighted Fair Queuing.

Provides the DSCP and precedence values used in QoS class maps and policy maps.

Provides information about limitations in configuring QoS.

Document Conventions

This publication uses the following conventions:

Command descriptions use these conventions:

Commands and keywords are in boldface.

Arguments for which you supply values are in italics.

{ }

Elements in braces are required choices.

[ ]

Elements in square brackets are optional.

Alternative, mutually exclusive elements are separated by vertical bars.

Screen examples use these conventions:

screen font

Terminal sessions and information that the switch displays are in screen font.

boldface screen font

Information that you must enter is in boldface screen font.

Arguments for which you supply values are in italic screen font.

< >

Nonprinting characters, such as passwords, are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or number sign (#) at the beginning of a line of code indicates a comment line.

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Recommended Reading

Before configuring this feature in the Cisco Nexus 1000V, we recommend that you read and become familiar with the following documentation:

- Cisco Nexus 1000V Getting Started Guide, Release 4.2(1)SV1(5.1)

- Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(5.1)

- Cisco VN-Link: Virtualization-Aware Networking white paper

Overview

This chapter describes the quality of service (QoS) features that you can use on Cisco Nexus 1000V to prevent traffic congestion in your network.

Information About Quality of Service

You can use QoS to provide the most desirable flow of traffic through a network. QoS allows you to classify your network traffic, police and prioritize the traffic flow, and provide congestion avoidance. Traffic is processed based on how you classify it and the QoS policies that you put in place.

You can implement a QoS policy using the following steps:

command. For more information, see Chapter2, “Configuring QoS Classification”

command. A traffic policy defines how specific traffic is to be acted upon to improve the quality of service. For more information, see Chapter3, “Configuring QoS Marking Policies”

command. For more information, see the “Creating Ingress and Egress Policies” section.

4. Police the traffic. For more information, see Chapter4, “Configuring QoS Policing”

Traffic Classification and Marking

describes these processes.

Table 1-1 Traffic Classification and Traffic Marking

QoS Method

Description

Command

Mechanism

Traffic Classification

Groups network traffic based on defined criteria.

class maps

Traffic Marking

Modifies traffic attributes by class.

policy maps

Traffic Classification

Traffic classification allows you to organize traffic (packets) into traffic classes or categories on the basis of whether the traffic matches the criteria you specify. The values used to classify traffic are called match criteria. When you define a traffic class, you can specify multiple match criteria, you can choose to not match on a particular criterion, or you can determine the traffic class by matching any or all criteria. For more information, see Chapter2, “Configuring QoS Classification”

Traffic Marking

Marking is the process of assigning a priority and involves setting the fields, such as class of service or DSCP, in a packet. The traffic is then marked accordingly as it comes into the device on an ingress interface. The markings are used to treat the traffic as it leaves the device on the egress interface. For more information about configuring marking, see Chapter3, “Configuring QoS Marking Policies”

Policing

Policing is the monitoring of data rates for a particular class of traffic. The Cisco Nexus 1000V can also monitor associated burst sizes.

Three conditions, are determined by the policer depending on the data rate parameters supplied: conform, exceed, or violate. You can configure only one action for each condition. When the data rate exceeds the user-supplied values, packets are either marked down or dropped.

You can define single-rate or dual-rate policers. Single-rate policers monitor the specified committed information rate (CIR) of traffic. Dual-rate policers monitor both CIR and peak information rate (PIR) of traffic.

For more information about configuring policing, see Chapter4, “Configuring QoS Policing”

QoS Commands

.

Table 1-2 QoS Configuration Commands

Global Configuration Commands

Class Map QoS Configuration

Command

Policy Map QoS Configuration

Command

Interface or

Port Profile Configuration Command

Policy Map Class QoS Configuration Command

Description

—

—

—

—

that represents a class of traffic.

—

—

—

—

that represents a mapping from one set of field values to another set of field values. You can reference a table map from a policy map.

—

—

—

—

that represents a set of policies to be applied to a set of class maps. Policy maps can reference table maps.

—

—

—

—

Applies a specified policy map to input or output packets on interfaces configured as follows:

- inherited from a port-profile1

- port-channel

- Ethernet

- VEthernet

—

—

—

—

Defines the action to take regarding packet data rates.

—

—

—

—

Defines the criteria for a class map.

—

—

—

—

Defines the packet header values for a policy map.

1.For information about port profiles, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(5.1).

1.For information about port profiles, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(5.1).

QoS Statistics

Statistics are maintained for each policy, class action, and match criteria per interface. For information about monitoring QoS statistics, see Chapter5, “Monitoring QoS Statistics”

Default QoS Behavior

QoS has no default behavior. Policing and prioritization of traffic are only implemented when you apply a policy map to an interface. The only exception is that, by default, the CoS value for control and packet VLAN traffic is set to 6. This value can be overridden with an explicit QoS policy that is configured on the interface that carries the control and packet VLAN traffic.

However, when designing your QoS and ACL policies, note that access control lists (ACLs) that are referenced within a QoS policy are processed as follows as part of the QoS policy:

- QoS ingress processing follows ACL processing.

- QoS egress processing precedes ACL egress processing.

Supported RFCs

lists RFCs that are supported by QoS.

Table 1-3 Supported RFCs

Number

Title

Architecture for Differentiated Services

A Single Rate Three Color Marker

A Dual Rate Three Color Marker

Management Information Base for the Differentiated Services Architecture

RTP: A Transport Protocol for Real-Time Applications

High Availability Requirements for QoS Features

QoS recovers its previous state after a software restart, and it is able to switch over from the active supervisor to the standby supervisor without a loss of state.

Configuring QoS Classification

This chapter describes how to create and map classes of traffic for QoS on Cisco Nexus 1000V.

Information About Traffic Classes

Traffic classes are categories of traffic (packets) that are grouped on the basis of similarity. Such groups of traffic are called class maps. Classifying network traffic allows you to enable a quality of service (QoS) strategy in your network.

Figure 2-1 shows the criteria that you use to classify network traffic.

Figure 2-1 Criteria for Classifying Network Traffic

Identifying and categorizing network traffic into traffic classes (that is, classifying packets) enables you to handle different types of traffic by separating network traffic into different categories.

Classifying network traffic allows you to see the kinds of traffic you have and treat some types of traffic differently than others. Identifying and organizing network traffic allows you to allocate network resources to deliver the best performance for each type of traffic.

You can place network traffic with a specific IP precedence into one traffic class, while you place traffic with a specific differentiated services code point (DSCP) value into another traffic class. Each traffic class can be given a different QoS treatment, which you configure in a policy map later.

. You can match the criteria to your traffic as follows:

- Matching all

- Matching or not matching one

- Matching or not matching multiple

- Matching or not matching another class map

Some of the criteria used in traffic class maps relates only to one direction of traffic—either ingress or egress. For example, the internal label QoS group has no meaning on ingress traffic because it has not yet been assigned a value.

Traffic that fails to match any traffic class in a QoS policy map is assigned to a default class of traffic called class-default. The class-default can be referenced in a QoS policy map to select this unmatched traffic.

lists and describes the allowable criteria used for mapping traffic classes.

Table 2-1 Traffic Class Criteria

Class Criteria

Description

CoS

Class of service (CoS) field in the IEEE 802.1Q header.

IP precedence

Precedence value within the type of service (ToS) byte of the IP header.

The IP precedence values are shown in the “IP Precedence Values” section.

Differentiated Services Code Point (DSCP)

DSCP value within the DIffServ field of the IP header.

The standard DSCP values are listed in the “Commonly Used DSCP Values” section.

QoS group

Locally significant QoS values that can be manipulated and matched within the system. The range is from 0 to 126.

Discard class

Locally significant values that can be matched and manipulated within the system. The range is from 0 to 63.

ACL

IP access control list (ACL) or MAC ACL name.

If you configure the class to match-all and ACL used as match-criteria, then no other match criteria, except the packet length, can be specified.

If you configure the class to match-any and ACL used as match-criteria, then you can match ACLs and any other match criteria also.

Packet length

Size range of Layer 3 packet lengths.

IP RTP

Applications that are using the Real-time Transport Protocol (RTP) are identified by UDP port number range.

Class map

Criteria that are specified in a named class-map object.

Prerequisites for Classification

Classification has the following prerequisites:

- You are logged in to the CLI in EXEC mode.

Guidelines and Limitations

Classification has the following guidelines and limitations:

- You can specify a maximum of 32 match criteria in a class map.

- You can configure a maximum of 64 classes for use in a single policy map, if no policers are configured.

- When you match on an ACL, the only other match that you can specify is the Layer 3 packet length in a match-all class.

- You can classify traffic on Layer 2 ports based on the port policy of the incoming packet.

Classifying Traffic

This section describes how to classify traffic.

Classifying ACL Traffic

You can classify traffic by matching packets based on existing access control lists (ACLs).

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- QoS does not use the permit-deny functions of ACLs. The permit and deny ACL keywords are ignored when matching.

- QoS does not support the not form of this command.

- If you configure the class to match-all and ACL used as match-criteria, then no other match criteria, except the packet length, can be specified.

- If you configure the class to match-any and ACL used as match-criteria, then you can match ACLs and any other match criteria also.

- You are logged in to the CLI in EXEC mode.

- Tunneled IP packets are not matched unless the tunneling protocol is also IP, and then the match applies to the outer IP header and not the encapsulated IP header.

SUMMARY STEPS

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# class-map class_acl

n1000v(config-cmap_qos)#

Places you into class map QoS configuration mode for the specified class map and configures and saves the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

n1000v(config-cmap-qos)# match access-group name my_acl

Configures and saves the access group to match for this class in the running configuration.
keywords are ignored when matching the ACL. form of this command is not supported.

Step 4

n1000v(config-cmap-qos)# show class-map class_acl1

Displays the class map configuration.

Step 5

n1000v(config-cmap-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Classifying DSCP Traffic

You can classify traffic based on the DSCP value in the DiffServ field of the IP header. The standard DSCP values are found in the “DSCP and Precedence Values” section.

Note Tunneled IP packets are not matched unless the tunneling protocol is also IP, and then the match applies to the outer IP header and not the encapsulated IP header.

SUMMARY STEPS

`DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# class-map class_dscp

n1000v(config-cmap-qos)#

Places you into class map QoS configuration mode for the specified class map and configures and saves the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

n1000v(config-cmap-qos)# match dscp af21, af32

. The standard DSCP values are listed in the “DSCP and Precedence Values” section.

keyword to match on values that do not match the specified range.

Step 4

n1000v(config-cmap-qos)# show class-map class_dscp

Displays the class map configuration.

Step 5

n1000v(config-cmap-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

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. Precedence values can be found in the “DSCP and Precedence Values” section.

Note Tunneled IP packets are not matched unless the tunneling protocol is also IP, and then the match applies to the outer IP header and not the encapsulated IP header.

SUMMARY STEPS

`DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# class-map class_ip_precedence

n1000v(config-cmap-qos)#

Places you into class map QoS configuration mode for the specified class map and configures and saves the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

n1000v(config-cmap-qos)# match precedence 1-2, 5-7

keyword to match on values that do not match the specified range.

Step 4

Example:

n1000v(config-cmap-qos)# show class-map class_ip_precedence

Displays the class map configuration.

Step 5

n1000v(config-cmap-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Configuring QoS Group Classification

command as described in the “Creating a QoS Group Policy” section.

Note You match on the QoS group only in egress policies because its value is undefined until you set it in an ingress policy.

SUMMARY STEPS

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# class-map class_qos_group

n1000v(config-cmap-qos)#

Places you into class map QoS configuration mode for the specified class map and configures and saves the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

n1000v(config-cmap-qos)# match qos-group 4, 80-90

keyword to match on values that do not match the specified range.

Step 4

Example:

n1000v(config-cmap-qos)# show class-map class_qos_group

Displays the class map configuration for the specified traffic class name.

Step 5

n1000v(config-cmap-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Configuring Discard Class Classification

command as described in the “Creating a Discard Class Policy” section.

Note You match on the discard class only in egress policies because its value is undefined until you set it in an ingress policy.

SUMMARY STEPS

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

] class_map_name

n1000v(config)# class-map class_discard_class

n1000v(config-cmap-qos)#

Places you into class map QoS configuration mode for the specified class map and configures and saves the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

n1000v(config-cmap-qos)# match discard-class 4, 60-62

n1000v(config-cmap-qos)#

keyword to match on values that do not match the specified range.

Step 4

Example:

n1000v(config-cmap-qos)# show class-map class_discard_class

n1000v(config-cmap-qos)#

Displays the specified class map configuration.

Step 5

n1000v(config-cmap-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

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.

SUMMARY STEPS

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# class-map class_packet_length

Places you into class map QoS configuration mode for the specified class map and configures and saves the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

n1000v(config-cmap-qos)# match packet length 2000

keyword to match on values that do not match the specified range.

Step 4

Example:

n1000v(config-cmap-qos)# show class-map class_packet_length

n1000v(config-cmap-qos)#

Displays the specified class map configuration.

Step 5

n1000v(config-cmap-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Configuring CoS Classification

You can classify traffic based on the class of service (CoS) in the IEEE 802.1Q header. This 3-bit field is defined in 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.

SUMMARY STEPS

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# class-map class_cos

Places you into class map QoS configuration mode for the specified class map and configures and saves the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

n1000v(config-cmap-qos)# match cos 4, 5-6

keyword to match on values that do not match the specified range.

Step 4

Example:

n1000v(config-cmap-qos)# show class-map class_cos

n1000v(config-cmap-qos)#

Displays the specified class map configuration.

Step 5

n1000v(config-cmap-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Configuring IP RTP Classification

. Although RTP does not use a common TCP or UDP port, you typically configure RTP to use ports 16384 to 32767. UDP communications use an even port and the next higher odd port is used for RTP Control Protocol (RTCP) communications.

You can configure classification based on UDP port ranges, which are likely to target applications using RTP.

SUMMARY STEPS

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# class-map class_rtp

n1000v(config-cmap-qos)#

Places you into class map QoS configuration mode for the specified class map and configures and saves the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

n1000v(config-cmap-qos)# match ip rtp 2000-2100, 4000-4100

keyword to match on values that do not match the specified range.

Step 4

Example:

n1000v(config-cmap-qos)# show class-map class_rtp

Displays the specified class map configuration.

Step 5

n1000v(config-cmap-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Configuring Class Map Classification

You can classify traffic based on the match criteria in another class map.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- The referenced class map must be created prior to its reference.

- You can reference the same class map in multiple policies.

- You can configure only one level of nesting of class maps. You cannot reference a class map that references another class map.

- Before you delete a referenced class map, you should delete all references to that class map.

- To perform a logical OR with the class map that is specified in the match class-map command, use the match-any keyword. The match-any or match-all specification of the matched class map is ignored.

- To perform a logical AND with the class map that is specified in the match class-map command, use the match-all keyword. The match-any or match-all specification of the matched class map is ignored.

SUMMARY STEPS

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# class-map class_class_map

n1000v(config-cmap-qos)#

Places you into class map QoS configuration mode for the specified class map and configures and saves the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

n1000v(config-cmap-qos)# match class-map class_map3

keyword to match on values that do not match the specified range.

Step 4

n1000v(config-cmap-qos)# show class-map class_class_map

Displays the specified class map configuration.

Step 5

n1000v(config-cmap-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Verifying the Classification Configuration

To verify the classification configuration, use the commands in the following table:

Command

Description

Displays the class map configuration for all class maps or for a specified class map.

Displays all IPv4 access control lists (ACLs) or a specific IPv4 ACL.

Configuration Example for QoS Classification

This example shows how to configure classification for the class map named cmap1, which matches DSCP traffic AF21 and AF32:

n1000v(config)# class-map type qos match-all cmap1

n1000v(config-cmap-qos)# match dscp af21 af32

n1000v(config-cmap-qos)# exit

n1000v(config)#

Feature History for QoS Classification

This section provides the QoS Classification release history.

Feature Name

Releases

Feature Information

QoS Classification

4.0

This feature was introduced.

Configuring QoS Marking Policies

This chapter describes how to configure QoS marking policies on Cisco Nexus 1000V to prioritize network traffic.

Information About Policy Maps

Policy maps prioritize network traffic by class. You create policy maps to define how to treat each class of traffic so that it is prioritized for the best quality of service.

Marking is the process of marking packets, that is, changing one of the following in the packet for QoS purposes:

- Differentiated services code point (DSCP)

- Precedence

- CoS

You can map a traffic class to a DSCP, which is an indicator of the service level for a specified frame. The DSCP value ranges from 0 to 63, and the default is 0. A DSCP value of 46 is disallowed.

Service policies are specified using policy maps. Policy maps provide an ordered mapping of class maps to service levels. You can specify multiple class maps within a policy map, and map a class map to a high, medium, or low service level. The default priority is low. The policy map name is restricted to 63 alphanumeric characters.

The order of the class maps within a policy map is important to determine the order in which the frame is compared to class maps. The first matching class map has the corresponding priority marked in the frame.

Figure 3-1 Packet Fields Available for Marking

Marking is the setting of QoS information that is related to a packet. You can set the value of standard QoS fields IP precedence, DSCP and Class of Service (CoS), and internal labels that can be used in subsequent actions such as policing.

Once your traffic classes are defined, you can reference them in the policy map where you also define how they should be marked. We recommend that you keep the policy simple by using no more than four classes.

.

Table 3-1 Fields That Can be Marked

Field

Description

DSCP

Layer 3 differentiated services code point (DSCP).

Note If you mark DSCP, you cannot mark Discard Class.

IP precedence

Layer 3 IP precedence.

Note IP precedence uses only the lower 3 bits of the type of service (ToS) field. The device overwrites the first 3 bits of the ToS field to 0.

CoS

Layer 2 class of service (CoS).

QoS group

The range is from 0 to 126.

Discard class

The range is from 0 to 63.

Note If you mark Discard Class, you cannot mark DSCP.

Ingress and egress ports

The marking applies to incoming or outgoing packets.

For a single class, you can set operations on any two out of the following five fields: CoS, IP Precedence, DSCP, QoS Group, and Discard Class.

Unless noted as a restriction, you can mark both incoming and outgoing packets.

Prerequisites for QoS Marking Policies

Marking has the following prerequisites:

- You must have already classified your network traffic. For more information, see the “Configuring QoS Classification” section.

- You are already logged in to the CLI in EXEC mode.

Guidelines and Limitations

QoS policies have the following guidelines and limitations:

- The set cos command is applicable only to 802.1Q interfaces. So, although you can use the set cos command on an ingress interface, the setting is only applied if a packet eventually egresses an 802.1Q compliant interface.

- For a single class, you can set operations on any two out of the following five fields: CoS, IP Precedence, DSCP, QoS Group, and Discard Class.

- You can only use the set qos-group command in ingress policies.

- You can only use the set discard-class command in ingress policies.

- When designing your QoS and access control list (ACL) policies, note that ACLs referenced within a QoS policy are processed as follows as part of the QoS policy:

– QoS ingress processing follows ACL processing.

– QoS egress processing precedes ACL egress processing.

Creating QoS Marking Policies

This section describes how to create QoS policies for the Cisco Nexus 1000V:

- Creating a DSCP Policy

- Creating an IP Precedence Policy

- Creating a Class of Service Policy

- Creating a QoS Group Policy

- Creating a Discard Class Policy

- Creating Ingress and Egress Policies

- Marking the Port DSCP

Creating a DSCP Policy

You can create a policy that marks the DSCP value in the IP header packet to prioritize traffic in a particular class.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- DSCP is described in RFC 2475 .

- You are logged in to the CLI in EXEC mode.

- If you use DSCP marking, you cannot use Discard Class marking (see the “Creating a Discard Class Policy” section).

- You can mark the DSCP field as a numeric value between 0 and 63 or as one of the commonly used values listed in the “DSCP and Precedence Values” section.

SUMMARY STEPS

}

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)#

Places you into policy map QoS configuration mode for the specified policy map and configures the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

}

n1000v(config-pmap)# class class1

and enters policy-map class QoS configuration mode for the specified class map. By default, the class is added to the end of the policy map. Changes are saved in the running configuration.

keyword to select all traffic that is not currently matched by classes in the policy map.

Step 4

n1000v(config-pmap-c-qos)# set dscp af31

Defines the DSCP value that should be used in all IP headers for the specified class and saves it in the running configuration.

You can use a numeric value from 1 to 60 or one of the standard values from the “DSCP and Precedence Values” section.

In this example, the standard value of af31 is used.

Step 5

Example:

n1000v(config-pmap-c-qos)# show policy-map policy1

Displays the policy map configuration for the specified map name.

Step 6

n1000v(config-pmap-c-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Creating an IP Precedence Policy

You can mark IP Precedence to give priority to all packets in a particular traffic class.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- You are logged in to the CLI in EXEC mode.

- Table 3-2 lists the RFC 791 precedence values from least to most important.

Table 3-2 Precedence Values

Value

Description

000 (0)

Routine or Best Effort

001 (1)

Priority

010 (2)

Immediate

011 (3)

Flash (mainly used for voice signaling or for video)

100 (4)

Flash Override

101 (5)

Critical (mainly used for voice RTP)

110 (6)

Internet

111 (7)

Network

SUMMARY STEPS

}

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)#

Places you into policy map QoS configuration mode for the specified policy map and configures the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

}

n1000v(config-pmap-qos)# class class1

and enters policy-map class QoS configuration mode for the specified class map. By default, the class is added to the end of the policy map. Changes are saved in the running configuration.

keyword to select all traffic that is not currently matched by classes in the policy map.

Step 4

n1000v(config-pmap-c-qos)# set precedence 3

Adds the precedence value that should be used in all packets for the specified traffic class. The change is saved in the running configuration.

.

Step 5

Example:

n1000v(config-pmap-c-qos)# show policy-map policy1

Displays the policy map configuration for the specified map name.

Step 6

n1000v(config-pmap-c-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Creating a Class of Service Policy

You can mark the CoS field in the IEEE 802.1Q header for all traffic in a specific class. If you mark this field in an ingress or egress policy, it will only be set when a packet egresses an IEEE 802.1Q-capable interface.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- You are logged in to the CLI in EXEC mode.

- You can set CoS in ingress and egress policies.

SUMMARY STEPS

}

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)#

Places you into policy map QoS configuration mode for the specified policy map and configures the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

}

n1000v(config-pmap-qos)# class class1

and enters policy-map class QoS configuration mode for the specified class map. By default, the class is added to the end of the policy map. Changes are saved in the running configuration.

keyword to select all traffic that is not currently matched by classes in the policy map.

Step 4

n1000v(config-pmap-c-qos)# set cos 3

. The value can range from 0 to 7. You can use this command only in egress policies.

Step 5

Example:

n1000v(config-pmap-c-qos)# show policy-map policy1

Displays the policy map configuration for the specified map name.

Step 6

n1000v(config-pmap-c-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

EXAMPLES

This example shows how to create a class of service policy.

n1000v# config t

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)# class class1

n1000v(config-pmap-c-qos)# set cos 3

n1000v(config-pmap-c-qos)# show policy-map policy1

Type qos policy-maps

====================

policy-map type qos policy1

class class1

set dscp 26

set cos 3

class class2

set dscp 14

class class-default

set dscp 20

police cir 256000 bps bc 300 ms pir 256000 bps be 300 ms conform transmit exceed set dscp dscp table cir-mar

kdown-map violate drop

n1000v(config-pmap-c-qos)#

Creating a QoS Group Policy

You can mark the locally defined QoS group value.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- You can mark the QoS group value only in ingress policies.

- You are logged in to the CLI in EXEC mode.

SUMMARY STEPS

}

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)#

Places you into policy map QoS configuration mode for the specified policy map and configures the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

}

n1000v(config-pmap-qos)# class class1

n1000v(config-pmap-c-qos)#

and enters policy-map class QoS configuration mode for the specified class map. By default, the class is added to the end of the policy map. Changes are saved in the running configuration.

keyword to select all traffic that is not currently matched by classes in the policy map.

Step 4

n1000v(config-pmap-c-qos)# set qos-group 100

. The value can range from 0 to 126.

Step 5

Example:

n1000v(config-pmap-c-qos)# show policy-map policy1

Displays the policy map configuration for the specified map name.

Step 6

n1000v(config-pmap-c-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Creating a Discard Class Policy

You can set a local internal label discard class policy.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- If you configure a local internal label discard class policy, you cannot create a DSCP policy. For more information about DSCP policies, see the Creating a DSCP Policy.

- You can set a discard class only in ingress policies.

- To reference the local discard class in a policy or in traffic classification, use the match discard-class command.

For more information, see the Configuring Discard Class Classification.

SUMMARY STEPS

}

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)#

Places you into policy map QoS configuration mode for the specified policy map and configures the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

}

n1000v(config-pmap-qos)# class class1

and enters policy-map class QoS configuration mode for the specified class map. By default, the class is added to the end of the policy map. Changes are saved in the running configuration.

keyword to select all traffic that is not currently matched by classes in the policy map.

Step 4

n1000v(config-pmap-c-qos)# set discard-class 40

. The value can range from 0 to 63.

Step 5

Example:

n1000v(config-pmap-c-qos)# show policy-map policy1

Displays the policy map configuration for the specified map name.

Step 6

n1000v(config-pmap-c-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Creating Ingress and Egress Policies

You can attach a policy map to an interface or a port profile so that the marking instructions are applied to the ingress or egress packets.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- The interface or port profile have been created.

- The policy map that you want to use has been defined.

Note You can attach only one input policy and one output policy to an interface or port profile.

SUMMARY STEPS

2. Enter one of the following commands:

]

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

Enter one of the following commands:

- interface type number

- port-profile name

n1000v(config)# interface ethernet 1/1

n1000v(config-if)#

Places you into Configuration mode for the specified Ethernet or vEthernet interface or port profile.

Step 3

[no-stats]

n1000v(config-if)# service-policy input policy1

(Optional) Attaches a policy map name that will be added to the input or output packets of the interface or port profile.

Note You can attach only one input policy and one output policy to an interface or port profile.

Step 4

Example:

n1000v(config-if)# show policy-map policy1

Displays the policy map configuration for the specified map name.

Step 5

n1000v(config-if)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

EXAMPLES

This example shows how to configure an ingress policy on an Ethernet interface:

n1000v(config-if)# show policy-map policy1

Type qos policy-maps

====================

policy-map type qos policy1

n1000v(config-if)# copy running-config startup-config

This example shows how to configure an ingress policy on a port profile:

n1000v(config-port-prof)# show policy-map policy1

Type qos policy-maps

====================

policy-map type qos policy1

n1000v(config-port-prof)# copy running-config startup-config

Marking the Port DSCP

You can mark the DSCP port for each class of traffic that is defined in a specified ingress or egress policy map.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- The default behavior is to preserve the DSCP value, or to trust DSCP. To make the port untrusted, change the DSCP value.

- Unless you configure a QoS policy and attach that policy to specified interfaces, the DSCP value is preserved.

- The class map that you want to use has been defined. See Chapter2, “Configuring QoS Classification”

Note You can attach only one input policy and one output policy to an interface or port profile.

SUMMARY STEPS

}

for each class map that you want to create.

8. Enter one of the following commands:

]

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)#

Places you into policy map QoS configuration mode for the specified policy map and configures the map name in the running configuration.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3a

}

n1000v(config-pmap)# class class1

n1000v(config-pmap-c-qos)#

and enters policy-map class QoS configuration mode for the specified class map. By default, the class is added to the end of the policy map. Changes are saved in the running configuration.

keyword to select all traffic that is not currently matched by classes in the policy map.

Step 4b

n1000v(config-pmap-c-qos)# set dscp af31

Sets a DSCP value. Valid values are shown in the “DSCP and Precedence Values” section.

Step 5

for each class map that you want to create.

Step 6

n1000v(config-pmap-c-qos)# exit

n1000v(config-pmap-qos)#

Returns you to policy map configuration mode.

Step 7

n1000v(config-pmap-qos)# exit

n1000v(config)#

Returns you to global configuration mode.

Step 8

Enter one of the following commands:

- interface type number

- port-profile name

n1000v(config)# interface ethernet 1/1

n1000v(config-if)#

Places you into the configuration mode for the specified Ethernet or vEthernet interface or port profile.

Step 9

[no-stats]

n1000v(config-if)# service-policy input policy1

(Optional) Attaches a policy map name that will be added to the input or output packets of the interface or port profile.

Note You can attach only one input policy and one output policy to an interface or port profile.

Step 10

Example:

n1000v(config-if)# show policy-map policy1

Displays the policy map configuration for the specified map name.

Step 11

n1000v(config-if)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

EXAMPLES

This example shows how to mark the DSCP port for each class of traffic defined in an ingress policy map on an Ethernet interface.

n1000v# config t

n1000v(config)# policy-map policy1

n1000v(config-pmap)# class class1

n1000v(config-pmap-c-qos)# set dscp af31

n1000v(config-pmap-c-qos)# exit

n1000v(config-pmap-qos)# class class2

n1000v(config-pmap-c-qos)# set dscp af13

n1000v(config-pmap-c-qos)# exit

n1000v(config-pmap-qos)# class class-default

n1000v(config-pmap-c-qos)# set dscp af22

n1000v(config-pmap-c-qos)# exit

n1000v(config-pmap-qos)# exit

n1000v(config)# interface ethernet 1/1

n1000v(config-if)# service-policy input policy1

n1000v(config-if)# show policy-map policy1

Type qos policy-maps

====================

policy-map type qos policy1

class class1

set dscp af31

class class2

set dscp af13

class class-default

set dscp af22

n1000v(config-if)# copy running-config startup-config

This example shows how to mark the DSCP port for each class of traffic defined in an ingress policy map on a port profile.

n1000v# config t

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)# class class1

n1000v(config-pmap-c-qos)# set dscp af31

n1000v(config-pmap-c-qos)# exit

n1000v(config-pmap-qos)# class class2

n1000v(config-pmap-c-qos)# set dscp af13

n1000v(config-pmap-c-qos)# exit

n1000v(config-pmap-qos)# class class-default

n1000v(config-pmap-c-qos)# set dscp af22

n1000v(config-pmap-c-qos)# exit

n1000v(config-pmap-qos)# exit

n1000v(config)# port-profile accessprofile

n1000v(config-port-prof)# service-policy input policy1

n1000v(config-port-prof)# show policy-map policy1

Type qos policy-maps

====================

policy-map type qos policy1

class class1

set dscp af31

class class2

set dscp af13

class class-default

set dscp af22

n1000v(config-port-prof)# copy running-config startup-config

Verifying the QoS Policy Configuration

To verify the QoS policy configuration, perform one of the following tasks:

Command

Description

]

Displays the policy map configuration.

Displays the table map configuration.

Configuration Example for QoS Marking Policies

This example shows how to display a specific policy-map policy:

n1000v(config)# show policy-map policy-ipacl

Type qos policy-maps

====================

policy-map type qos policy-ipacl

class class-ipacl

set dscp 10

This example shows how to display policy maps for all interfaces:

n1000v# show policy-map interface brief

Interface/VLAN [Status]:INP QOS OUT QOS INP QUE OUT QUE

================================================================================

Vethernet1 [Active]: media

Vethernet10 [Active]: media

Vethernet13 [Active]:web_policer

Vethernet15 [Active]:iperf

Vethernet16 [Active]: iperf_policer

Vethernet17 [Active]:ixia_in ixia_out

Vethernet18 [Active]: media

Vethernet19 [Active]:iperf

Vethernet20 [Active]: iperf_policer

Vethernet21 [Active]:netperf_polic

================================================================================

Feature History for QoS Marking Policies

This section provides the QoS marking policies release history.

Feature Name

Releases

Feature Information

QoS Marking Policies

4.0

This feature was introduced.

QoS Marking Policies

4.0(4)SV1(2)

DSCP and Discard Class are no longer mutually exclusive. For a single class, you can set operations on any two out of the following five fields: CoS, IP Precedence, DSCP, QoS Group, and Discard Class.

Configuring QoS Policing

This chapter describes how to configure policing of traffic classes for Cisco Nexus 1000V.

Information About Policing

Policing is the monitoring of data rates for a particular class of traffic. The Cisco Nexus 1000V can also monitor associated burst sizes.

Three conditions, are determined by the policer depending on the data rate parameters supplied: conform (green), exceed (yellow), or violate (red). You can configure only one action for each condition. When the data rate exceeds the user-supplied values, packets are either marked down or dropped.

You can define single-rate or dual-rate policers. Single-rate policers monitor the specified committed information rate (CIR) of traffic. Dual-rate policers monitor both CIR and peak information rate (PIR) of traffic. Figure 4-1shows policing conditions and types.

.

Figure 4-1 Policing Conditions and Types

The following conditions trigger actions by the policer depending on the defined data rate:

Condition

Color

Description

Policer Action

(only one allowed per condition)

Conform

Green

The packet traffic data rate is within the defined boundaries.

The policer either transmits these packets as is, or changes the value in the header (DSCP, precedence, or CoS), and then transmits these packets.

Exceed

Yellow

The packet traffic data rate exceeds the defined boundary.

The policer can drop or mark down these packets.

Violate

Red

The packet traffic data rate violates the defined boundaries.

The policer can drop or mark down these packets.

Prerequisites for Policing

Policing has the following prerequisites:

- You must be familiar with RFC 2698 .

- You are logged on to the CLI in EXEC mode.

Guidelines and Limitations

Use the following guideline to configure policing:

- Each module polices independently, which might affect a policer that is applied to traffic distributed across more than one module, such as in the case of a port channel interface.

Configuring Policing

You can configure a single- or dual-rate policer in the Cisco Nexus 1000V.

Configuring 1-Rate and 2-Rate, 2-Color and 3-Color Policing

.

Note Specify the identical value for pir and cir to configure 1-rate 3-color policing.

Command

Argument

Description

is required, the argument itself is optional. The range of values is from 1 to 80000000000; the range of policing values that are mathematically significant is 8000 to 80 Gbps.

Specifies the rate as a percentage of the interface rate. The range of values is from 1 to 100%.

. The default is 200 milliseconds of traffic at the configured rate. The default data rate units are bytes, and the Gigabit per second (gbps) rate is not supported for this parameter.

Peak information rate, which is specified as a PIR bit rate or a percentage of the link rate. There is no default. The range of values is from 1 to 80000000000; the range of policing values that are mathematically significant is from 8000 to 80 Gbps. The range of percentage values is from 1 to 100%.

value is not specified, the default is 200 milliseconds of traffic at the configured rate. The default data rate units are bytes, and the Gigabit per second (gbps) rate is not supported for this parameter.
before the device displays this argument.

. The default is transmit.

Single action to take if the traffic data rate exceeds the specified boundaries. The basic actions are drop or markdown. The default is drop.

Single action to take if the traffic data rate violates the configured rate values. The basic actions are drop or markdown. The default is drop.

.

Table 4-2 Policer Types and Actions

Police Arguments Present

Policer Type

Policer Action

1-rate, 2-color

1-rate, 3-color

.

2-rate, 3-color

.

Table 4-3 Policer Actions for Exceed or Violate

Action

Description

Drops the packet. This action is available only when the packet exceeds or violates the parameters.

}

Sets the specified fields from a table map and transmits the packet. For more information on the system-defined, or default table maps, see Chapter3, “Configuring QoS Marking Policies” This is available only when the packet exceeds the parameters (use the cir-markdown-map) or violates the parameters (use the pir-markdown-map).

Table 4-4 Policer Actions for Conform

Action

Description

Transmits the packet. This action is available only when the packet conforms to the parameters.

Sets the IP precedence field to a specified value and transmits the packet. This action is available only when the packet conforms to the parameters.

Sets the DSCP field to a specified value and transmits the packet. This action is available only when the packet conforms to the parameters.

Sets the CoS field to a specified value and transmits the packet. This action is available only when the packet conforms to the parameters.

Sets the QoS group internal label to specified value and transmits the packet. This action can be used only in input policies and is available only when the packet conforms to the parameters.

Sets the discard-class internal label to a specified value and transmits the packet. This action can be used only in ingress policies and is available only when the packet conforms to the parameters.

Note The policer can only drop or mark down packets that exceed or violate the specified parameters. See Chapter 3, “Configuring QoS Marking Policies” for information on marking down packets.

.

Table 4-5 Data Rates for the police Command

Rate

Description

Bits per second (default)

1,000 bits per seconds

1,000,000 bits per second

1,000,000,000 bits per second

.

Table 4-6 Burst Sizes for the police Command

Speed

Description

bytes

1,000 bytes

1,000,000 bytes

milliseconds

microseconds

SUMMARY STEPS

Note You must specify the identical value for pir and cir to configure 1-rate, 3-color policing.

}

}}]}

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)#

Places you into policy map QoS configuration mode and creates or accesses the specified policy map.

argument is an alphabetic string that can be up to 40 case-insensitive characters long, including hyphen (-) and underscore (_) characters.

Step 3

}

n1000v(config-pmap-qos)# class class-default

n1000v(config-pmap-c-qos)#

and enters policy-map class QoS configuration mode for the specified class map. By default, the class is added to the end of the policy map. Changes are saved in the running configuration.

keyword to select all traffic that is not currently matched by classes in the policy map.

Step 4

}}]}

n1000v(config-pmap-c-qos)# police cir 256000 conform transmit violate set dscp dscp table pir-markdown-map

n1000v(config-pmap-c-qos)#

.

Step 5

]

n1000v(config-pmap-c-qos)# show policy-map

(Optional) Displays information about all configured policy maps or a selected policy map of type QoS.

Step 6

n1000v(config-pmap-c-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

EXAMPLES

This example shows how to configure a 1-rate, 2-color policer that transmits if the data rate is within 200 milliseconds of traffic at 256000 bps and marks IP precendence to 6 if the datarate is exceeded.

n1000v# config t

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)# class class-default

n1000v(config-pmap-c-qos)# police cir 256000 conform transmit violate set dscp dscp table pir-markdown-map

n1000v(config-pmap-c-qos)# show policy-map

Type qos policy-maps

====================

policy-map type qos policy1

class class1

set dscp af31

class class2

set dscp af13

class class-default

set dscp af22

police cir 256000 bps bc 200 ms conform transmit violate set dscp dscp tab

le pir-markdown-map

n1000v(config-pmap-c-qos)# copy running-config startup-config

This example shows how to configure a 1-rate, 3-color policer that transmits if the data rate is within 200 milliseconds of traffic at 256000 bps, and marks DSCP to 6 if the data rate is within 300 milliseconds of traffic at 256000 bps, and drops packets otherwise.

n1000v# config t

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)# class class-default

n1000v(config-pmap-c-qos)# police cir 256000 pir 256000 conform transmit exceed set dscp dscp table cir-markdown-map violate drop

n1000v(config-pmap-c-qos)# show policy-map

Type qos policy-maps

====================

policy-map type qos policy1

class class1

set dscp af31

class class2

set dscp af13

class class-default

set dscp af22

police cir 256000 bps bc 200 ms pir 256000 bps be 200 ms conform transmit

exceed set dscp dscp table cir-markdown-map violate drop

n1000v(config-pmap-c-qos)# copy running-config startup-config

Configuring Ingress and Egress Policing

command, see the Creating Ingress and Egress Policies.

Configuring Markdown Policing

.

SUMMARY STEPS

}

}]]}}

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# policy-map policy1

n1000v(config-pmap-qos)#

and then enters policy-map mode. The policy-map name can contain alphabetic, hyphen, or underscore characters, is case-insensitive, and can be up to 40 characters.

Step 3

}

n1000v(config-pmap-qos)# class class-default

n1000v(config-pmap-c-qos)#

and enters policy-map class QoS configuration mode for the specified class map. By default, the class is added to the end of the policy map. Changes are saved in the running configuration.

keyword to select all traffic that is not currently matched by classes in the policy map.

Step 4

}]]}}

n1000v(config-pmap-c-qos)# police cir 256000 be 300 ms conform transmit exceed set dscp dscp table cir-markdown-map violate drop

.

Step 5

]

n1000v(config-pmap-c-qos)# show policy-map

(Optional) Displays information about the policy map configuration.

Step 6

n1000v(config-pmap-c-qos)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

EXAMPLES

This example shows a 1-rate, 3-color policer that transmits if the data rate is within 300 milliseconds of traffic at 256000 bps; marks down DSCP using the system-defined table map if the data rate is within 300 milliseconds of traffic at 256000 bps; and drops packets otherwise:

Type qos policy-maps

====================

policy-map type qos policy1

class class-default

police cir 256000 bps bc 300 ms pir 256000 bps be 300 ms conform transmit

exceed set dscp dscp table cir-markdown-map violate drop

Verifying the Policing Configuration

To verify the policing configuration, perform the following task:

Command

Description

Displays information about policy maps and policing.

Configuration Example for QoS Policing

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

config t

policy-map policy1

class one_rate_2_color_policer

police cir 256000 conform transmit violate drop

The following example shows how to configure a 1-rate, 2-color policer with DSCP mark down:

config t

policy-map policy2

class one_rate_2_color_policer_with_dscp_markdown

police cir 256000 conform set-dscp-transmit af11 violate set dscp dscp table pir-markdown-map

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

config t

policy-map policy3

class one_rate_3_color_policer

police cir 256000 pir 256000 conform transmit exceed set dscp dscp table cir-markdown-map violate drop

Feature History for QoS Policing

This section provides the QoS policing release history.

Feature Name

Releases

Feature Information

QoS Policing

4.0

This feature was introduced.

Monitoring QoS Statistics

This chapter describes how to enable, display, and clear QoS statistics from the Cisco Nexus 1000V.

Information About QoS Statistics

command. Statistics are enabled by default and can be disabled globally.

Prerequisites for Monitoring QoS Statistics

Monitoring QoS statistics has the following prerequisites:

- You are logged in to the CLI in EXEC mode.

Enabling QoS Statistics

You can enable or disable QoS statistics for all interfaces on the device.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- By default, QoS statistics are enabled.

SUMMARY STEPS

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

n1000v(config)# qos statistics

Enables QoS statistics on all interfaces.

Step 3

n1000v(config)# show policy-map interface

(Optional) Displays the status of the global statistics and the configured policy maps on all interfaces.

Step 4

n1000v(config)# copy running-config startup-config

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Displaying QoS Statistics

You can display QoS statistics for an interface.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- You know the interface for which statistics are needed.

Note Statistics for individual interfaces are often the most useful.

SUMMARY STEPS

]

DETAILED STEPS

Command

Purpose

Step 1

]

n1000v# show policy-map interface ethernet 2/1

Displays the specified statistics.

To achieve the best result when your system has a large number of policies, use this command with specific arguments, such as specifying a particular interface or port channel.

- Use the interface keyword with the following keywords to display the service policy on an interface:

—displays a brief report of all policies attached to interfaces.

—displays statistics for an Ethernet interface.

—displays statistics for QoS input policies.

—displays statistics for QoS output policies.

—displays statistics for a port channel interface.

—displays the statistics for a vEthernet interface.

- Use the type qos keyword to display the type of policy map.

Clearing QoS Statistics

You can clear QoS statistics.

SUMMARY STEPS

}]

DETAILED STEPS

Command

Purpose

Step 1

}]

n1000v# clear qos statistics type qos

Clears the specified QoS statistics.

Configuration Example for QoS Statistics

This example shows how to display statistics for policy maps that are configured on interfaces:

n1000v(config)# show policy-map interface

Global statistics status : enabled

Vethernet3

Service-policy (qos) input: new-policy

policy statistics status: enabled

Class-map (qos): class-default (match-any)

59610700 packets

set prec 5

Vethernet5

Service-policy (qos) output: new-policer

policy statistics status: enabled

Class-map (qos): new-class (match-all)

344661013 packets

Match: precedence 5

police cir 900 mbps bc 200 ms

conformed 505953339796 bytes, 899924196 bps action: transmit

violated 12285218014 bytes, 22283000 bps action: drop

This example shows how to display statistics for a specific IPv4 access control list (ACL):

n1000v(config)# show ip access-lists protoacl

IP access list protoacl

statistics per-entry

10 permit icmp 7.120.1.10/32 7.120.1.20/32

20 permit tcp 7.120.1.10/32 7.120.1.20/32 dscp af11

30 permit udp 7.120.1.10/32 7.120.1.20/32 precedence critical

50 permit ip 7.120.1.20/32 7.120.1.10/32

60 permit ip 7.120.1.20/32 7.120.1.10/32 dscp af11

70 permit ip 7.120.1.20/32 7.120.1.10/32 precedence critical

This example shows how to display the status of the global statistics and the configured policy maps on a specific interface:

n1000v(config)# show policy-map interface vethernet 3

Global statistics status : enabled

Vethernet3

Service-policy (qos) input: policy-protoacl

policy statistics status: enabled

Class-map (qos): class-protoacl (match-any)

132 packets

Match: access-group protoacl

132 packets

set qos-group 100

Additional References

For additional information related to implementing system-level HA features, see the following sections:

- Related Documents

- Standards

- MIBs

- RFCs

- Technical Assistance

Related Documents

Related Topic

Document Title

QoS Classification

“Configuring QoS Classification” section

QoS Policies and Marking

“Configuring QoS Marking Policies” section

QoS Overview

“Overview” section

QoS Policing

“Configuring QoS Policing” section

Configuring ACLs

Cisco Nexus 1000V commands

Standards

Standards

Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

—

MIBs

MIBs

MIBs Link

- CISCO-PROCESS-MIB

To locate and download MIBs, go to the following URL:

RFCs

RFCs

Title

No RFCs are supported by this feature

—

Technical Assistance

Description

Link

Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

Feature History for QoS Statistics

This section provides the QoS statistics release history.

Feature Name

Releases

Feature Information

QoS Statistics

4.0

This feature was introduced.

Configuring Class Based Weighted Fair Queueing

This chapter describes how to configure Class Based Weighted Fair Queueing policies on the Cisco Nexus 1000V to prioritize network traffic.

Information About Class Based Weighted Fair Queueing

With this feature the following goals have been addressed:

- Queueing can ensure that any traffic class does not starve other traffic types.

- Respect the bandwidth guarantees for each traffic class.

- Optimize the utilization of the uplink bandwidth.

Class-based weighted fair queueing (CBWFQ) extends the standard weighted fair queueing (WFQ) functionality to provide support for user-defined traffic classes. For CBWFQ, you define traffic classes based on match criteria including protocols, and cos values. Packets satisfying the match criteria for a class constitute the traffic for that class. A queue is reserved for each class, and traffic belonging to a class is directed to the queue for that class.

Once a class has been defined according to its match criteria, you can assign its characteristics. To characterize a class, you assign it bandwidth, and maximum queue limit. The bandwidth assigned to a class is the guaranteed bandwidth delivered to the class during congestion.

To characterize a class, you also specify the queue limit for that class, which is the maximum number of packets allowed to accumulate in the queue for the class. Packets belonging to a class are subject to the bandwidth and queue limits that characterize the class.

After a queue has reached its configured queue limit, enqueueing of additional packets to the class causes tail drop.

The traffic that does not match any of the configured classes is given best-effort treatment. Once a packet is classified, all of the standard mechanisms that can also be used to differentiate service among the classes apply.

For CBWFQ, the weight specified for the class becomes the weight of each packet that meets the match criteria of the class. Packets that arrive at the egress interface are classified according to the match criteria filters you define, then each one is assigned the appropriate weight. The weight for a packet belonging to a specific class is derived from the bandwidth you assigned to the class when you configured it; in this sense the weight for a class is user-configurable.

After the weight for a packet is assigned, the packet is enqueued in the appropriate class queue. CBWFQ uses the weights assigned to the queued packets to ensure that the class queue is serviced fairly.

Configuring a class policy—thus, configuring CBWFQ—entails these three processes:

- Defining traffic classes to specify the classification policy (class maps).

This process determines how many types of packets are to be differentiated from one another.

- Associating policies—that is, class characteristics—with each traffic class (policy maps).

This process entails configuration of policies to be applied to packets belonging to one of the classes previously defined through a class map. For this process, you configure a policy map that specifies the policy for each traffic class.

- Attaching policies to interfaces (service policies).

Note A queueing policy map can only be applied on an uplink in the egress (outbound) direction.

This process requires that you associate an existing policy map, or service policy, with an interface to apply the particular set of policies for the map to that interface.

Policy maps prioritize network traffic by class. You create policy maps to define how to treat each class of traffic so that it is prioritized for the best quality of service.

Information About Class Maps for Queuing

command defines whether you want packets for this class map to match protocol, class of service, or both.

- CoS is specified as a number from 0 to 7.

This matches traffic based on the class of service (CoS) in the IEEE 802.1Q header, defined in IEEE 802.1p. CoS is encoded in the high order 3 bits of the VLAN ID Tag field and is referred to as user_priority.

- The following are pre-defined protocol matches:

– n1k_control

– n1k_mgmt

– n1k_packet

– vmw_ft

– vmw_iscsi

– vmw_mgmt

– vmw_nfs

– vmw_vmotion

- The following are the default COS values associated with the protocols:

– n1k_control: 6

– n1k_mgmt: No default value

– n1k_packet: 6

For VMware protocols such as vmw_ft, vmw_iscsi, vmw_mgmt, vmw_nfs, and vmw_vmotion, Cisco Nexus 1000V does not set any default COS value. See the VMware documentation for more information.

Licensing Requirements for Class Based Weighted Fair Queueing

There are no licensing requirements for this feature.

Prerequisites for Class Based Weighted Fair Queueing

Class Based Weighted Fair Queueing has the following prerequisites:

- You are already logged in to the CLI in EXEC mode.

Guidelines and Limitations

Use the following guidelines and limitations when configuring Class Based Weighted Fair Queueing (CBWFQ).

- A queueing policy can only be applied on an uplink interface in the egress (outbound) direction.

- Queueing is supported on ESX/ESXi 4.1.0 and later hosts.

- For port-channel interfaces, queueing bandwidth applies on the member ports. The overall performance will depend on how the vethernets are pinned to member ports and the traffic pattern on the individual ports.

- We recommend that you reserve 10% bandwidth of the uplink for the control traffic.

Default Settings

Class Based Weighted Fair Queueing is disabled by default.

Configuring Class Based Weighted Fair Queueing Policies

This section describes how to create QoS queueing class policies for the Cisco Nexus 1000V:

Creating the policy consists of the following steps:

1. Create a class map

2. Create a policy map

3. Apply the policy map on an interface

Configuring Class Based Weighted Fair Queueing

This feature allows the user to differentiate traffic classes and provide appropriate bandwidth guarantees.

You can use this procedure to configure class-based weighted fair queueing as follows:

- Create a queueing class map with protocol or CoS matching criteria.

- Create a queueing policy map and assign the class map to it.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

- You are logged in to the CLI in EXEC mode.

- You know whether you want the queueing class map to match protocol or CoS.

- You know whether you want to designate a minimum guaranteed bandwidth for the traffic class.

- You know whether you want to designate a maximum queue size for the traffic class.

SUMMARY STEPS

3. match {cos id | protocol name}

]}]

11. show policy-map interface

DETAILED STEPS

Command

Purpose

Step 1

n1000v# config t

n1000v(config)#

Places you into global configuration mode.

Step 2

class-map type queuing {match-any | match-all} map-name

n1000v(config)# class-map type queuing match-all class_fin1

n1000v(config-cmap-que)

Creates a CBWFQ class map and enters class map queueing mode for configuring the new class map.

match-any: Use this option to apply this class map to a packet if it matches any of the matching criteria.

match-all: Use this option to apply this class map to a packet if it matches all of the matching criteria.

map-name: up to 40 alphanumeric characters in length and can include the hyphen and underscore characters.

Step 3

match {cos id} | {protocol name}

n1000v(config-cmap-que)# match protocol vmw_vmotion

n1000v(config-cmap-que)#

Defines whether you want packets for this class map to match protocol, class of service, or both.

- CoS is specified as a number from 0 to 7.

This matches traffic based on the class of service (CoS) in the IEEE 802.1Q header, defined in IEEE 802.1p. CoS is encoded in the high order 3 bits of the VLAN ID Tag field and is referred to as user_priority.

- The following are pre-defined protocol matches:

– n1k_control

– n1k_mgmt

– n1k_packet

– vmw_ft

– vmw_iscsi

– vmw_mgmt

– vmw_nfs

– vmw_vmotion

- The following are the default COS values associated with the protocols:

– n1k_control: 6

– n1k_mgmt: No default value

– n1k_packet: 6

– For VMware protocols such as vmw_ft, vmw_iscsi, vmw_mgmt, vmw_nfs, and vmw_vmotion, Cisco Nexus 1000V does not set any default COS value. See the VMware documentation for more information.

Step 4

n1000v(config-cmap-que)# exit

n1000v(config)#

Exits class-map queueing configuration mode and returns you to global configuration mode.

Step 5

n1000v(config)# policy-map type queuing Policy-vmotion

n1000v(config-pmap-que)

Creates a CBWFQ policy map and enters policy map queueing mode for configuring the new policy map.

Step 6

Example:

n1000v(config-pmap-que)# class type queuing class_fin1

n1000v(config-pmap-c-que)#

Assigns a CBWFQ class to this policy map and enters policy map class queueing configuration mode.

Step 7

Example:

n1000v(config-pmap-c-que)# bandwidth percent 50

n1000v(config-pmap-c-que)#

Designates the minimum guaranteed bandwidth for this traffic class as a percentage of total available bandwidth.

Step 8

show policy-map [{[type qos] [pmap-name-qos]} | {type queuing [pmap-name-que]}]

Example:

n1000v(config-pmap-c-que)# show policy-map type queuing Policy-vmotion

Type queuing policy-maps

========================

policy-map type queuing Policy-vmotion

class type queuing Match-vmotion

bandwidth percent 50

n1000v(config-pmap-c-que)#

Displays the configuration for verification.

Step 9

n1000v(config-pmap-c-que)# exit

n1000v(config-pmap-que)#

Exits policy-map type queueing configuration mode and returns you to policy-map configuration mode.

Step 10

n1000v(config-pmap-que)# exit

n1000v(config)#

Exits policy-map configuration mode and returns you to global configuration mode.

Step 11

Example:

n1000v(config)# port-profile type ethernet myppte

n1000v(config-port-prof)#

Creates a port-profile and enters port-profile configuration mode.

Step 12

Example:

n1000v(config-port-prof)# service-policy type queuing output my_pmtq

n1000v(config-port-prof)#

Creates a service-policy of type queuing.

Step 13

show policy-map interface

Example:

n1000v(config-port-prof)# show policy-map interface

n1000v(config-port-prof)

Displays the status of the global statistics and the configured policy maps on all interfaces.

Step 14

n1000v(config-port-prof)# copy running-config startup-config

n1000v(config-port-prof)#

(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Verifying the Class Based Weighted Fair Queueing Configuration

To verify the QoS queueing policy configuration, perform one of the following tasks:

Command

Description

Displays the queueing policy map configuration.

See Display Policy Map Type Queuing

Displays the queueing class map configuration.

See Display Class Map

Displays the policy map interface configuration.

See Display Policy Map on Interface

Displays the QoS running configuration.

Example 6-1 Display Policy Map Type Queuing

n1000v# show policy-map type queuing Policy-vmotion

Type queuing policy-maps

========================

policy-map type queuing Policy-vmotion

class type queuing Match-vmotion

bandwidth percent 50

Example 6-2 Display Class Map

n1000v# show class-map type queuing Match-vmotion

Type queuing class-maps

========================

class-map type queuing match-any Match-vmotion

match protocol vmw_vmotion

Example 6-3 Display Policy Map on Interface

n1000v# show policy-map interface ethernet 3/3

Global statistics status : disabled

Ethernet3/3

Service-policy (queuing) output: Policy-vmotion

policy statistics status: enabled

Class-map (queuing): Match-vmotion (match-any)

Match: protocol vmw_vmotion

bandwidth percent 50

Example 6-4 Display Class Map

n1000v# show class-map type queuing Match-Cos

Type queuing class-maps

========================

class-map type queuing match-all Match-Cos

match cos 5

Example 6-5 Display Service Policy on Interface

n1000v# show policy-map interface ethernet 3/3

Global statistics status : disabled

Ethernet3/3

Service-policy (queuing) output: Policy-Cos

policy statistics status: enabled

Class-map (queuing): Match-Cos (match-all)

Match: cos 5

bandwidth percent 50

Example 6-6 Display Service Policy on Interface

n1000v# show policy-map interface port-channel 1

Global statistics status : disabled

port-channel1

Service-policy (queuing) output: Policy-vmotion

policy statistics status: enabled

Class-map (queuing): Match-vmotion (match-any)

Match: protocol vmw_vmotion

bandwidth percent 50

Configuration Examples for Class-Based Weighted Fair Queueing

Example 6-7 Allocating 50% of Bandwidth for vMotion Traffic

conf t

Enter configuration commands, one per line. End with CNTL/Z.

class-map type queuing match-any Match-vmotion

match protocol vmw_vmotion

exit

policy-map type queuing Policy-vmotion

class type queuing Match-vmotion

bandwidth percent 50

exit

exit

interface ethernet 3/3

service-policy type queuing output Policy-vmotion

Example 6-8 Alocating 50% of Bandwidth for Traffic with CoS Value of 5

conf t

Enter configuration commands, one per line. End with CNTL/Z.

class-map type queuing match-all Match-Cos

match cos 5

exit

policy-map type queuing Policy-Cos

class type queuing Match-Cos

bandwidth percent 50

exit

exit

interface ethernet 3/3

service-policy type queuing output Policy-Cos

Example 6-9 Policy-Map with Multiple Traffic Classes

conf t

Enter configuration commands, one per line. End with CNTL/Z.

class-map type queuing match-any class-vmotion

match protocol vmw_vmotion

exit

class-map type queuing match-any class-cos-2

match cos 2

exit

policy-map type queuing policy-priority-vmotion

class type queuing class-vmotion

bandwidth percent 60

class type queuing class-cos-2

bandwidth percent 40

exit

exit

int po1

service-policy type queuing output policy-priority-vmotion

sh policy-map type queuing policy-priority-vmotion

Type queuing policy-maps

========================

policy-map type queuing policy-priority-vmotion

class type queuing class-vmotion

bandwidth percent 60

class type queuing class-cos-2

bandwidth percent 40

conf t

Enter configuration commands, one per line. End with CNTL/Z.

int po1

service-policy type queuing output policy-priority-vmotion

end

sh policy-map interface po1

Global statistics status : disabled

port-channel1

Service-policy (queuing) output: policy-priority-vmotion

policy statistics status: enabled

Class-map (queuing): class-vmotion (match-any)

Match: protocol vmw_vmotion

bandwidth percent 60

Class-map (queuing): class-cos-2 (match-any)

Match: cos 2

bandwidth percent 40

Feature History for Class Based Weighted Fair Queueing

This section provides the Class Based Weighted Fair Queueing release history.

Feature Name

Releases

Feature Information

Class Based Weighted Fair Queueing

4.2(1)SV1(4)

This feature was introduced.

DSCP and Precedence Values

This appendix provides the DSCP and precedence values used in QoS class maps and policy maps.

Commonly Used DSCP Values

Unless noted as a restriction, you can mark both incoming and outgoing packets.

.

Table 7-1 Commonly Used DSCP Values

DSCP Value

Decimal Value

Meaning

Drop Probability

Equivalent IP Precedence Value

101 110

46

High Priority

Expedited Forwarding (EF)

N/A

101 - Critical

000 000

0

Best Effort

N/A

000 - Routine

001 010

10

AF11

Low

001 - Priority

001 100

12

AF12

Medium

001 - Priority

001 110

14

AF13

High

001 - Priority

010 010

18

AF21

Low

010 - Immediate

010 100

20

AF22

Medium

010 - Immediate

010 110

22

AF23

High

010 - Immediate

011 010

26

AF31

Low

011 - Flash

011 100

28

AF32

Medium

011 - Flash

011 110

30

AF33

High

011 - Flash

100 010

34

AF41

Low

100 - Flash Override

100 100

36

AF42

Medium

100 - Flash Override

100 110

38

AF43

High

100 - Flash Override

001 000

8

CS1

1

010 000

16

CS2

2

011 000

24

CS3

3

100 000

32

CS4

4

101 000

40

CS5

5

110 000

48

CS6

6

111 000

56

CS7

7

000 000

0

Default

101 110

46

EF

IP Precedence Values

precedence values from least to most important.

Table 7-2 Precedence Values

Value

Description

000 (0)

Routine or Best Effort

001 (1)

Priority

010 (2)

Immediate

011 (3)

Flash (mainly used for voice signaling or for video)

100 (4)

Flash Override

101 (5)

Critical (mainly used for voice RTP)

110 (6)

Internet

111 (7)

Network

QoS Configuration Limits

shows the maximum configuration limits for QoS.

Table 8-1 QoS Maximum Configuration Limits

QoS feature

Maximum Limit

Match criteria per class-map

32

Class-maps per policy map

64

Class-maps per server

64 (with policers)

Policy-maps per server

16

Service Policies per server

128

Cisco Nexus 1000V Quality of Service Configuration Guide, Release 4.2(1)SV1(5.1)

October 29, 2012

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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 . 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. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2009-2016 Cisco Systems, Inc. All rights reserved.