[nsp] Rate - limiting

Krzysztof Zaleski kzal at pol.pl
Fri May 21 03:40:28 EDT 2004



On Thursday, May 20, 2004 23:29:07, you wrote:

> This behavior is avoided if you use random-detect along with rate limiting.
> Here's an example that works perfectly at limiting a user to 500 Kb/s:
>
> interface FastEthernet0/0
>  no ip address
>  random-detect 
>
> interface FastEthernet0/0.22
>  encapsulation isl 22
>  ip address x.x.x.x y.y.y.y
>  ip verify unicast reverse-path
>  no ip redirects
>  no ip proxy-arp
>  rate-limit input 496000 93750 187500 conform-action transmit exceed-action drop
>  rate-limit output 496000 93750 187500 conform-action transmit exceed-action drop

I'm not sure if this will work. I think random-detect in this
situation will get FE's bandiwdth as reference and it will start
dropping packets when closing to 100Mb. While you can not apply
random-detect on subif, it is useless if you rate-limit on subif,
especialy if you have many subintterfaces with different limits.

cheers,
xal




More information about the cisco-nsp mailing list