nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

delayed in the switch. The primary consideration for using the strict priority queue is to be
careful about what traffic is mapped into the priority queue. Inadvertently mapping too much
traffic into the priority queue can create a situation called queue starvation. In queue
starvation, the strict priority queue constantly has traffic in it that needs to be serviced, and
the other queues on the interface do not get access to transmit their data and in essence
starve.
The M-series modules can support the 1P queue as a strict priority queue when the priority
command is added to the queue; otherwise, it is a regular queue. This is default behavior as
illustrated by the priority level 1 command. Example 10-8 illustrates the use of the priority
command on the queue.
Example 10-8. Displaying a Strict priority Queue on an M Series Module
Click here to view code image
N7K-2# show mod 4 | i Mod
Mod Ports Module-
Type Model Status
4 8 10 Gbps Ethernet XL Module N7K-M108X2-
12L ok
N7K-2# show policy-map int e4/2 type queuing
Global statistics status :
enabled
Ethernet4/2
Service-policy (queuing) input:
SNMP Policy Index: 301991185
default-in-policy
Class-map (queuing): in-q1 (match-any)
queue-limit percent 50
bandwidth percent 80
queue dropped pkts : 0
Class-map (queuing): in-q-default (match-any)
queue-limit percent 50
bandwidth percent 20
queue dropped pkts : 0
Service-policy (queuing) output:
SNMP Policy Index: 301991194
default-out-policy
Class-map (queuing):
priority level 1
out-pq1 (match-any)