I have a query re QoS settings on a 3560 switch. The switch has PCs and VOIP phones attached.
The 3560 is configured with what is a basically an AutoQos config. The dscp mappings, queue thresholds etc are all there in the 'sh run'. However, a 'sh mls qos queing interface f0/1' ( f0/1 is the main uplink port) returned the following:
Egress Priority Queue : disabled
Shaped queue weights (absolute) : 25 0 0 0
Shared queue weights : 25 25 25 25
The port bandwidth limit : 100
The port is mapped to qset : 1
This concerned me. With VOIP I would have expected the priority queue here to be enabled. It isn't. The weights are all equal too.
Can anyone tell me if this is a matter of concern - should I enable the Egress Priority Queue?
Personally, I wouldn't leave AUTOQOS on. I would disable it. We've seen many instances where it shutting it off "fixes" issues. Plus, some earlier IOS versions had the WRONG dscp mappings. The SRND actually does a good job of showing you access ports, uplinks, phone ports, Call Center agents, softphone, etc. with configurations for each. Of course with some of the 2960 switches the policing options aren't as granular as the 3560's and higher switches.
Again if you aren't running into congestion issues, queueing won't even come into play. Its also preferable to mark the traffic as close to the source as possible.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...