RE: WRED in MQC

From: Gajewski Mariusz - TP POLPAK (Mariusz.Gajewski@telekomunikacja.pl)
Date: Mon Aug 22 2005 - 07:17:35 GMT-3


Or.. do some nesting policy

class-map match-all CLASS_80
  match access-group name TCP_80
!
!
policy-map www_wred
  class class-default
   fair-queue
   random-detect
   random-detect precedence 5 60 90 5
policy-map www
  class CLASS_80
   service-policy www_wred
  class class-default

But this requires shaping.

Cheers,

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Thomwin Chen
Sent: Monday, August 22, 2005 12:07 PM
To: Quetta Walla; ccielab@groupstudy.com
Subject: Re: WRED in MQC

Walla,
 
you can use match not on your CLASS_80
 
class-map match-all CLASS_80
match not access-group name TCP_80
 
so, the default class will have your TCP_80 match criteria.
 
Rgds,
Thomwin

Quetta Walla <quetta_1@lycos.com> wrote:
In a scenario where I have to match an access-list

ip access-list extended TCP_80
permit tcp any eq 80 any

and apply wred to it

class-map match-all CLASS_80
match access-group name TCP_80
!
policy-map WWW_POLICY
class CLASS_80
random-detect
random-detect 5 60 90 5

class class-default
fair-queue

The above config does not work. The router will complain (saying the class
should have bandwidth configured) when I try to enter random-detect command
under class CLASS_7070 inside policy-map UDP_POLICY.

Here the catch is to configure wred inside mqc, the class must either have a
bandwidth reservation configured, or it should be the defalut class with
fair-queue enable.

But lets say there is no bandwidth reservation needed. Then, how can I match
access-list only using

policy-map WWW_POLICY
class class-default
fair-queue
random-detect
random-detect 5 60 90 5

-- 


This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:19 GMT-3