From: Chris Lewis \(chrlewis\) (chrlewis@cisco.com)
Date: Thu Aug 11 2005 - 10:39:22 GMT-3
Hi Gladston,
This looks like an order of operation issue. For the physical interface,
if you enter the commands in the same order as the class based
configuration is requesting them, the commands are accepted.
Starting here:
!
interface Serial1/0
ip address 131.108.50.1 255.255.0.0
!
The commands can be applied as follows:
R1(config)#int s1/0
R1(config-if)#fair-queue
R1(config-if)#random-detect
Chris
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
gladston@br.ibm.com
Sent: Thursday, August 11, 2005 8:10 AM
To: ccielab@groupstudy.com
Subject: WRED on Physical Interface and CBWFQ
Hi,
Do you know what is the logic behind the following behavior of IOS?
Under class-default of CBWFQ, WRED requires fair-queue to be configured.
Under physical interface, WRED requires fair-queue to be removed.
Tests:
WRED applyed on class-default
Rack2R5(config-pmap)#class class-default
Rack2R5(config-pmap-c)#random-detect dscp-b fair-queue or bandwidth on
the class is required to issue this command
Rack2R5(config-pmap-c)#fair-queue Rack2R5(config-pmap-c)#random-detect
dscp-b
WRED applyed on physical:
Rack2R5(config-if)#int ser 0/1
Rack2R5(config-if)#fair-queue
Must remove RED configuration first.
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:19 GMT-3