[c-nsp] FR and QoS

[Rodney Dunn]

The proper way to do it is like this:

a) Do you need fragmentation based on the
   speed of the PVC?  If not, then define
   a hiearchical policy (parent to shape and
   child to do the queueing) and attach it to
   the PVC.

b) If you need fragmentation you attach a 
   map-class to the PVC and then attach 
   a similar policy as in (a) under the
   map-class.  They only reason you have to
   add the map-class is to configure the fragment
   size and nothing else.

I wish we would make it so you could just configure
the fragment size under the policy for the shaping
to elminate the extra step for (b).

I'm going to ask why we don't have a more clear
document on CCO for this exact example.

Rodney

On Thu, Dec 09, 2004 at 09:36:26AM -0000, Tim Franklin wrote:
> cisco-nsp-bounces at puck.nether.net wrote:
> 
> > Now, I think service policies will not work on interfaces that have FR
> > sub-interfaces configured. I dont exactly remember the reason, but I
> > think for FR one needs to use FRTS for QoS.
> 
> You can nest a service policy inside the FRTS; just add the 'service-policy'
> line to the map-class along with the usual cir, bc et al.  You can only
> queue with it though, not shape, similar to attaching a service policy to a
> PVC rather than an ATM sub-interface.
> 
> In theory you can instead attach a service policy to the sub-interface that
> both shapes and queues.  I've had this working, but I've also had it failing
> quite miserably, and failing silently (which is *far* more annoying).  On my
> to-do list to nail it down to which combinations of chassis, line-card, IOS
> and sacrificial chickens actually work :(
> 
> Regards,
> Tim.
> 
> --
> ____________   Tim Franklin                 e: tim at colt.net
> \C/\O/\L/\T/   Product Engineering Manager  w: www.colt.net
>  V  V  V  V    Managed Data Services        t: +44 20 7863 5714
>                                             f: +44 20 7863 5876
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/