Above qos map is fairly default except from the maps I created to put voice traffic in prio queue 3. for now this is all I want to confure.
Question 1: By looking at the map it seems values 0-15, 16-31, 26 32-47 and 58 - 63 are distributed over the different queues. Since we have no other qos traffic then dscp
46 and 26 I assume all other traffic is default 0. So where does this traffic go? - only to queue 1? Or is is distributed still? - Do I have to set all other queues to dscp 0?
Question 2: This would be fairly easy to check if there is a command which would show you the different queues and stats of packets going through, however I have not found such a command. Is there a way to monitor this process at all?
First of all by classifing COS you do not really accomplish any QoS. It's only the first step. For LAN QoS you want to create expedite queue, for voice on 4500 switch you need to do it by appliying "tx-queue 3" and "priority high" commands to the interfaces. This way all of you DSCP 32-47 (COS 3 - default for RTP stream).
If you read my post you can see I already configured this. But that's not my question. There are 4 queues, one the expidite which I am sending Cos 3 (dscp 32 - 47) traffic. But the other queues all seem to have different ranged attached to them does this mean there is no traffic at all going to queues 2 and 4 (I dont have any cos or dscp traffic in that range) Anyway, it's all in my original post.
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...