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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Bandwidth

Status
Not open for further replies.

tonyktone

MIS
Aug 31, 2004
59
0
0
Hi everyone,

I have a cisco 2600 series router...I want to allocate certain bandwidth for a particular application...How do I go about doing this? I'm new to cisco, any help would greatly be appreciated?
 
you want to give an application a certain amount of bandwidth to use, then you use CBWFQ method of QoS..

if you want to limit the application, then you need to look at policing..


BuckWeet
 
Priority queuing, like all methods of queuing can only be enabled on interfaces with bandwidths less than 2.048 Mbps. In other words, you aint gonna configure queuing on an ethernet interface. So it's for a WAN link, like ISDN or frame relay. Now listen up people! If your link is already overloaded, queuing won't help. It's only to prioritize time sensitive traffic over lower priority traffic. With Priority Queuing, you can have up to 4 queues. They are called: high, medium, normal and low. Priority queuing is configured using the priority-list command. The priority list assigns incoming packets to each of the 4 queues based on arguments you configure.



The high priority queue is always emptied first, then the medium queue gets emptied. Next the normal queue gets emptied and finally the low queue gets emptied. If the high queue is always full and never gets emptied, none of the other queues will ever get serviced. That sucks! This is why you probably don't want to use priority queuing, you probably want to use custom queuing. Oh, one more thing, people, if a lower priority queue is getting serviced and traffic arrives into a higher priority queue, you guessed it, the router forgets all about the queue it was servicing and immediately takes care of the higher priority queue. Now that I think of it, Hollywood runs the same way.


Now check this out, you had better assign a default queue for traffic that you forgot to include in the other queues. Use the priority-list default command. Your boss swore up and down that the only protocol on the network was IP, but what he doesn't know is there is an IPX server that has been in QA since 1988. Moral of the story, configure a default queue. You can prioritize incoming packets based on protocol or interface. You can even use the keyword list to call an access list. Hot Damn! Oh, yeah, one more thing you can use the priority-list queue-limit command to change the maximum number packets allowed in each queue to begin with. By default from high to low, it's 20, 40, 60 and 80. Here's a sample config I worked out :

!
priority-list 1 protocol ip high tcp 23
priority-list 1 protocol ipx medium
priority-list 1 interface ethernet 1 medium
priority-list 1 protocol ip list 112 normal
priority-list 1 default low
!
interface serial 0
priority-group 1
!






I'm the Fanciest of the Fancy...INDEED
 
or use CBWFQ, priority queueing isn't very scalable...
 
Look into RSVP for a more specific bandwidth to application reservation and it works well on LAN Technologies.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top