From: Athaide, Dwayne (DAthaide@epco.com)
Date: Fri May 30 2008 - 10:33:27 ART
So then why can't the CIR be 256K and if there is congestion then it drops to the MINCIR of 64Kbps.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Leo Leung
Sent: Wednesday, May 28, 2008 1:17 PM
To: akyccie
Cc: Cisco certification
Subject: Re: frame relay shaping
this is a typical scenario where cir=mincir (by default mincir = 1/2
cir). AR 256k may be cir only when there's no congestion, but the
question clearly points "Make sure your throughput changes accordingly
based upon BECN's received". This means cir will become 64k when
congestion occurs. and BE is needed to utilize maximal throughput:
cir = 64000
bc = TC*cir = 125ms * 64000 = 8000
bc+be = TC*AR = 125ms * 256000 = 32000
be = 32000 - 8000 = 24000
map-class frame-relay SHAPE
frame-relay cir 64000
frame-relay mincir 64000
frame-relay bc 8000
frame-relay be 24000
frame-relay adaptive-shaping becn
!
int s1/0
frame-relay traffic-shaping
frame-relay class SHAPE
thanks,
Leo
On 5/27/08, akyccie <akyccie@gmail.com> wrote:
> Question regd the frame relay shaping.
> Maximum throughout given is 256kbps. During congestion your provider will mark
> any traffic in excess of 64kbps as discard eligible. Make sure your through
> put changes accordingly based upon BECN's received. Token bucket interval is
> 125ms.
>
> Is it the right answer
>
> map-class frame-relay SHAPE
> frame-relay cir 256000
> frame-relay mincir 64000
> frame-relay bc 32000 (Bc = Tc * cir --> 0.125 * 256000 )
> frame-relay be 4000 (air - cir * Tc / 8 Bytes --> 256000 * 0.125 / 8)
> frame-relay adaptive-shaping becn
> !
> int s1/0
> frame-relay traffic-shaping
> frame-relay class SHAPE
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2008 - 06:59:18 ART