From: Alexander Arsenyev (GU/ETL) (alexander.arsenyev@ericsson.com)
Date: Fri Jun 11 2004 - 08:55:48 GMT-3
I did not say "ingress direction", I said "ingress interface" . Or shall I again correct my post? Here it goes:
a) enable Custom Queueing in egress direction for corresponding interface for the traffic in question and WRED/FRED in egress direction on all other interfaces for return traffic
b) or if You know the traffic pattern (for example if question explicitly says that traffic between client X and server Y shall be "aggresively dropped") then enable Custom Queueing in egress direction for corresponding interface for the traffic in question and WRED/FRED in egress direction for the other interface which is used by return traffic (You shall know it from route table).
If You kept reading up to this point, congratulations!
HTH,
Cheers
Alex
-----Original Message-----
From: Richard Dumoulin [mailto:richard.dumoulin@vanco.es]
Sent: 11 June 2004 12:29
To: Alexander Arsenyev (GU/ETL); 'ccielab@groupstudy.com'
Subject: RE: Custom Queue - correction
I did not know you could enable red on the ingress direction. Is this possible ?
--Richard
-----Original Message-----
From: Alexander Arsenyev (GU/ETL) [ mailto:alexander.arsenyev@ericsson.com <mailto:alexander.arsenyev@ericsson.com> ]
Sent: viernes, 11 de junio de 2004 13:23
To: 'ccielab@groupstudy.com'
Subject: RE: Custom Queue - correction
I see a sentence is missing in my previous post, below is a corrected one:
The traffic is rarely unidirectional (multicast is one exception) so I believe either
a) enabling Custom Queueing for one interface and WRED/FRED on other interfaces (for return traffic)
b) enabling custom queueing on egress interface and enabling WRED (or FRED for UDP, depending on traffic profile) on ingress interface(s)
would suit the requirement.
HTH,
Cheers
Alex
-----Original Message-----
From: nobody@groupstudy.com [ mailto:nobody@groupstudy.com <mailto:nobody@groupstudy.com> ]On Behalf Of Alexander Arsenyev (GU/ETL)
Sent: 11 June 2004 09:56
To: 'ccielab@groupstudy.com'
Subject: RE: Custom Queue
Hello
The traffic is rarely unidirectional (multicast is one exception) so I believe enabling custom queueing on egress interface and enabling WRED (or FRED for UDP, depending on traffic profile) on ingress interface(s) would suit the requirement.
HTH,
Cheers
Alex
-----Original Message-----
From: nobody@groupstudy.com [ mailto:nobody@groupstudy.com <mailto:nobody@groupstudy.com> ]On Behalf Of Dan
Sent: 11 June 2004 05:53
To: Richard Dumoulin
Cc: Peng Zheng; Carlos G Mendioroz; ccielab@groupstudy.com
Subject: Re: Custom Queue
But red is not part of custom queue
Richard Dumoulin wrote:
> Sounds like configuring RED such that it aggressively drops packets,
>
> --RIchard
>
> -----Original Message-----
> From: Dan [ mailto:dans@danbsd.a.la <mailto:dans@danbsd.a.la> ]
> Sent: jueves, 10 de junio de 2004 22:42
> To: Peng Zheng
> Cc: Carlos G Mendioroz; ccielab@groupstudy.com
> Subject: Re: Custom Queue
>
>
> The doc says that queue 0 is unlimited.
>
>
>
> Peng Zheng wrote:
>
> >Is a queue size 0 reasonable?
> >
> >--- Carlos G Mendioroz <tron@huapi.ba.ar> wrote:
> >
> >
> >>Have a small queue ?
> >>
> >>Peng Zheng wrote:
> >>
> >>
> >>
> >>>How to make traffic dropped aggressively?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>__________________________________
> >>>Do you Yahoo!?
> >>>Friends. Fun. Try the all-new Yahoo! Messenger.
> >>> http://messenger.yahoo.com/ <http://messenger.yahoo.com/>
> >>>
> >>>
> >>>
> >>>
> >_____________________________________________________________________
> >__
> >
> >
> >>>Please help support GroupStudy by purchasing your
> >>>
> >>>
> >>study materials from:
> >>
> >>
> >>> http://shop.groupstudy.com <http://shop.groupstudy.com>
> >>>
> >>>Subscription information may be found at:
> >>> http://www.groupstudy.com/list/CCIELab.html <http://www.groupstudy.com/list/CCIELab.html>
> >>>
> >>>
> >>>
> >>--
> >>Carlos G Mendioroz <tron@huapi.ba.ar> LW7 EQI
> >>Argentina
> >>
> >>
> >>
> >>
> >_____________________________________________________________________
> >__
> >
> >
> >>Please help support GroupStudy by purchasing your
> >>study materials from:
> >> http://shop.groupstudy.com <http://shop.groupstudy.com>
> >>
> >>Subscription information may be found at:
> >> http://www.groupstudy.com/list/CCIELab.html <http://www.groupstudy.com/list/CCIELab.html>
> >>
> >>
> >
> >
> >
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >Friends. Fun. Try the all-new Yahoo! Messenger.
> > http://messenger.yahoo.com/ <http://messenger.yahoo.com/>
> >
> >_____________________________________________________________________
> >__
> >Please help support GroupStudy by purchasing your study materials from:
> > http://shop.groupstudy.com <http://shop.groupstudy.com>
> >
> >Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html <http://www.groupstudy.com/list/CCIELab.html>
>
> ______________________________________________________________________
> _
> Please help support GroupStudy by purchasing your study materials
> from: http://shop.groupstudy.com <http://shop.groupstudy.com>
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html <http://www.groupstudy.com/list/CCIELab.html>
>
>
> **********************************************************************
> Any opinions expressed in the email are those of the individual and
> not necessarily the company. This email and any files transmitted with
> it are confidential and solely for the use of the intended recipient.
> If you are not the intended recipient or the person responsible for
> delivering it to the intended recipient, be advised that you have
> received this email in error and that any dissemination, distribution,
> copying or use is strictly prohibited.
>
> If you have received this email in error, or if you are concerned with
> the content of this email please e-mail to: e-security.support@vanco.co.uk
>
> The contents of an attachment to this e-mail may contain software
> viruses which could damage your own computer system. While the sender
> has taken every reasonable precaution to minimise this risk, we cannot
> accept liability for any damage which you sustain as a result of
> software viruses. You should carry out your own virus checks before
> opening any attachments to this e-mail.
>
> **********************************************************************
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:37 GMT-3