Re: QOS: police rate ???

From: Jack Router <pan.router_at_gmail.com>
Date: Wed, 22 Dec 2010 19:05:19 -0500

Thanks Narbik,
I did the test that you suggested on Ethernet and also on FR. In order to
let pass ping of 1500 bytes, BC must be 1514 on Ethernet but only 1503 on
Frame Relay. This is an eye opener !!!

On 22 December 2010 01:20, Narbik Kocharians <narbikk_at_gmail.com> wrote:

> Typically YES they are. But remember that when you use Class based Policing
> the layer 2 overhead is NOT considered.
>
> Try this lab and it will show you what i am talking about.
>
> R1 (F0/0) ------------------- (F0/0) R2 (F0/1)
> -------------------------------(F0/1) R3
>
> configure a class based policing with a rate of 1m and a BC value of 1500
> and apply it to R2's F0/1 outbound.
> On R1 ping R3 with a size of 1500 and a repeat count of 1, and you will see
> that the ping will fail. A common mistake that i see people make is they
> look at the policing rate and NOT the BC value. Once you test this, you will
> see that the BC is extremely important.
>
> But as far as what you were mentioning, i don't see any difference between
> the two.
>
>
> On Wed, Dec 22, 2010 at 4:00 PM, Jack Router <pan.router_at_gmail.com> wrote:
>
>> Yes, but what happens when police rate is applied on physical interface ?
>> Is
>> it the same as police cir ?
>>
>> In my lab:
>> R1----(F0/0)R2(F0/1)----R3
>>
>> On R2 there are two policy-maps to limit icmp to 1%:
>>
>> policy-map TEST0
>> class TEST0
>> police cir percent 1
>> conform-action transmit
>> exceed-action drop
>>
>> policy-map TEST1
>> class TEST1
>> police rate percent 1
>> conform-action transmit
>> exceed-action drop
>>
>> TEST0 is applied on input of F0/0
>> TEST1 is applied on input of F0/1
>>
>> Now, when I ping R3 from R1 and R1 from R3 results are excactly the same.
>> Are then "police cir percent" and "police rate percent" THE SAME ? My test
>> tells me that they behave the same way, is there a difference in the way
>> they work inside the router or even not that ?
>>
>>
>> On 21 December 2010 14:28, Deepak Ahuja <deeps.ccie_at_gmail.com> wrote:
>>
>> > Its a clear reference to COPP not General Policing
>> >
>> > HTH
>> > Deepak
>> >
>> > On Tue, Dec 21, 2010 at 6:03 PM, Jack Router <pan.router_at_gmail.com>
>> wrote:
>> > > Hello,
>> > >
>> > > What for is "police rate" ? There is very little information about
>> this
>> > > command. Even Cisco mentions it only twice in a 1100 page QOS
>> > configuration
>> > > guide 12.4:
>> > >
>> >
>> http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/12_4t/qos_12_4t_book.pdf
>> > >
>> > > According to this document:
>> > >
>> > > CISCO-CLASS-BASED-QOS-MIB was extended to manage control plane QoS
>> > policies,
>> > > and the police rate command was introduced to support traffic policing
>> on
>> > > the basis of packets per second for control plane traffic.
>> > >
>> > > Taking into consideration that "police rate" is meant to manage
>> control
>> > > plane, what it does when it is attached to physical interface (not
>> > > control-plane) ?
>> > >
>> > >
>> > > Blogs and organic groups at http://www.ccie.net
>> > >
>> > >
>> _______________________________________________________________________
>> > > Subscription information may be found at:
>> > > http://www.groupstudy.com/list/CCIELab.html
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
>> >
>> >
>> > --
>> > Regards
>> > Deepak Ahuja
>> > CCIE#19545(R&S/SP)
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> *Narbik Kocharians
> *CCSI#30832, CCIE# 12410 (R&S, SP, Security)
> www.MicronicsTraining.com <http://www.micronicstraining.com/>
> Sr. Technical Instructor
> *Ask about our FREE Lab Voucher with our Boot Camps*
> YES! We take Cisco Learning Credits!
> Training & Remote Racks available

Blogs and organic groups at http://www.ccie.net
Received on Wed Dec 22 2010 - 19:05:19 ART

This archive was generated by hypermail 2.2.0 : Sat Jan 01 2011 - 09:37:49 ART