I have a CallManager 5.x connected to a 3750 stack with auto-qos enabled. Also off that stack, on another VLAN, I have my router connecting across the WAN. However, my service-policy on the router serial interface indicates that no control packets marked with eitehr COS3 or AF31 are coming in. "Show mls qos interface stat" on the 3750 shows packets coming in from CM marked with AF24 (CS3), however, the output of the 3750 port towards the router doesn't indicate packets with those same markings being transmitted towards the router. It appears as though the 3750 stack is re-writing the DSCP values for call-control. I have not done any QoS config on the 3750 interface VLANS. Does anyone have any idea? Please see the attached notepad for better illustrative purposes. THANKS!
DiffServ is one of two QoS architectures for IP networks defined by the IETF. In this model, packets entering a DiffServ-enabled network are grouped into a small number of classes. For example, VoIP packets can be grouped into the premium class, while e-commerce HTTP packets are grouped into the gold class, and so on. Furthermore, each class has a color or mark associated with it. This makes packet classification extremely scalable and assures appropriate bandwidth and delay guarantees in the network core. Thus, when they enter the network, packets are marked based on classification policies at the network boundary nodes. The boundary nodes also apply traffic conditioning functions to control the amount of traffic entering the network. Traffic conditioning includes shaping (smoothing the rate at which packets are sent into the network) and policing (dropping packets that are in excess of a subscribed-to rate; or re-coloring the ones exceeding the rate, so that the probability of dropping them increases when there is congestion in the core). Each node within the network then applies different queuing and dropping policies on every packet based on the marking that packet carries.
Typically for both CallManager and Routers, you will want to trust DSCP rather than COS. The outgoing queue indicates that all of your traffic is being marked as COS 0 for that port as it is put on the wire.
A few things:
1) If you are going to stick with AutoQOS, try trusting DSCP on the CallManager and Router ports using mls qos trust dscp.
The above recommendation to trust DSCP is a good one. Enabling mls qos in a switch also means that ports are NOT trusted unless specifically configured to do so. Not being trusted means the switch rewrites everything to 0 that is not trusted.
Also, just as an FYI --
DSCP is in the Layer 3 IP header, so it will go end-end.
COS is in the layer 2 VLAN header and only seen where packets trunked.
Trust DSCP per the QOS SRND( solution reference network design ).
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...