Re: Random Detect

From: Peng Zheng (zpnist@yahoo.com)
Date: Tue Sep 17 2002 - 23:49:04 GMT-3


I mean compare to Kris's solution. (attached)

--- Nick Shah <nshah@connect.com.au> wrote:
> Peng
>
> just random-detect in interface configuration mode,
> ENABLES WRED.
> random-detect with precedence and other parameters
> change the default
> parameters.
>
> The default parameters are : The weight factor is 9.
> For all precedences,
> the mark probability denominator is 10, and maximum
> threshold is based on
> the output buffering capacity and the transmission
> speed for the interface.
>
> So if the question states that you jsut have to
> enable/use WRED, then
> 'random-detect' will suffice.
> If the question states changing the default values
> or specific precedence
> values, then you have to use both.
>
> rgds
> Nick
> ----- Original Message -----
> From: "Peng Zheng" <zpnist@yahoo.com>
> To: "Kris Keen" <kkeen@bigpond.net.au>
> Cc: <ccielab@groupstudy.com>
> Sent: Wednesday, September 18, 2002 11:53 AM
> Subject: Re: Random Detect
>
>
> > I received another solution:
> >
> > 1. enable random detect
> >
> > random-detect
> >
> > 2. random-detect precedence p min-threshold
> > max-threshold
> > mark-prob-denominator
> >
> > random-detect prededence X 40
> > 100
> > 40
> >
> >
> > Which one is correct?
> >
> >
> > --- Kris Keen <kkeen@bigpond.net.au> wrote:
> > > Peng,
> > >
> > > The comands you want are:
> > >
> > > random-detect dscp (if you are using dscp) <dscp
> > > value> <min thres> <max
> > > thres> <drop rate>
> > >
> > > I believe this can be done with precedeance,
> you'd
> > > need to match the source
> > > ranges with an access list and define a policy
> map
> > > tied to a class which
> > > will define your drop rates.
> > >
> > > drop rate will be the number it will drop once
> your
> > > thresholds are exceeded
> > > for instance, drop 20 is drop 1 out of 20
> packets.
> > > The lower the value the
> > > more aggresive the drops are
> > > You can set also under the class a queue-limit,
> this
> > > will define your queue
> > > size.
> > >
> > > I do some work with DSCP but never Precedance,
> so I
> > > guess this email is at
> > > least pointing you in the right direction.
> > >
> > > here is a sample of a class we have defined for
> data
> > >
> > >
> > > class DSCP-OUT-Data2
> > > bandwidth percent 33
> > > random-detect dscp-based
> > > random-detect exponential-weighting-constant 6
> > > random-detect dscp 18 15 28 15
> > > random-detect dscp 20 1 13 3
> > > queue-limit 200
> > > fair-queue
> > >
> > >
> > > As you can see, DSCP 20 which was set and
> matched
> > > with an access list has a
> > > more aggressive drop rate with smaller queue
> sizes
> > > (0 to 1 packet, 1 to 13
> > > packets and then when exceeded drop 1 in 3
> packets.
> > > DSCP 18 is less
> > > aggresive.
> > >
> > > Hope that helps
> > > Kris
> > > ----- Original Message -----
> > > From: "Peng Zheng" <zpnist@yahoo.com>
> > > To: <ccielab@groupstudy.com>
> > > Sent: Wednesday, September 18, 2002 8:36 AM
> > > Subject: Random Detect
> > >
> > >
> > > > Hi,
> > > >
> > > > Asked to configure:
> > > >
> > > > Wred under some interface.
> > > >
> > > > requirement:
> > > >
> > > > 1) for specific precedence, for example,
> critical,
> > > > specify drop 1 out of 40
> > > >
> > > > 2) minimum queue 40, maximum queue 100
> > > >
> > > >
> > > > Thanks for help.
> > > >
> > > >
> > > > Best Wishes,
> > > > Peng Zheng
> > > >
> > > >
> __________________________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! News - Today's headlines
> > > > http://news.yahoo.com
> > >
> >
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! News - Today's headlines
> > http://news.yahoo.com
> >
>



This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:55 GMT-3