From: Erick Bergquist (ebergquist@ameritech.net)
Date: Fri Sep 30 2005 - 02:13:16 GMT-3
A related question on this, if you apply a
service-policy under the map-class for frame then the
FRTS parameters in the show frame-relay pvc # output
are at bottom below service policys.
If you apply service-policy to the sub interface then
this info is at top with rest with PVC info before the
stats for the service policies are displayed.
Is there a difference here in way it is working, or
just being displayed? The cisco docs say "The
service-policy is applied to the PVC indirectly by
configuring it under the map-class associated to the
PVC.".
Just checking as a colleage was asking me about the
difference.
--- "Dennis J. Hartmann" <dennisjhartmann@hotmail.com>
wrote:
> I believe what Brian is talking about here is DUAL
> FIFO. This is
> the nomenclature/syntax that will be displayed when
> viewing the physical
> interface with such mechanism applied?
>
> Can you verify this Brian? Thanks.
>
> Cheers,
>
> Dennis Hartmann
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of
> Brian McGahan
> Sent: Wednesday, September 28, 2005 4:18 PM
> To: Stefan Grey; ccielab@groupstudy.com
> Subject: RE: MQC bandwidth
>
> Stefan,
>
> Assuming you are referring to Frame Relay QoS it
> depends if you are
> doing per-VC queueing or not. By default there is
> one shared output queue
> for the interface regardless of how many VCs or
> subinterfaces you have. In
> this case QoS is applied to the main interface since
> there is only one
> output queue, and hence only one "bandwidth" value
> that is significant.
>
> With legacy and MQC based Frame Relay Traffic
> Shaping each VC is
> assigned a separate output queue that in turn
> contends for the transmit ring
> of the interface. Since there are separate output
> queues you can apply
> separate QoS attributes onto then, either at the
> main interface,
> subinterface, or VC level. In this case the
> available bandwidth for a
> particular queue is based on the "mincir" value,
> either as defined by the
> "frame-relay mincir" command in legacy FRTS or the
> "shape adaptive"
> command in the MQC. By default this value is half
> of the configured "cir"
> or "average" rate.
>
> If you have a specific practice lab task that you
> want more
> information about for QoS feel free to post it,
> otherwise check here for
> more information:
>
>
http://www.cisco.com/en/US/tech/tk543/tk544/technologies_tech_note09186a
> 00800a4754.shtml
>
> HTH,
>
> Brian McGahan, CCIE #8593
> bmcgahan@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987 x 705
> Outside US: 775-826-4344 x 705
> 24/7 Support: http://forum.internetworkexpert.com
> Live Chat: http://www.internetworkexpert.com/chat/
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf
> Of
> > Stefan Grey
> > Sent: Wednesday, September 28, 2005 11:25 AM
> > To: ccielab@groupstudy.com
> > Subject: MQC bandwidth
> >
> > Hello group,
> >
> > Question:
> >
> > "Output queue calculations for the MQC are based
> on the configured
> > bandwidth value of the interface and not the speed
> the interface is
> > clocked at.
> Be
> > sure to set the appropriate bandwidth value when
> configuring the MQC
> on an
> > interface."
> >
> > When we configure CBWFQ on the subinterface should
> we configure the
> > reference bandwidth on the subinterface itself or
> on the physical
> > interface.
> > Where does router look for reference??
> >
> >
>
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:17 GMT-3