Best practices for controlling inbound bandwidth per protocol
Next week our company will be turning up a full rate DS3 and I am trying to figure out what is the best method to manage (limit) how much bandwidth a protocol can potentially use. Right out of the gate I want to only allow 15Mbps (in and out) of the circuit to be used (we are currently using an NxT1 (4 - T-1's) design), so the jump in bandwidth will be significant for us. I plan to use the rest of the circuits' bandwidth as we grow.
I really would like to control the amount of ingress traffic coming into us. I'm assuming that applying my access groups to the Internet facing interface is my best bet?
I have done quite a bit of reading up on CAR and it looks as if this could work for me, but is it the best method?
Below is a down and dirty rate-limiting config that I threw together.
Re: Best practices for controlling inbound bandwidth per protoco
You didn't mention the hardware platform, assuming a router, I would suggest using a shaper over a rate limiter. If you want to shape per protocol, this could be accomplished using shapers with CBWFQ classes. Define two shapers, set for output on both the internal and external facing interfaces.
The shaper for your inbound traffic (the one on the internal facing interface), will limit bandwidth to clients, but traffic will burst higher on the DS3.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.