Using An Mqc Object; Type Qos Policies - Cisco Nexus 7000 Series Configuration Manual

Using Modular QoS CLI
For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide.

Using an MQC Object

You configure QoS and queuing policies using the MQC class-map, policy-map, and table-map objects. You
cannot use table maps in queuing policies. After you configure class maps and policy maps, you can attach
one policy map of each type to each of the ingress or egress directions of an interface. The figure below lists
the maximum QoS and queuing policies that you can define on each interface.
Figure 1: Maximum QoS Policies Per Interface
A policy map contains either a QoS policy or queuing policy. The policy map references the names of class
maps that represent traffic classes. For each class of traffic, the device applies the policies on the interface or
VLAN that you select.
A packet is matched sequentially to a class of traffic starting from the first traffic class definition. When a
match is found, the policy actions for that class are applied to the packet.
The reserved class map 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. You use class-default to perform mutations (mutation is
a method for translating QoS values in the packet header prior to traffic classification).
Note You can access user-defined MQC objects only in the VDC in which they were created. You can access the
system-defined MQC objects in all VDCs.

Type qos Policies

You use type qos policies to mark, to apply mutations, to set the ingress port trust state, and to police packets.
The figure below shows the QoS policy structure with the associated MQC objects of type qos without
mutation.
Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide
Using an MQC Object
11