12-21-2007 03:55 PM - edited 03-05-2019 08:07 PM
I have been studying QoS for some time now and am familiar with the tools and commands that Cisco provides for configuring QoS.
Recently, my company has given me the task of creating a QoS policy. We will be deploying VoIP and video very soon and my task is to prepare the network for this endeavor.
While there are lots of documents describing how to configure QoS, I only find a few documents on how to design a policy. In particular, let's say that I have a packeteer or other similar device that can classify traffic and tell me what the average / peak traffic rates are. What is the proper way of setting up queuing if you have this information?
I know that for voice, I need to look at the codecs that will be used (G729 in my case) and the Call Admission Controls to determine what my voice BW requirements are (as well as the other basics such as future traffic growth, etc).
What I don't know is how to size my other traffic queues? Should I classify the traffic and just add up the average BW usage for the class? Or should I provide a BW to provide for the peak rates (I doubt I have that much BW to divide up).
I guess - what are your recommendations? Currently I am looking at LLQ to provide for my voice / video traffic (perhaps 2 priority queues, 1 for each type of traffic). Any and all help is appreciated!
Jim
12-28-2007 11:33 AM
You can enable Auto Qos in your devices.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a0080500b8f.html
12-28-2007 07:37 PM
Jim, first idea: go to this URL http://www.cisco.com/en/US/netsol/ns656/networking_solutions_program_home.html and read the "Enterprise QoS Solution Reference Network Design Guide Version 3.3" This guide has an excellent explanation of many of the things you've been studying, as well as the differences between devices (hardware queues, capabilities, etc.) It discusses Auto-QoS which is ONE TOOL for QoS but not a global panacea.
Second, in my real world experience, I do (almost) everything based on BW% not BPS. My basic policy defines 35% BW for LLQ for VoIP, 50% BW for production applications (Citrix, specific http/s traffic, SAP), 5% reserved for ssh/telnet/snmp/syslog/ftp/etc. and everything else in the default. Many WAN providers won't go >35% for the priority queue anyway.
I have some QoS templates for routers and switches, drop me a line if you'd like a copy.
HTH
Paul
01-09-2008 08:45 AM
Paul,
I am interested in taking a look at your QoS templates for routers and switches. Can you send me a copy?
Thanks,
Jim
01-10-2008 11:27 AM
I sent these to your Profile email, did you get them?
Paul
01-10-2008 01:20 PM
Excellent
01-10-2008 01:23 PM
Surely, but you have no email listed. Drop me a note at ptrivino@arrowheadgrp.com and I'll reply with it.
Paul
01-10-2008 01:29 PM
Thanks.
01-10-2008 11:47 PM
i also looking for template of QOS so if is not too much trouble please send me to anis_nane@hotmail.com
thanks a lot
01-11-2008 05:55 AM
Hi,
As another good example of a policy check out the following paper:
http://www.amilabs.com/NYutility/NYCUTILITY%20QoS%20Strategy.pdf
Even if you don't have exactly the same requirements there are still many good ideas here.
HTH
Andrew.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide