From: Jason Alex (amr.ccie@gmail.com)
Date: Thu Mar 05 2009 - 11:42:29 ARST
Sorry the Legacy QOS is
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
On 3/5/09, Jason Alex <amr.ccie@gmail.com> wrote:
>
> Dear All,
> the task says to convert the legacy QOS into MQC on R5 ethernet
> interface
>
> the Legacy QOS is below
>
> interface e0/1
> custom-queue-list 1
>
> queue-limit protocol ip 1 tcp www
> queue-limit protocol ip 2 tcp ftp
> queue-limit protocol ip 2 tcp ftp-data
> queue-limit protocol ip 3 tcp telnet
> queue-limit 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
>
> the solution says that
>
>
>
> policy-map QOS
> class HTTP
> bandwidth percent 50
> queue-limit 30
> class FTP
> bandwidth percent 30
> class TELNET
> bandwidth percent 5
>
> policy-map PARENT
> class class-default
> shape average percent 100
> service-policy QOS
>
> !
>
> interface Ethernet0/0.52
> service-policy output PARENT
> I don't know how the bandwidth percent 50 for the HTTP traffic cames from
>
> Please advice
>
> Regards
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:04 ART