From: OhioHondo (ohiohondo@columbus.rr.com)
Date: Sat Feb 22 2003 - 12:15:38 GMT-3
Sage
I believe the highest Tc supported by Cisco is 125 msec. Since Tc=Bc/CIR
that means that the highest Bc, with a CIR of 9600, is 1200. The excess
burst is set with Be.
The burst occurs during the first time period only. Depending on how the
question is phrased Burst can be calculated as:
1) the number of bits above Bc in the first time period. In this case burst
would be Be= 19200
2) the total number of bits transmitted in the 1st Tc time period. In this
case burst would be Be-Bc or 19200-1200=1800
My reading of the question -- I would have chosen number 1.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Sage Vadi
Sent: Friday, February 21, 2003 9:09 PM
To: ccielab@groupstudy.com
Subject: FRTS: Bc & minCIR
All,
Q) Configure your frame-relay network to have a
committed information rate of 9,600 bps and a burst
size of 19,200 bps.
So would this be correct - ?
frame-relay CIR 9600
frame-relay Bc 9600
The Bc figure is what I am concerned about. Reading
the documentation, CCO states the peak is = CIR + Be.
Therefore that would mean CIR=9600 + Be = 19200, so I
arrived @ Bc figure of 9600.
Also in the traffic-rate command it is explained that
the Be value is calculated from subracting the average
from the peak. In my case average would be 9600, minus
this from a peak of 19200 would also equal 9600.
Furthermore I have a question about minCIR - according
to CCO, "rate values greater than 2048 must be entered
with trailing zeros. For example, 2048000 and 5120000"
- what on earth does that mean? And why do you have to
do this???
Lastly if the minCIR value cannot be supported, the
call is cleared (direct quote CCO). Does this mean
that CIR by itself is not as stringent as the minCIR,
so that would mean CIR does some negotiation with the
endpoint - how does this work?
rgds,
Sage
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:29 GMT-3