Re: policy-map: police vs police cir

Jack,

your first command yields:

test#sh policy-map int f 0/0
  FastEthernet0/0

   Service-policy output: test

     Class-map: class-default (match-any)
       1 packets, 60 bytes
       5 minute offered rate 0000 bps, drop rate 0000 bps
       Match: any
         1 packets, 60 bytes
         5 minute rate 0 bps
       police:
           cir 1000000 bps, bc 31250 bytes
         conformed 0 packets, 0 bytes; actions:
           transmit
         exceeded 0 packets, 0 bytes; actions:
           drop
         conformed 0000 bps, exceed 0000 bps

your second:

policy-map test
   class class-default
     police 1000000 conform-action transmit exceed-action drop

test#sh policy-map int f 0/0
  FastEthernet0/0

   Service-policy output: test

     Class-map: class-default (match-any)
       12 packets, 720 bytes
       5 minute offered rate 0000 bps, drop rate 0000 bps
       Match: any
         12 packets, 720 bytes
         5 minute rate 0 bps
       police:
           cir 1000000 bps, bc 31250 bytes
         conformed 0 packets, 0 bytes; actions:
           transmit
         exceeded 0 packets, 0 bytes; actions:
           drop
         conformed 0000 bps, exceed 0000 bps

so they seem to do the same.
As long as you don't put "pir" in there, you are configuring a one
colour policer.

-Carlos

Jack Router wrote:
> Hello all,
>
> I have a question about police command. Assume that I want to police some
> traffic. Under policy-map, class I can enter:
> police 1000000 conform-action transmit exceed-action drop
> or
> police cir 1000000 conform-action transmit exceed-action drop
>
> Is there any diffrence between two commands and which should be used when ?
>
> Thanks,
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>

-- 
Carlos G Mendioroz  <tron_at_huapi.ba.ar>  LW7 EQI  Argentina
Blogs and organic groups at http://www.ccie.net