From: Todd Carswell (acarswell@xxxxxxxxx)
Date: Mon Apr 01 2002 - 15:53:35 GMT-3
Carl,
No, your config will not allocate 50% of the bandwidth for IP traffic.
Try this one out...
queue-list 1 protocol ip 0
queue-list 1 protocol bridge 2
queue-list 1 protocol dlsw 3
queue-list 1 queue 1 byte-count 6000
queue-list 1 queue 2 byte-count 3000
queue-list 1 queue 3 byte-count 3000
Using the "limit" option will only change the number of packets allowed in
the queue. To allocate bandwidth percentages, you need to specify the
byte-count for each queue so that you get the desired bandwidth percentages.
Custom Queueing works in a round robin fashion. It will go to queue #1 and
send the specified number of bytes, then it will go to queue #2, and so on.
In the config that I've put here, IP gets 50% of the bandwidth and the other
2 protocols get 25% each.
Here's another way to look at it: In this scenario, custom queueing will
transmit a total of 12,000 bytes of traffic each time it cycles through all
of the queues. Since IP's byte-count is set at 6000, it will get 50% of the
bandwidth.
Hope that helps!
Todd
----- Original Message -----
From: "Carl Phelan" <carlphelan@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Monday, April 01, 2002 12:07 PM
Subject: Custom Queueing
> Hi All,
>
> Can anyone tell me if this custom queue list is ok to allocate 50% of
> bandwidth to IP, 25% to bridging and 25% to dlsw considering IP has a
> packet size of 2048, bridging a packet size of 512 and dlsw a packet
> size of 256?
>
>
>
> queue-list 1 protocol ip 0
> queue-list 1 protocol bridge 2
> queue-list 1 protocol dlsw 3
> queue-list 1 queue 1 byte-count 6000 limit 2048
> queue-list 1 queue 2 limit 512
> queue-list 1 queue 3 limit 256
>
> Many thanks,
>
> Carl
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:51 GMT-3