RE: WRED

From: Solomon Ghebremariam (sghebrem@cisco.com)
Date: Sun Jan 12 2003 - 17:08:57 GMT-3


 Scott
        So this means using class to match the traffic of interest and
applying the WRED parameters won't work?

Ex.
        Class-map WRED_TELNET

                match ip address 142

        access-list 142 permit tcp any any eq telnet

        Policy-map DROP_TELNET
                class WRED_TELNET
                bandwidth 2048
                random-detect flow

                random-detect flow average-depth-factor 20
                random-detect flow count 40

and applying service policy DROP_TELNET to the interface??? or I am off
base here?
What is the best way of applying WRED to a specific traffic type?

solomon

At 11:15 AM 1/12/2003 -0500, Scott Morris wrote:

  There are a couple different ways to do it, but the bottom line is
  that
  you classify your traffic before deciding how to handle it.

  For example, set up a CBWFQ and one queue deals with telnet traffic.
  Within this queue you use random-detect with the parameters you have
  mentioned.

  Another way is to mark the traffic on ingress perhaps even with
  policy
  routing. Set a DSCP tag onto the traffic. Then use random-detect
  dscp
  with the values you have listed on the egress point.

  AFAIK, there isn't an ACL parameter on any of the random-detect
  command
  lines.

  Enjoy!

  Scott

  -----Original Message-----
  From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
  Of
  pita40
  Sent: Sunday, January 12, 2003 10:11 AM
  To: ccielab@groupstudy.com
  Subject: WRED

  I am trying to configure WRED. I can configure WRED based on
  precedence
  but I am having difficulty finding in CCO how to configure based on
  different types of ip traffic.

  For example.

  Configure WRED so that telnet traffic will be randomly dropped if
  queue
  lenght is over 20 and completely droped if over 40

  I am having proble with specify telnet traffic in the configuration.
  Please help. .
  .
.



This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:47 GMT-3