[c-nsp] Limiting incoming rate on Catalyst6509

Anton Yurchenko phila at cascopoint.com
Fri Jun 17 13:12:36 EDT 2005


Joe Shen wrote:

>Hi,
>
>I'm trying to  limit incoming bit rate on GE ofCatalyst6509. What I want to achive is to limitincoming bit rate to 300Mbps while permitting 350Mbpsburst rate.  I do the following configuration onCatalyst6509:
>mls qos
>mls qos aggregate-policer 300M-test 300000000 150000150000 conform-action transmit exceed-action drop
>access-list 101 permit ip any any
>class-map match-all 300M-test  match access-group 101  policy-map 300M-test   # this is for ingress trafficpolicing  class 300M-test 
>

>   police aggregate shidao
>  
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ you are using an
aggregate policer "shidao" instead of named aggregate policer
"300m-test" you`ve defined above.

if you are trying to limit traffic just from one port, you can also
rewrite the policy-map config as:
--------------------------------------
policy-map 300m-test
class 300m-test
police 300M-test 300000000 150000 150000 conform-action transmit
exceed-action drop
--------------------------------------
this may be more appropriate because if you apply the policy that uses a
named aggregate-policer on 2 or more ports it`ll apply to combined
traffic from those ports ( on a per PFC/DFC bases).

>After applying above policy to one of GE interface, Inoticed the incoming rate could be 400Mbps. Is thereany parameter misconfigured? 
>thanks in advance 
>Joe
>__________________________________________________赶快注册雅虎超大容量免费邮箱?http://cn.mail.yahoo.com_______________________________________________cisco-nsp mailing list  cisco-nsp at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-nsparchive at http://puck.nether.net/pipermail/cisco-nsp/
>
>  
>


More information about the cisco-nsp mailing list