Re: CAR configuration parameters - IE-LAB17 posted 07/26/2007
- Subject: Re: CAR configuration parameters - IE-LAB17
- From: Ryan <ryan95842@xxxxxxxxx>
- Date: Thu, 26 Jul 2007 16:17:15 -1000
- Cc: "Cisco certification" <ccielab@xxxxxxxxxxxxxx>
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=d9d7oy353udoCAPGvoaGAlU25A3ruVrQfoIwlhCM6KQYPd2p4P788PMAvtpheRzFhqW5+UuyYpFsA9V6SHRDnMie99zQHWPUBinHXJw+u09P6bus6SpGeD/ow/aI9VlmTwrXPbELX63ctqE7IgJWudQ2xWQ9pIINpbS4t2tHYCI=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=WFyw/fB1J+e+fgxXgDBXLegHyokJ/jerneW9fKtMAHUqDc+X8UqzUY/8n85yK1bshEE6Tizu58fetTxyWm1kc8rSa5H4GPGt4s7XUiVZeOYqhoaRfAu5IUXo90FXNJ7vcBwuXxMUeK+Xdauw5lV1/XCIE39EKSQcGw7jsp4aN3o=
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com>
I know this doesn't answer your question, but from command reference, there
is a formula for configuring the normal and extend burst. I've found in
"real life" it to be true. Using the 'default' bytes for normal and extended
burst like the solution shows will seriously degrade the performance and it
will police at a much lower rate. Using the formula though works well. Since
this is the lab, I guess it doesn't matter.
I have no idea how they got 496000 either...based on the question and the
formula, I would have put in:
int e 1/0
rate-limit output access-group 191 500000 93750 187500 conform-action
transmit exceed-action drop
Use this command to configure your CAR policy on an interface. To specify
multiple policies, enter this command once for each policy.
CAR and DCAR can be configured on an interface or subinterface.
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 = configured rate * (1 byte)/(8 bits) * 1.5 seconds
extended burst = 2 * normal burst
With the listed choices for parameters, extensive test results have shown
CAR to achieve the configured rate. If the burst values are too low, then
the achieved rate is often much lower than the configured rate.
On 7/26/07, Alan Ewer <acewer64@xxxxxxxxx> wrote:
> Hi All
> apologies for asking this here if it has already been answered elsewhere (
> didnt find it if it has .)
> I am struggling with CAR. Question reads like this... Configure CAR on an
> interface to not exceed 500kbps outbound..
> cool i think to myself !!
> The command syntax is :
> rate-limit input|output access-group <name> <sustained-rate in bps>
> burst BYTES> <excess burst BYTES> conform-action transmit exceed-action
> OK this is applied to an ethernet interface on a 3640 and has nothing to
> with time-intervals <true/false ???>
> the answer in the workbook is
> int e 1/0
> rate-limit out put access-group 191 496000 4000 4000 conform-action
> transmit exceed-action drop
> Question 1 How does the 496000 get derived
> Question 2 what and where does 4000 bytes normal burst get derived.. what
> are the considering factors here ??
> Question 3 what difference does the excess burst have if the exceed-action
> is "drop" ..... i
> If anyone could point me in the right direction.. i would me grateful...
> I have already read the QOS guide and the configuration guide and they
> seem to be helping me with this concept !
> I dont get how 496000 bits per second + 4000 bytes per second = 500000
> per second
> Brisbane Oztralia
> Subscription information may be found at: