From: Joe Smith (j333smith@hotmail.com)
Date: Fri Feb 04 2005 - 15:57:05 GMT-3
It really depends on what you want to do. But lets say in this example you
want to limit WWW traffic to 10 Mbps FTP traffic to 5 Mbps and all TCP
traffic to 200 Mbps:
1) The first way that you identified thats in the DQOS book:
match all TCP traffic 200 Mbps Conform continue, exceed drop
match WWW traffic 10 Mbps Conform transmit, exceed drop
match FTP traffic 5 Mbps Conform transmit, exceed drop
Assume:
WWW traffic is 20 Mbps
FTP traffic 10 Mbps
Other TCP traffic is 185 Mbps
TCP Total is 215 Mbps
The first line indiscriminately cuts the TCP rate down, so you dont know
which TCP packets will be dropped. Now lets say in this example that all
the WWW traffic passed and all (10 Mbps) of the FTP traffic along with 5
Mbps of other TCP traffic were dropped. Then the final transmitted packets
would be:
WWW traffic - 10 Mbps
FTP traffic 0 Mbps
Other TCP traffic 180 Mbps
TCP Total 190 Mbps
2) You could reverse the statements from above:
match WWW traffic 10 Mbps Conform continue, exceed drop
match FTP traffic 5 Mbps Conform continue, exceed drop
match all TCP traffic 200 Mbps Conform transmit, exceed drop
Again assuming:
WWW traffic is 20 Mbps
FTP traffic is 10 Mbps
Other TCP traffic is 185 Mbps
TCP Total is 215 Mbps
Now the following occurs:
WWW traffic 10 Mbps
FTP traffic 5 Mbps
Other TCP traffic 185 Mbps
TCP Total 200 Mbps
The first case indiscriminately cuts all TCP traffic before anything else,
so traffic you are going to limit anyway adds to the total TCP traffic. So
its possible that you could go under the desired rate.
The second limits certain traffic before it adds it to the total TCP
traffic. Doing it this way will actually give you closer to the desired
rate and might be a better choice given the requirements.
J3
>From: null void <nullv0idmain@yahoo.com>
>Reply-To: null void <nullv0idmain@yahoo.com>
>To: ccielab@groupstudy.com
>Subject: CAR conform-action details
>Date: Fri, 4 Feb 2005 08:05:56 -0800 (PST)
>
>Hi, I was wondering if anyone has further information on
>conform-action-continue option when configuring CAR , in the dqos / odom
>book in the policing section it shows a few multi-line rate-limit examples
>but doesnt really clarify what is required or give detail.. Say we have the
>following situation:
>
>Limit traffic out of R1 G0/0 interface for traffic destined to hosts on
>subnet 1.1.1.x from your networks. TCP traffic must be limited to 200Mbps ,
>WWW traffic to 10Mbps , TCP port 3389 to 10Mbps , ftp traffic to 5 Mbps.
>In the dqos book they show the most specific item listed first which in
>this case would be all TCP traffic to rate-limit of 2000000 , then they use
>the conform-action continue , down to 3 other lines that or more granular
>than just all TCP traffic , so my question is if you have a multi line
>rate-limit policy to apply what is the thought process in ordering the
>lines and is the conform-action-continue statement required on the first
>rate-limit command to use say rate-limit lines 2 through 6 for example..
>Below is from a cco doc and this is really all I can find about it.
>TIA Null
>
>ContinueThe packet is evaluated using the next rate policy in a chain of
>rate limits. If there is not another rate policy, the packet is transmitted
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Mar 03 2005 - 08:51:17 GMT-3