Our company has a 3/.5 DSL connection. On this connection we have a VPN where the execs are able to access files on the network as well as VOIP. On this connection we also have our exchange email server.

I would like to decrease the amount bandwidth that is used by the exchange server to give more to the VPN...specifically the VOIP.

My hope is there something I put on the particular port to slow its access speed.


  • What model of switch? Be aware that you can't control the download utilization.
    – Ron Trunk
    Commented Mar 9, 2017 at 18:27
  • If your switch supports the same features as the Catalyst 3560, then you might find the answer here: networkengineering.stackexchange.com/questions/32544/… Commented Mar 9, 2017 at 21:43
  • I do have the 3560 and will be upgrading to the 3650's. I will check out the link thanks. Commented Mar 10, 2017 at 12:26
  • Did any answer help you? If so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you can provide your own answer and accept it.
    – Ron Maupin
    Commented Aug 6, 2017 at 23:06

1 Answer 1


What you need to do is implement QoS. QoS is a very large and complex subject (too broad for details here, as entire books are written on how to use it) that encompasses everything from classifying and marking packets, to performing some sort of action (shaping, policing, queuing, etc.) based on the classification/marking. To properly implement QoS, you need to have a comprehensive set of QoS policies that are implemented consistently across your network.

Also, understand that your QoS policies and markings will not work on the public Internet. You may be able to pay your ISP to respect some of your QoS policies and markings, but QoS on any traffic sent from your ISP to others on it way to the destination will be ignored. You also have no direct control of any traffic coming from the public Internet until you have received it on your network, where you can properly mark and treat it.

To properly treat the traffic, you need to first mark it, and you want to do that as close to the source as possible, ideally on the source device, but you can get into trouble simply trusting applications. Practically, this means marking on the access switches as the traffic comes into the access switches.

Some Cisco switches default to marking everything coming as BE (Best Effort). You probably want most traffic to be marked BE, but you will want VoIP data to be marked EF (Expedited Forwarding). You will also want to mark some things, e.g. control traffic (VoIP control, routing protocols, etc.), with a higher priority, but not EF, and you will want to mark some things, e.g. server backup, with a lower priority.

Once you have your traffic properly marked, then you want to use that. Cisco switches can do some limited queuing, but you certainly want to use the markings on your routers where you can do queuing, policing, and shaping. Typically, you will want to set up a priority queue for VoIP to guarantee some bandwidth, and you really want to police any traffic beyond the priority queue bandwidth. Other traffic will have various queue sizes.

You really want to keep it fairly simple. A rookie mistake is to try to set up markings and queue for every different traffic type. The simplest, and often best, QoS policies leave most traffic as BE, and you only mark and treat differently any exceptional traffic like VoIP, control, or bulk traffic.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.