Re: Policing - what happens to violate packets?

From: Petr Lapukhov (petr@internetworkexpert.com)
Date: Mon Jun 26 2006 - 08:43:12 ART

Hmm, since no *violate* action has been defined, Be value is NOT used
actually. All your traffic that exceeds Bc falls under exceed action.

This behavior is unlike CAR, where you "exceed" action is somewhat
"random", to simulate RED behavior, and depends on Be-Bc "margin".

HTH 

-- 
Petr Lapukhov, CCIE #16379
petr@internetworkexpert.com

Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Outside US: 775-826-4344

2006/6/26, allboutcisco <frenzeus@streamyx.com>:
>
> Hi Group,
>
> Looking at the config below:
>
> Rack1R2#sh run | b policy-map
> policy-map QOS_IN
>    class UDP
>    police cir 128000 bc 2000 be 2000
>      conform-action transmit
>      exceed-action set-prec-transmit 0
>   class TCP
>    police cir 256000 bc 4000 be 8000
>      conform-action transmit
>      exceed-action set-prec-transmit 0
>
> Taking class UDP as an example, policing rate for UDP is 128000bps, with a
> Bc bucket depth of 2000 bytes & a Be bucket depth of 2000 bytes as well. A
> bunch of packets arrive, assuming Bc bucket tokens are all used up to
> transmit & excess packets used up all of Be bucket tokens as well where the
> excess action is to set prec to 0 then transmit. Now assuming that there are
> still packets & since no action has been defined for violate - what happens
> to those packets?
>
> Appreciate if someone could advise on this?
>
> Thanks.
>
> Cheers,
> K
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

This archive was generated by hypermail 2.1.4 : Sat Jul 01 2006 - 07:57:33 ART