WRED on Physical Interface and CBWFQ

From: gladston@br.ibm.com
Date: Thu Aug 11 2005 - 10:09:52 GMT-3

• Next message: rionaldi@cbn.net.id: "Remote Lab and Local Lab"
• Previous message: richard.harvey@nbs.nhs.uk: "RE: uplink fast or backbone fast"
• Next in thread: Chris Lewis \(chrlewis\): "RE: WRED on Physical Interface and CBWFQ"
• Maybe reply: Chris Lewis \(chrlewis\): "RE: WRED on Physical Interface and CBWFQ"
• Maybe reply: gladston@br.ibm.com: "RE: WRED on Physical Interface and CBWFQ"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

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.

• Next message: rionaldi@cbn.net.id: "Remote Lab and Local Lab"
• Previous message: richard.harvey@nbs.nhs.uk: "RE: uplink fast or backbone fast"
• Next in thread: Chris Lewis \(chrlewis\): "RE: WRED on Physical Interface and CBWFQ"
• Maybe reply: Chris Lewis \(chrlewis\): "RE: WRED on Physical Interface and CBWFQ"
• Maybe reply: gladston@br.ibm.com: "RE: WRED on Physical Interface and CBWFQ"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

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