Configuring Queuing And Scheduling; Configuring An Ingress Queuing Policy - Cisco Nexus 7000 Series Configuration Manual

Configuring Queuing and Scheduling

• Ports in a port channel with a user-defined policy attached should have this same user-defined policy
• When a user-defined policy map is attached to a port group, the set cos and bandwidth commands are
• Shared buffer queuing does not apply on the FEX Hif ports.
• When changing egress Class of Service (CoS) to queue mapping, ensure that you specify 2 or 3 seconds
• The M3 modules do not support per-queue counters for egress drops (multicast, unknown unicast, or
• Only 8e templates are supported on M3 modules.
• The M3 module supports only network-qos template with default-nq-8e-4q8q-policy. It does not support
• The M3 module supports only the network-qos template. This template contains all the CoS values that
• All data traffic will be enqueued to the default queue of dot1q-tunnel port because this port is untrusted
• Starting with Cisco NX-OS Release 8.0(1), the dscp-to-queue mapping for M3-Series modules is enabled
Configuring Queuing and Scheduling
You configure queuing and scheduling by creating policy maps of type queuing that you apply to either traffic
direction of an interface. You can configure a queuing policy by following one of these methods:
• Copying predefined policy—You can copy a queuing policy template and modify it as needed.
• User-defined policy—You can create a queuing policy that conforms to one of the system-defined queuing
For information about configuring policy maps and class maps, see "Using Modular QoS CLI."

Configuring an Ingress Queuing Policy

You must modify the ingress queuing policy only if you want to change the default policy that the port inherited
from the system default.
Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide
126
attached to the port groups.
not applicable to the port group.
as the minimum time limit between changes. Otherwise, continuous traffic drop might occur.
broadcasts). The egress drops will be per port and per Q-Default counter.
default-nq-4e-4q8q-policy, default-nq-6e-4q8q-policy, default-nq-7e-4q8q-policy, and
default-nq-8021qav-4q8q-policy.
match the MTU size.
by default.
by using the hardware qos dscp-to-queue ingress module type f-series command.
Note When you copy an ingress or egress queuing policy, you are also copying the
internal policies for the hierarchical queuing policy. Copying shortens the default
policy name by stripping the default and policy substrings from it.
policy templates.
Configuring Queuing and Scheduling on F-Series I/O Modules