From: Daniel Ginsburg (dginsburg@gmail.com)
Date: Sun Sep 05 2004 - 14:35:23 GMT-3
On Sun, 5 Sep 2004 12:21:02 -0400, Scott Morris <swm@emanon.com> wrote:
> Thanks. :)
>
> Sorry for the wording... It's a restriction with the WFQ engine (coding
> problem?)... You are allowed to apply a policy (see the example I did on my
> router there) that has traffic-shaping listed, but you are not allowed to
> apply a policy that has queuing specifics to a subinterface.
>
> My guess is that the way that part of IOS is coded implies an overall
> control of software queuing mechanisms from the main physical interface,
> although logically that makes little difference. It's just one of those
> things.
>
I think this is because subinterfaces have no separate queues, so
queueing policy on a subinterface simply doesn't make sense. However
traffic shaping invents a queue - traffic shaping delays excess
traffic in a buffer and you can put some traffic in this buffer ahead
of other.
> With FRTS, you are doing independent shaping on each PVC, but you can CALL
> queuing mechanisms like priority or CBWFQ as well. Which furthers the "why
> not" question posed earlier. :)
>
> But if you are simply looking to deploy CBWFQ without using FRTS or a
> map-class, then you have to do it via a hierarchical policy deployment.
>
-- dg
This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:37 GMT-3