Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Best QOS Practice for a congested Uplink Port?

I have an MPLS uplink port to a carrier that carries both voice and data.

For example, Customer 3750 Switch 100MB Uplink--->100MB Uplink Carrier Router---Carrier Router 6MB MLPP Voice/Data MPLS Uplink with QOS configured for Voice subnet on carrier side too.

The port occasionally suffers from overutilizition and spikes to the full 6MB

I have a centralized CUCM that has phones that occasionally reset due to TCP 2000 timeouts (usually during the period of high utilization)

So that I can avoid most phone resets during high utilization I have prioritized all voice traffic (signalling and RTP streams) to EF

My question: What is best practice configuration for a congested uplink port? I'm going to assume the answer is it depends (the all great technical answer )

Here are my thoughts on how to configure the 3750 uplink port so far:

apply mls qos trust dscp

apply priority-queue out

(Here's where I'm looking for help)

apply some sort of policing or bandwidth statement on the interface to protect the voice traffic: What are the recommendations and what would those configurations look like?

I would apply these these configurations to the uplink ports at the edge site as well as the central site.

Any thoughts as to the best way to accomplish this?

Everyone's tags (2)
Super Bronze

Re: Best QOS Practice for a congested Uplink Port?


The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.


You want to prioritize VoIP traffic at congestion points, which for you, looks to be whenever your LAN bandwidth hits your 6 Mbps WAN.

If the carrier takes your 100 Mbps, and doesn't just generally police all traffic to 6 Mbps, but instead has different priority queues for the 6 Mbps, all you should need to do, is insure you traffic is correctly processed by your WAN vendor.  This, though, might require marking your traffic for the WAN provider.

If you carrier first polices all your traffic at 6 Mbps (many do), then you need to shape the traffic (with you own prioritization) before the provider "sees" it.  If you need to "shape" on the 3750, there's a command to limit a port's bandwidth utilization, as a percentage.  However it's not exact, so you may need to "shape" slower than 6 Mbps to insure 6 Mbps won't be exceeded.  (BTW, for 6 Mbps, if you need to do QoS, you would be better off with an ISR.)

You also mention 6 MLPPP, but it's unlclear what your device is for that.

How to configure 3750 QoS is involved.  Basically when you enable QoS, each port has four dedicated egress queues.  By default, different traffic markings go into one of the four queues, each queue has same share of the bandwidth, and almost same share of the buffers.  The PQ command you noted, enables the first queue to always transmit its packets first.  Normally, you'll want to do that for VoIP bearer packets, which you've (insured are) directed to that queue.  You also want to insure that VoIP signally packets are not likley to be dropped and, more or less, are forwarded quickly.

Cisco has multiple papers on QoS configurations, including papers for 3750s, so instead of my trying to present that, the above is intended as an overview.  Feel free to post additional questions, the more specific, the more likely you'll get an answer.