From: ccie2be (ccie2be@nyc.rr.com)
Date: Wed Jan 12 2005 - 20:46:24 GMT-3
Thinking and playing around with the numbers I used versus
the IE solution, I now think my original solution is wrong.
Here's why.
With MQC, by default, max-reserved-bandwidth is 75%, leaving 25% for
all other non-explicitly defined traffic.
While, custom-queueing, by default, reserves only 1500 bytes per cycle
for non-defined traffic. This works out to be 15% of the bandwidth in the
problem below.
Therefore, to make my solution - using the command, bandwidth remaining
percent,
equivalent, I need to change max-reserved-bandwidth to 85.
The key to this working and being equivalent is computing the correct
the max-reserved-bandwidth value. In this lab problem, the 1500 bytes
reserved for the default turned out to be = 15% and
15% + max-reserved-bandwidth of 85% = 100%
So, the trick is to first compute the percentage of bandwidth
used by the default custom queue. Then subtract that from 100%
of the bandwidth.
Then set the max-reserved-bandwidth to that amount ie 100 - 15 = 85%
What do ya think? (Personally, I think I got it right this time.)
Before, I thought I found a shortcut, but now, it looks like
eihter method you use, this new method or the IE method,
you need to remember that custom queueing reserves 1500 bytes
for the default queue and you have to set the max-reserved-bandwidth
correctly.
For example, with custom-queueing, if you add up all the queues, you get
5000 + 3000 + 500 + 1500 (for default queue) = 10,000 bytes per cycle.
So, for www traffic, 5000 / 10,000 = 50 % of bandwidth is used.
Using my method / solution, if max-reserved is changed to 85%, then
5000/8500 = 58.82% and
58.82 % times 85% of the remaining bandwidth = 49.999 of the bandwidth
> Hi guys,
>
> Problem:
> Convert the legacy custom queue config to MQC.
>
> queue-list 1 protocol ip 1 tcp www
> queue-list 1 protocol ip 2 tcp ftp
> queue-list 1 protocol ip 2 tcp ftp-data
> queue-list 1 protocol ip 3 tcp telnet
> queue-list 1 default 4
> queue-list 1 queue 1 byte-count 5000 limit 30
> queue-list 1 queue 2 byte-count 3000
> queue-list 1 queue 3 byte-count 500
>
>
> My Solution was:
>
> class-map match-all TELNET
> match protocol telnet
> class-map match-all FTP
> match protocol ftp
> class-map match-all WWW
> match protocol http
> !
> policy-map MQC
> class WWW
> bandwidth remaining percent 58
> queue-limit 30
> class FTP
> bandwidth remaining percent 35
> class TELNET
> bandwidth remaining percent 6
>
> Question:
>
> Is my solution which is different from that shown in the IE SG equally
> correct?
>
> I think my solution is better and simpler, assuming it's correct, because
it
> doesn't require
>
> you to know that, by default, custom queueing reserves 1500 Bps for the
> default queue and it doesn't require
>
> you to change the max-reserved-bandwidth on the output interface.
>
> What do you guys think?
>
> Tim
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Feb 02 2005 - 22:10:22 GMT-3