From: Truman, Michelle, BNSVC (mtruman@xxxxxxx)
Date: Tue Feb 22 2000 - 14:49:12 GMT-3
Yes, it's called CAR or Committed Access Rate and the benefit is that it
takes advantage of the CEF algorithms for caching and forwarding so
processing of the rate limits does not bring the processor to it's knees.
Here's a link:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios111/cc111/car.pd
f
<http://www.cisco.com/univercd/cc/td/doc/product/software/ios111/cc111/car.p
df>
There are many ways you can shape the traffic, including bandwidth by
protocol, source address, destination, etc as well as precedence. Uses
access lists for policy matching.
p.s. there are better links, but I didn't have time to look them up
p.s.s. This is how many ISP's responded assisted customers who were being
DDOS'ed during the web hacks week before last, by rate limiting ICMP and SYN
response.
Michelle Truman, CCNP
Internet Technologies Consultant-AT&T
mtruman@att.com
w 612-376-5137 vo 651-917-8104
-----Original Message-----
From: Richard Wagner [mailto:Richard.Wagner@mitchell.com]
Sent: Tuesday, February 22, 2000 10:37 AM
To: 'ccielab@groupstudy.com'
Subject: Queuing and other options like it
If I wanted to limit the traffic rate of a certain protocol, say FTP on a
link. I could easily use custom queuing.
I would create two queues for it... the FTP and the default queue. The
"amount of bytes serviced" by each queue would then be set to the same
proportion that I want to limit FTP traffic.
Using an easy 1024k link speed... if I wanted 25% max FTP traffic, my queues
would be "ftp=256k" and "default=768k".
Someone explained that this is the "old way" and that there is simpler way
to accomplish this, where you make the same access list, but apply a command
to the interface where "traffic matching this list is limited to a certain
bandwidth".
Is anyone aware of this better/newer/simpler method?
Thanks!
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:22:54 GMT-3