(just pinched the text from a question posted a month ago)
But I have exactly the same issue.
original text ....
just enabled QoS in a 6509 (mls qos).
My main requirement is about having counters so see how many packets for each CoS/DSCP type each interface is sending and/or receiving.
Additionally, how many of these are sent to each one of the queues (how many to the high priority queue and how many to the others).
The command I found (show queueing interf gig x/y)
includes counters for packets being discarded. This is nice but gives you information only when congestion happens. During normal operation it is all zeros.
Smaller switches like the 3750 or 3560 include the following command: "show mls qos interface x/y stat". Gives me the counters I want. Nevertheless, does not exist in the 6500s.
In a summary, I want to have no concerns about VoIP traffic not using the high priority queues. I also want to make sure we don't have any rogue packets using the high priority queues. Get the idea? Any other commands you may know to verify this?
How about netflow? If you're serious about monitoring QoS then a netflow analysis tool is essential. For example, you could pick a time period and a particular QoS value and see all the conversations associated with it which is far better info than what you get from the counters.. (assuming you had some counters :-)
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...