I see what oyur saying. With my referenced formula you would do 10/1000 to
get milliseconds, not .010/1000. I just use 10/1000. I could simply write
Bc=Cir(.010) like you did. I guess it's confusing. My bad. And The reason
I got 36.4 ms and you got .04 ms is cause you did it correctly and I
I was meaning that perhaps he uses Kbps instead of bps for the CIR or
milliseconds instead of seconds for the interval. According to his
formula, Bc=CIR(Tc/1000). Let's use a 256k circuit with 10ms as an
example:
Bc=256000(.010/1000) = 2.56
That doesn't quite work out.
As you can see, Tc in t
The config for the bottom of this page is correct for FRF.12
http://www.cisco.com/warp/public/788/voice-qos/voip-ov-fr-qos.html#first
Plus we're arguing about the same thing. If Tc=Bc/Cir, or Bc=CIR(Tc/1000)
and we have
Cir=256000
Tc=10ms
Bc=?
With your formula, you get 2560 and with mine you
No we all use ms, including Wendel Odom.
""John Neiberger"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Actually, that web page is correct. Tc = Bc/CIR, and the
> answer is in seconds. If you get an answer such as .125, that
> is 1/8th of a second, or 125ms.
>
> At work we
Actually, that web page is correct. Tc = Bc/CIR, and the
answer is in seconds. If you get an answer such as .125, that
is 1/8th of a second, or 125ms.
At work we use a Bc of 5120 on 512k links. 5120/512000 = .010,
or 10ms, which is the recommended interval. It all depends on
what units yo
I believe the true calculation for the interval (Tc) is Bc=CIR(Tc/1000).
This web page over-simplifies it. I have read in varoius sources
(Intergrating Voice and Data Network, and from Wendel Odom himself, that
it's actually the above calculation. I have other problem wih CCO web pages
also, esp
I only see two examples on that page that are different. The first is
on a 56k link, Bc=1000 and CIR=56000. Bc/CIR = .0178, or basically
18ms. I know that's higher than the recommended 10ms, but perhaps there
are drawbacks to lowering the Bc below 1000 that I'm not aware of.
The other example
Forgive me, you have a Tc of 36.4ms, not a serialization delay. But the
packets went out at 10ms or less, so you have 26.4 ms lest to wait before
you can build more credit. Tc should = serialization.
""Steven A. Ridder"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> The bc i
The bc info for the Frame-Relay traffic shaping info on that page is wrong.
One should always target Bc to get a Tc of 10ms, but the config examples are
more like a Bc of 36.4. So you have the serialization delay time at 36.4,
but optimally you want 10ms. The packets will be going out at 10ms (o
9 matches
Mail list logo
