We have the following QoS config running on Edge, Distributions and Cores and got the following error.
âpriority command is not supported in output direction for this interface
Configuration failed on: Port-channelâ
We had opened a TAC case and they said â PFC QoS does not support these policy map class commands:
How can we prioritize voip traffic. On our monitoring application, it says queues empty. Even if the priority command is not working there should be traffic in the queue.Different version of supervisors in Distribution (sup720) and COREs (Sup2).
Any suggestions? Attached document gives Config details.
If you properly classify, mark and police your traffic in the access-layer, you could simply trust the dscp value in the distribution and core layers instead of attempting to reclassify and remark the traffic.
You would still need to properly setup your transmit queues based on the tx-queue capabilities of your modules. Of course if you are running L2 in your access layer, then you would need to classify and mark your traffic in the distribution layer. Instead of doing port-based, use VLAN based classification.
There are great explanations and examples in this book:
One final question/comment: What QoS "monitoring application" are you using? QoS on the 6500 series is done in hardware and there are no SNMP MIBs to query (i.e., cbQosCMCfgTable, cbQosServicePolicyTable
Thanks for replying. We are classifying traffic on our access-layer switches. We are running layer 2 in our access layer. We are turning on QoS and modifying default COS map on our access-layer switches as shown below:
mls qos map cos-dscp 0 8 16 26 32 46 48 56
And we are configuring QoS on the uplink port of the switch to Distribution (Catalyst 6500) and trunking voice vlan. See below:
mls qos trust dscp
switchport trunk allowed vlan 801-802
On our Distributions and Cores, we are trusting DSCP and applying the service policy outbound on the port-channels.See below:
mls qos trust dscp
service-policy output voip-policy
On our Distributions, We are defining policy-maps:
class-map match-any voip-class
match ip dscp ef
The monitoring application is NetMRI. It doesn't give lots of details but says "Queues empty"
We also use NetMRI and you're correct, because the Cat 6500 PFC performs classification, marking, mapping, and policing functions, but the queuing and dropping policies are administered by the line cards, there are no MIBs for NetMRI to poll.
Thanks Steve. We are using catalyst 3750 or 3550 on access-layer with SMI code. The DIstribution box has Sup 720 and Cores have Sup 2. The IOS on them is s72033-ipservicesk9-mz.122-18.SXF8.bin
I did not get a chance to read that document.We are mapping COS-to-DSCP on our access-layer switches and making sure Dist and Cores trust DSCP but we are not redefining the boundaries there.We are doing CBWFQ for voice and video.
Please read over the SRND document I referenced earlier, it provides the best explanations and examples for exactly what you want to accomplish for each type of switch in Access, Distribution, Core layers.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4