From: maureen schaar (maureen.schaar@gmail.com)
Date: Thu Mar 29 2007 - 04:06:10 ART
I know I can manually set the Be to 0 with shape average, but the
thing that confuses me is that it is actually possible to have a Be
with shape average.
Compare the output from show policy-map int for average and peak:
AVERAGE:
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
256000/256000 8000 32000 32000 125 4000
PEAK:
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
512000/256000 8000 32000 32000 125 8000
With average I see the target rate is 256000, whereas with peak
shaping I see it can peak to 512000 (for both the cir is 256000). But
what do the excess bits with shape average mean? I don't think these
bits can actually be sent, or can they?
If I set the Be manually to 0, the output for AVERAGE changes to this:
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
256000/256000 4000 32000 0 125 4000
So what is exactly the difference between:
shape average 256000 32000 0
and shape average 256000 32000
with regards to how much traffic can be sent?
Maureen
On 3/29/07, Blastmor <alextols@gmail.com> wrote:
> Shape peak is rather useless now.
>
> The case when you can use it, for instance, is when provider allows you to
> burst but you are warned that your traffic can be dropped at any time (when
> ISP is congested) --> so you can use it when your traffic is
> "steady" for jitter and losses(FTP, SMTP and so on)
>
> HTH
>
> 2007/3/29, Gary <liguoyi8@gmail.com>:
> > I am confused by average & peak too.
> > According to DocCD, the syntax is : shape peak cir
> > By default be=bc. So the target rate is two times cir.
> > So when should we use "shape peak" and when should we use "shape average"?
> >
> >
>
>
> SY, Alexey
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:53 ART