02-25-2015 11:32 PM - edited 03-07-2019 10:51 PM
Hi,
I have been referring 9k qos doco - (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/qos/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Quality_of_Service_Configuration_Guide/b_Cisco_Nexus_9000_Series_NX-OS_Quality_of_Service_Configuration_Guide_chapter_01...
If I want to configure class-map & policy-may type of queuing, will it overwrite default queuing configuration? And can I apply it to specific interface or I have to apply at system level?
I know in the document it is mentioned to apply at system level and hence affect all ports except 40G on egress. But some examples I have seen have specifically used queuing policy at interface level. My preference is to configure new queuing policy and only apply to interface that I need to without affecting default configuration. Is it possible?
Thanks in advance.
04-20-2018 12:12 AM
System-defined queuing class maps are provided.
ou can use the following methods to proactively avoid traffic congestion on the device:
Apply WRED to TCP or non-TCP traffic.
Apply tail drop to TCP or non-TCP traffic.
For egress packets, you can choose one of the following congestion management methods:
Specify a bandwidth that allocates a minimum data rate to a queue.
Impose a minimum and maximum data rate on a class of traffic so that excess packets are retained in a queue to shape the output rate.
Allocate all data for a class of traffic to a priority queue. The device distributes the remaining bandwidth among the other queues.
For information about configuring congestion management, see the Configuring WRED on Egress Queues section.
You can configure WRED on egress queues to set minimum and maximum packet drop thresholds. The frequency of dropped packets increases as the queue size exceeds the minimum threshold. When the maximum threshold is exceeded, all packets for the queue are dropped.
SUMMARY STEPS
1. configure terminal
2. policy-map type queuing {[match-first] policy-map-name}
3. class type queuing class-name
4. random-detect [minimum-threshold min-threshold {packets | bytes | kbytes | mbytes} maximum-threshold max-threshold {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
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide