[nsp] Custome Queueing

[Brad Bonin]

Here is how I would consider doing it.  Custom queuing forces you to
identify the maximum number of bytes allowed to be transmitted out of
each defined queue.  As soon as the byte limit is reached, the current
packet is transmitted(must send all of the packet).  Then, on to the
next queue.
 
The easy way to figure out how to "carve" up your bandwidth is to define
the byte limit in each queue based upon a predetermined ratio.  For
instance,
 
 
Queue 2 - www - Gets 50% of bandwidth during a given interval
 
Queue 3 - ftp - Gets 25% of bandwidth during a given interval
 
Queue 4 - pop3 - Gets 25% of bandwidth during a given interval
 
 
So, the default byte limit is 1500 bytes per queue.  Here are your
queues:
 
queue-list 1 protocol ip 2 www
queue-list 1 protocol ip 4 ftp
queue-list 1 protocol ip 6 pop3
 
queue-list 1 queue 2 byte-count 3000
queue-list 1 queue 4 byte-count 1500
queue-list 1 queue 6 byte-count 1500
queue-list 1 default 1500
 
 
So, assuming negligible traffic in your default queue, the www queue
should utilize 50% of the available bandwidth and ftp and pop3 each will
utilize 25% respectively.  The percentages won't be exact because of
varying packet sizes.
 
Also, check your avg. packet size, if you have small packet sizes, you
may have to increase queue depth from default of 10 packets per queue.
 
Hope this help,
 
Brad
-----Original Message-----
From: cisco-nsp-bounces@puck.nether.net
[mailto:cisco-nsp-bounces@puck.nether.net] On Behalf Of Rakesh Menon
Sent: Friday, December 13, 2002 10:04 AM
To: cisco-nsp@puck.nether.net
Subject: [nsp] Custome Queueing





Hi,
 
Would like some help in configuring custom queueing in cisco router.
Incase i have to divide the bandwidth among www , ftp and pop3 how
should i be configuring the same. let says for eg - www to be 64kbit ,
ftp - 32kbit , pop3 - 32kbit. And also how do we monitor that each
application is getting the specified bandwidth. All this will be applied
in one custom-queue-list in the interface. 
 
Rgds

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/cisco-nsp/attachments/20021213/6ffd5743/attachment.htm