A couple of considerations when deciding between traffic shaping and CAR:
Traffic shaping is not supported with optimum, distributed, or flow
switching. If you enable this command, all interfaces will revert to fast
switching.
CEF must be enabled on the interface before you configure CAR or DCAR.
ref:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/qos_r
/qrcmdr.htm#xtocid498924
&i
-----Original Message-----
From: Charles Sprickman [mailto:spork@inch.com]
Sent: Friday, May 18, 2001 10:01 AM
To: George Robbins
Cc: gert@greenie.muc.de; goemon@anime.net; cisco-nsp@puck.nether.net
Subject: Re: [nsp] generic traffic shaping
On Fri, 18 May 2001, George Robbins wrote:
> What are you wanting? Whether it's simple or extended, the second
> part is a wildcard mask and .14 is 00001110 which will match only
> eight even IP addresses. This is probably not what you intended.
Yep, as someone else pointed out that should be .15 (255-mask).
I also have another rule with a full C, and seeing similar results.
Anyone use this stuff, or is CAR better? This seemed more "gentle" than
CAR; at least going by how the docs described it...
I still see no affect, and I'm throwing it on a block doing about 1.5 Mb
constant and trying to keep it down to 700K/b.
I'm going to play with CAR now.
Thanks,
C
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:38 EDT