Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

QoS configuration???

Status
Not open for further replies.

JASEN40

Technical User
Oct 20, 2005
3
US
Ok, here is the deal;

I need to tag 3 classes of service,
1)Network
2)Immediate
3)Basic

I need all traffic from 3 IP's for Voice, and 1 IP for Video tagged with a precedence of 7(Network)

I need all traffic from all IPs from a range of TCP ports tagged with a precedence of 2(Immediate)

And all other traffic I need tagged with a precedence of 0(Basic)...I think that is the default?

My questions are as follows...

Will I be able to classify the voice and video traffic with one class-map? Or does there need to be two seperate ones?

How do you apply a class-map/policy-map once you have created it?

Any help or direction anybody would be able to provide would be greatly appreciated.

Jasen
 
Look up CBWFQ and LLQ on and you'll find everything you need to configure this setup. I not sure about your idea of tagging traffic with precedence 7, though. I believe that 6 and 7 are reserved and that the highest we should use is 5.
 
As jneiberger says you are advised against using precedence above 5. However you can use it if you really want to.

Usually people allocate normal (untagged) traffic to 0. Non-interative data traffic that needs some kind of special treatment usually use get precedence 1-4. Voice/Video/Interactive data is usually assigned precedence 5 (note that VoIP RTP call control traffic is usually not marked with precedence of 5 but is usually given special treatment over non-marked data flows, for example precedence 3)

It's best to mark the traffic as close to the source as possible (i.e. the directly-connected LAN access switches). However this may not always be possible or even advisable if you aren't responsible for those switches. In environments like that, I would usually recommend that you remark all traffic (even if it was previously marked) at your demarc point (aka trust boundary).

Once you've marked your traffic, you then need to queue it accordingly. Using Cisco's policy maps, gives you one priority queue to play with. If you are deploying voice and video, they should be assigned to this queue. Try and avoid allocating data to this queue also (unless VoIP has not been implemented) as this may cause jitter problems with voice. The rest of the queues are simply weighted (as per the Weighted Fair Queuing idea) based on the bandwidth allocations you've allocated.

Have a read of the the following URL from Cisco. It's excellent at breaking down CBWFQ and LLQ with lots of good examples:

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top