From: Jason Madsen (madsen.jason@gmail.com)
Date: Tue Nov 25 2008 - 23:02:15 ARST
Hi Mark,
You don't have to explicitly specify the TC value...it's done implicitly
when you specify your CIR and BC values. The values you listed render a TC
of 31ms as can be seen via "show traffic-shape f0/0". If you want to alter
your TC value, do it by manipulating your BC value. As you stated, if you
want a TC of .125 (125 ms) then define your BC value as 32000 since it is
1/8th of 256000.
QoS is my weakest area, but from what I understand your BC is a TC of your
CIR (your CIR rate during a specified time interval). BE, if specified,
allows you to burst above that rate up to your line Access Rate. Since you
used 8000 for both your BC and BE, you are disallowing excess bursting above
your committed rate.
With Traffic Shaping, any traffic with a rate up to your BC will be
transmitted normally; any traffic with a rate over your BC, but still under
your BE will be transmitted normally unless congestion occurs and then
queuing will take place. If your queue / buffer fills tail drop will
occur. Any traffic exceeding your BE rate will also be tail dropped.
Hope that helps and I hope I was accurate in my explanations.
Jason
On Tue, Nov 25, 2008 at 5:45 PM, Mark Stephanus Chandra <
mark.chandra@gmail.com> wrote:
> Hi Guys,
>
>
>
> I want to ask about traffic shaping in Interface.
>
>
>
> Like this example
>
>
>
> int fa0/0
>
> traffic-shape 256000 8000 8000
>
>
>
> Is there any TC to calculate like frame-relay in this scenario ?
>
>
>
> Cause if we calculate with 125ms TC, the bc should be 32000.
>
>
>
> So How this packet treat if this traffic shape applied on ethernet
> interafce
> ?
>
>
>
> Thanks guys
>
>
>
>
>
> Regards
>
>
>
> Mark Stephanus Chandra
> IT Consultant
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:32 ARST