From: Alexei Monastyrnyi (alexeim@orcsoftware.com)
Date: Thu Nov 23 2006 - 10:40:34 ART
Sounds right to me....
Is the anyone who can shed some light on normal burst value?
I remember reading that this is what we can allow above police rate,
but can't find a source that easy.
A.
Salman Abbas wrote:
> Hi Alexei,
>
> Thanks for the reply. Just to confirm whether I've correctly
> understood u or not, Lets say the question says: maximum is 256kbps
> and normal is 64Kbps, would that mean that I'll do
>
> Normal bytes = 256k - 64k = 192k => to bytes 24000, so the police
> command would be
>
> police 64000 24000 exceed action drop
>
> Regards,
>
> Salman
>
>
> On 11/23/06, *Alexei Monastyrnyi* <alexeim@orcsoftware.com
> <mailto:alexeim@orcsoftware.com>> wrote:
>
> Hi.
>
> If I understand it right from DocCD, normal burst is what you have
> above
> the police rate. 256k-128k=128k => to bytes 16000/ If it should be
> considered together with police rate, then just 256k=>32000 bytes. In
> either case police rate should be 128000, not 256000 IMO.
>
> I would go for
> police 128000 16000 exceed action drop
>
> HTH
> a.
>
> Salman Abbas wrote:
> > Hi guys,
> >
> > Pls help to answer the following question:
> >
> >
> > On SW1 int fa0/6, limit all UDP traffic by maximum 256Kbps and
> normal
> > 128Kbps to avoid congestion on your VLAN.
> >
> >
> > My solution is:
> >
> > mls qos
> > access-list 101 permit udp any any
> >
> > class-map LIMIT
> > match access-group 101
> >
> > policy-map POLICE
> > class LIMIT
> > police 256000 _____ exceed action drop
> >
> > int fa0/6
> > service-policy input POLICE
> >
> > Now the part that I dont understand is that second value in the
> police
> > command which is "Burst in bytes". How can I calculate it based
> on the
> > question above? Also, am I missing anyting else in my configuration?
> >
> >
> > Thanks in advance,
> >
> > Cheers!!!
> >
> > Salman
This archive was generated by hypermail 2.1.4 : Fri Dec 01 2006 - 08:05:48 ART