From: Ken Bartlinski (kenbar3@gmail.com)
Date: Sat Jun 25 2005 - 11:42:54 GMT-3
To meet the requirements of this task I would look at custom queueing using
three queues. My configs would look something like this.
Queue-list 1 protocol ip 1 tcp ftp
Queue-list 1 protocol ip 1 tcp ftp-data
Queue-list 1 protocol ip 2
Queue-list 1 default 3
Queue-list 1 queue 1 byte-count 1000
Queue-list 1 queue 2 byte-count 4000
Queue-list 1 queue 3 byte-count 5000
Then apply it to the appropriate interface - Or am I wrong and can say
goodbye to approximately 3 points.
HTH
Ken
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Zouta oxpf
Sent: Saturday, June 25, 2005 8:54 AM
To: cisco ccie
Cc: ccielab@groupstudy.com
Subject: Re: qos
This configuration does not contain an acl for ip, but a class for the
remaining ip traffic is created.
class-map match-all FTP
match protocol ftp
!
class-map match-all REMAINING_IP
match not protocol ftp
match protocol ip
!
policy-map QOS
class FTP
bandwidth percent 10
class REMAINING_IP
bandwidth percent 40
!
HTH
ZO
On 6/25/05, cisco ccie <ccieman@hotmail.com> wrote:
> Hi group...
>
>
> I have a question about qos that I do not know how to do. It goes like
this
> :
>
> Classify ftp traffic and assign it 10% of bandwidth.
>
> Remaining IP traffic should have 40% of bandwidth
>
> Do not create class or use access-list for the IP traffic
>
>
> ccieman
>
> _________________________________________________________________
> MSN Hotmail http://www.hotmail.no Send e-post fra der du er
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:44 GMT-3