From: Masood Malik (malikm24@xxxxxxxxxxx)
Date: Sun Dec 24 2000 - 18:28:09 GMT-3
Michael,
Further to my earlier mail. In your scenario, when there is congestion in
the network any packet set with Discard eligible bit will be dicarded
immediately and a becn will be send to sending site. This will throttle the
link down to mincir. ie. the sending side will reduce the speed. Thus in
your case as soon as congestion occurs in the network, your devices will
send at mincir rates.
Masood
----- Original Message -----
From: "Masood Malik" <malikm24@hotmail.com>
To: "Michael King" <kingmi1@yahoo.com>
Sent: Monday, December 25, 2000 6:50 AM
Subject: Re: frame relay traffic shaping
> Michael,
>
> You should use the following config.
>
> interface Serial0
> no ip address
> encapsulation frame-relay
> frame-relay traffic-shaping
> frame-relay class yu
>
> map-class frame-relay yu
> frame-relay adaptive-shaping becn
> frame-relay cir 64000
> frame-relay bc 8000
> frame-relay be 16000
> frame-relay mincir 16000
>
> This will make sure the rate throttles back to 16K in case of BECN.
>
> For discard eligible bit setting above 48K use the following config. I am
> assuming your are using Ip only. If other protocols are use build the
> relivant de-list in global config and apply it to the interface config.
>
>
> frame-relay de-list 3 protocol ip gt 750
> int s 0
> frame-relay de-group 3 170
>
> note: replace 170 in the above statement with the interface DLCI.
>
> This is how it works. You want to dicard any packet above 48kbps. and your
> tc is .125s i.e 1/8th sec. Thus in one Tc you will send 48000/8 = 6000
> bits.= 750 bytes. Thus any packet larger than 750 bytes should be discard
> eligible (de). Hence the above configuration.
>
> I hope this helps.
>
> regards
> Masood
>
>
>
> ----- Original Message -----
> From: "Michael King" <kingmi1@yahoo.com>
> To: <malikm24@hotmail.com>
> Sent: Sunday, December 24, 2000 10:42 AM
> Subject: frame relay traffic shaping
>
>
> > Masood,
> >
> > I'm having trouble with this frame relay traffic
> > shaping and you seem so have a pretty good grasp the
> > way Cisco interprets it. You wrote in a groupstudy
> > mail the following:
> >
> > map-class frame-relay yu
> > frame-relay cir 64000
> > frame-relay bc 8000
> > frame-relay be 16000
> > frame-relay mincir 48000
> >
> > The way cisco interprets these is as follows:
> > CIR is the access/physical rate in your case 64k
> > mincir is the committed information rate in your case
> > 48K
> >
> > Thus when dealing with cisco routes use the new
> > terminology viz, CIR as
> > the
> > physical rate and mincir as the term for CIR which
> > telcos and you and
> > me
> > know normally. I know it is confusing but that is the
> > reality.
> >
> > for explination of bc and be look at the following
> > url, I have used bc
> > as
> > 1/8th of access rate and be double that of bc which is
> > the default
> > values
> > cisco routers use.
> >
> > http://www.cisco.com/warp/public/125/21.shtml
> >
> > regards
> > Masood Malik
> >
> > My scenario is this:
> >
> > My interval is .125s. Packets will be discard eligible
> > over 48k and discarded over 64k. I should throttle my
> > transmission rate down to 16k if I receive a BECN
> > response. Is the above config that you suggested the
> > appropriate config for my scenario? If so, does the
> > rate coming down to 16k not affect anything? Please
> > help!!!
> >
> > Mike
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:10 GMT-3