Hi Yogesh The allowed traffic is CIR = bc/T. Why are they again adding another CIR?
(token bucket capacity in bits / time interval in seconds) + established rate in bps = maximum flow speed in bps is nothing but CIR + CIR = maximum flow speed in bps With regards Kings On Fri, Aug 20, 2010 at 6:32 PM, Yogesh Gawankar <[email protected]>wrote: > > HI Kingsley > > You are clear on this . What comments you need now ?:) > > > Thanks and regards > > Yogesh Gawankar > > --- On *Fri, 8/20/10, Kingsley Charles <[email protected]>*wrote: > > > From: Kingsley Charles <[email protected]> > Subject: [OSL | CCIE_Security] shaping > To: [email protected] > Date: Friday, August 20, 2010, 10:19 PM > > > Hi all > > Snippet from > > > http://www.cisco.com/en/US/docs/security/asa/asa80/configuration/guide/qos.html > > For traffic shaping, a token bucket permits burstiness but bounds it. It > guarantees that the burstiness is bounded so that the flow will never send > faster than the token bucket capacity, divided by the time interval, plus > the established rate at which tokens are placed in the token bucket. See the > following formula: > > (token bucket capacity in bits / time interval in seconds) + established > rate in bps = maximum flow speed in bps > > > Established rate i.e., the number of tokens placed in tokens is CIR. > > > token bucket capacity in bits / time interval in seconds is also CIR which > Bc/T > > > I am clear on this. Can someone please comment. > > > With regards > > Kings > > > -----Inline Attachment Follows----- > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
