From: Edwards, Andrew M (andrew.m.edwards@boeing.com)
Date: Wed Jul 27 2005 - 17:17:47 GMT-3
Toonsh,
The nested policy provides the capabilities for queueing traffic across
subinterfaces.
Without the nested policy, no queueing occurs on subinterfaces. I
believe IOS gives you an error if you try and apply a queuing policy to
a subinterface... But not if its nested.
That is why it is nested.
HTH,
Andy
-----Original Message-----
From: Arun Arumuganainar [mailto:aarumuga@hotmail.com]
Sent: Wednesday, July 27, 2005 9:58 AM
To: toonsh dosh; ccielab@groupstudy.com
Subject: Re: FRTS query
Cool today seems to be QoS field Day ...Too many question on Shaping. &
Policing !!!!
Let me explain .
Say you are in a central office and You and big leased line say of E1
bandwidth ( 2.04MBPS ) .You have 10 remote sites who has wan bandwidth
of 128KBPS each . In such as case you may choose to employ Nested
policies .
Some FAQs
Why Shaping is needed here ?:
Because if you don't shape at the central office then, there may be a
situation where central office may pump more than 128KBPS . This would
result in dropped packets at the remote end . So you will have to resort
to shaping .
Why Nested Shaping ?
So we got the traffic shaped via CBTS . Once the traffic is shaped we
wanted to give priority to real time traffic flowing to the remote end .
Hence u need to employ LLQ over shaped traffic .This is achieved via
nesting LLQ policy over CBTS.
Note : This is a typical case study of Nested Policy .Great that you got
it !!!!
Thanks and Regards
Arun
----- Original Message -----
From: "toonsh dosh" <toonsh@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Wednesday, July 27, 2005 8:18 PM
Subject: FRTS query
> Hi
>
> I have a question with this sample configuration below take from
> MQC-Based Frame-Relay configuration doc:
>
>
> class-map voice
>
> match ip dscp ef
>
> policy-map llq
>
> class voice
>
> priority 32
>
> policy-map shape
>
> class class-default
>
> shape average 64000
>
> shape adaptive 32000
>
> service-policy llq <----------------------------------
Why do
> they nest this LLQ policy
>
>
>
> interface serial0/0
>
> encapsulation frame-relay
>
> interface serial0/0.1 point-to-point
>
> ip address 192.168.1.1 255.255.255.0
>
> frame-relay interface-dlci 100
>
> class shape
>
>
> Why is it that they create a LLQ policy and then nest it under the
> default class. What would have been the difference if the did it in
> the following
> manner:
>
> policy-map shape
> class llq
> priority 32
>
> class class-default
>
> shape average 64000
>
> shape adaptive 32000
>
>
> So have two seperate classes under the "policy-map shape".
>
> Thanks
>
> _________________________________________________________________
> We've overhauled MSN Search Toolbar - FREE download!
> http://toolbar.msn.co.za?DI=1054&XAPID=2083
>
> ______________________________________________________________________
> _
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:31 GMT-3