From: Hobbs (deadheadblues@gmail.com)
Date: Wed Jan 07 2009 - 21:32:30 ARST
Yeah I agree with that for sure. I would pick #2 but I have seen real
implementations (previous job) where cir was guaranteed through the use of
the mincir command and the cir was at access rate because the SP was
allowing them to burst.
On 1/7/09, Scott Morris <smorris@internetworkexpert.com> wrote:
>
> IMHO the "conforming to CIR of 1024k" doesn't leave much to the
> imagination.
> Your shaping to 1.536M doesn't do that. It conforms to a cir of 1536k.
>
> So while both may give the same maximum possible throughput, they both
> behave differently in terms of time interval and in terms of the verbage of
> the question.
>
> HTH,
>
>
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Hobbs
>
> Sent: Wednesday, January 07, 2009 6:15 PM
> To: Tyson Scott
> Cc: Cisco certification
> Subject: Re: FRTS Frame-relay traffic shaping - Burst to Access Rate
>
> Thanks Tyson. I do notice the Tc and Bc values are different, but I was
> just
> wondering about the more general goal of "Conforming to the CIR of 1024k
> and
> allowing burst up to access rate."
>
> What I am getting at is that you have either have congestion or you don't.
> If you don't both options give 1536k, if you do both options give you
> 1024k...right?
>
> I would most likely choose #2 but I was wondering about option 1 because it
> seems to act the same.
>
> On 1/7/09, Tyson Scott <tscott@ipexpert.com> wrote:
> >
> > Hobbs,
> >
> > Here I will quickly show the output of applying each to a router
> >
> > R7(config-fr-dlci)#do sh traffic-sh
> >
> > Interface Se0/0/0
> > Access Target Byte Sustain Excess Interval Increment
> > Adapt
> > VC List Rate Limit bits/int bits/int (ms) (bytes)
> > Active
> > 708 1536000 6144 1536000 0 32 6144 -
> > R7(config-fr-dlci)#
> >
> > R7(config-fr-dlci)#class FRTS2
> > R7(config-fr-dlci)#do sh traffic-sh
> >
> > Interface Se0/0/0
> > Access Target Byte Sustain Excess Interval Increment
> > Adapt
> > VC List Rate Limit bits/int bits/int (ms) (bytes)
> > Active
> > 708 1024000 1920 10240 5120 10 1280 -
> > R7(config-fr-dlci)#
> >
> > This should answer your question if they are different.
> >
> > But if you want the CIR to adjust to MINCIR you also need to apply some
> > type
> > of adaptive shaping otherwise it will not change. Typically you will use
> > frame-relay adaptive-shaping becn.
> >
> > Regards,
> >
> > Tyson Scott - CCIE #13513 R&S and Security
> > Technical Instructor - IPexpert, Inc.
> >
> > Telephone: +1.810.326.1444
> > Cell: +1.248.504.7309
> > Fax: +1.810.454.0130
> > Mailto: tscott@ipexpert.com
> >
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> > Hobbs
> > Sent: Wednesday, January 07, 2009 4:23 PM
> > To: Cisco certification
> > Subject: FRTS Frame-relay traffic shaping - Burst to Access Rate
> >
> > Hello,
> >
> > Suppose you had a T1 frame-relay link with 1024k CIR. You need to
> configure
> > FRTS to conform to this, while allowing burst up to the access rate. Are
> > the
> > options below both accomplishing the task? As I understand, default
> mincir
> > is half of cir so we need that argument in any case. My real question
> > centers around the use of cir command.
> >
> > 1)
> > map-class frame-relay FRTS
> > frame-relay cir 1536000
> > frame-relay mincir 1024000
> >
> > 2)
> > map-class frame-relay FRTS
> > frame-relay cir 1024000
> > frame-relay mincir 1024000
> > frame-relay bc 10240
> > frame-relay be 5120
> >
> > thank you,
> >
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:43:37 ARST