From: marvin greenlee (marvin@ccbootcamp.com)
Date: Sat Apr 16 2005 - 23:10:11 GMT-3
That depends on your interpretation of the queue limits. With custom
queues, the default is 20. With CBWFQ, the default is 64.
If you interpret the conversion requirement to be that one queue should be
50% more than the default value (30 is 50% more than 20), you would set that
queue to 96, and leave the others at 64.
If you interpret the conversion requirement to be that the queue limits
should be set to the same value as the custom queue, the queues would be set
to 20 and 30, like the custom queue.
If you interpret the requirement such that all queues should be at the
default value, except for the one changed to 30, then you would have one
queue at 30, and the rest at 64.
When in doubt about what is being asked, make sure to ask the proctor for
clarification.
Marvin Greenlee, CCIE#12237, CCSI# 30483
Network Learning Inc
marvin@ccbootcamp.com
www.ccbootcamp.com (Cisco Training)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
DaveW
Sent: Saturday, April 16, 2005 5:03 PM
To: ccielab@groupstudy.com
Subject: Re: QOS IWEB LAB15 TASK 8.1 custome queueing to MQC
[bcc][faked-from]
Importance: Low
Interesting, I would think all queues except WWW would have a "queue-limit
20" statement in the solution. Looking at the solution posted below the
queue depth for all classes is 64. Any idea why?
DAve
----- Original Message -----
From: "mani poopal" <mani_ccie@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Saturday, April 16, 2005 2:43 PM
Subject: QOS IWEB LAB15 TASK 8.1 custome queueing to MQC
> Hi Brian and all,
>
> The question gives set of custom queueing and asks us to conver to MQC.
> =================================================
> int e 0/1
> custom-queue-list 1
>
> 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[we are taking byte count for queue
4/default as 1500]
>
> queue-list 1 protocol ip 1 tcp www
> queue-list 2 protocol ip 2 tcp ftp
> queue-list 2 protocol ip 2 tcp ftp-data
> queue-list 3 protocol ip 3 tcp telnet
> queue-list 4 default
> =================================================
> Solution in the guide:
> ip cef
> class-map TELNET
> match protocol telnet
> class-map FTP
> match protocol FTP
> class-map match-all WWW
> match protocol HTTP
>
> policy-map MIGRATION
> class WWW
> bandwidth percent 50
> queue-limit 30
> class FTP
> bandwidth percent 30
> class TELNET
> bandwidth percent 5
>
> interface eth 0/1
> max-reserve-bandwidth 85
> service-policy output MIGRATION
> ==========================
> NOW for the question, the answer given in the solution guide is right
because it changed the max reserve bandwidth to 85 and class-default takes
remaining 15 percent bandwidht.
> But What is the implication of defining bandwidth percent for class
default
>
> eg:
> class class-default<---I know this accomplishes the same thing but is
there is any difference
> bandwidth percent 15
>
> If we define a bandwidth percent for class class-default, do we have to
leave the max-reserve bandwidth as 85 or changed to max-reserve-bandwidth
100. Any help is appreciated.
>
> thanks
>
>
> Mani
>
>
> B.ENG,A+,CCNA,CCNP,CCNP-VOICE, CSS1,CNA,MCSE
> (416)431 9929
> MANI_CCIE@YAHOO.COM
>
> ---------------------------------
> Do you Yahoo!?
> Plan great trips with Yahoo! Travel: Now over 17,000 guides!
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 07:54:58 GMT-3