Michael The command refs and config guides have some good pointers for this. Below is an example:
http://www.cisco.com/en/US/docs/ios/qos/command/reference/qos_q1.html#wp1054922 *Policing Traffic with CAR * *CAR embodies a rate-limiting feature for policing traffic. When policing traffic with CAR, Cisco recommends the following values for the normal and extended burst parameters: * *normal burst (in bytes) = configured rate (in bits per second) * (1 byte)/(8 bits) * 1.5 seconds * *17.000.000 * (1 byte)/(8 bits) * 1.5 seconds = 3.187.500 bytes * *extended burst = 2 * normal burst * *2 * 3.187.500 = 6.375.000 bytes * Stu On Wed, Jan 6, 2010 at 7:40 AM, Michael Davis <[email protected]>wrote: > Hi everyone – I have 2 questions about the legacy rate-limit command. > > 1. How do we correctly calculate what the correct normal burst and > maximum (excess) burst setting should be? > > 2. I know you should always apply the rate-limit or QOS service > policies to a physical interface, but I saw an ISP engineer apply the > rate-limit command to a dialer (pppoe) interface today. Is this a > recommended practice? > > Thanks > > Michael > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- Regards, Stuart Hare CCIE #25616 (Security), CCSP, Microsoft MCP Sr. Support Engineer – IPexpert, Inc. URL: http://www.IPexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
