From: Jens Petter Eikeland (jenseike@start.no)
Date: Mon Sep 12 2005 - 05:49:35 GMT-3
Well, I have experienced bot together so this I can not give you an answer
on. But I can try explain the differens between them .
Congestion Management-Often a network interface is congested (even at high
speeds, transient congestion is observed), and queueing techniques are
necessary to ensure that the critical applications get the forwarding
treatment necessary. For example, real-time applications such as VoIP,
stock-trading, etc. may need to be forwarded with the least latency and
jitter (up to a provisioned limit). Cisco's Low-Latency Queuing (LLQ)
provides for such a solution. For other non-delay sensitive traffic (such as
FTP, HTTP, etc.), other queuing techniques such as CBWFQ, and MDRR (Modified
Deficit Round-Robin) may be used. The queueing techniques can be
instantiated using the policy-framework of the MQC as well.
Traffic Conditioning-Traffic entering a network can be conditioned by using
a policer or shaper. A policer simply enforces a rate-limit, while a shaper
smoothes the traffic flow to a specified rate by the use of buffers. Once
again, mechanisms such as CAR (Committed Access Rate), GTS (Generic Traffic
Shaping), and FRTS (Frame-Relay Traffic Shaping) can be configured
without/within the MQC framework.
Jens Petter
-----Opprinnelig melding-----
Fra: Stefan Grey [mailto:examplebrain@hotmail.com]
Sendt: 12. september 2005 07:36
Til: jenseike@start.no; ccielab@groupstudy.com
Emne: RE: SV: Qos question (bandwidth,police).
Hi,
Thank you very much for your reply and for the link. But there is explained
just how the police and bandwidth commands are used separetely but not
together. I just need to find the difference between:
1.
policy-map LIMIT
class web
police 100000 conform-action transmit exceed action drop.
and
2.
policy-map LIMIT
class web
bandwidth 100
police 100000 conform-action transmit exceed action drop.
Could anybody tell something?? Because I don't see any. As I think during
the congestions both configs don't let traffic to be more than 100 M and
when there is no congestion there are no limiting in both case. Thanks.
>From: "Jens Petter Eikeland" <jenseike@start.no>
>Reply-To: "Jens Petter Eikeland" <jenseike@start.no>
>To: "'Stefan Grey'" <examplebrain@hotmail.com>, <ccielab@groupstudy.com>
>Subject: SV: Qos question (bandwidth,police).
>Date: Sun, 11 Sep 2005 23:28:21 +0200
>
>Hi ,
>
>I am sure you will get a better understanding of this two technologies by
>reading findings yourselfe
>
>Here is a some good documents covering both technologies very vel
>
>http://www.cisco.com/en/US/tech/tk543/tk545/tech_design_guides_list.html
>
>Answer to your question is to use the policing command and conform it to
>100
>meg as in your example
>
>Jens Petter
>
>
>
>-----Opprinnelig melding-----
>Fra: nobody@groupstudy.com [mailto:nobody@groupstudy.com] Pe vegne av
>Stefan
>Grey
>Sendt: 11. september 2005 23:02
>Til: ccielab@groupstudy.com
>Emne: Qos question (bandwidth,police).
>
>It is needed to limit the input of some WEB traffic to 100 Megabyte.
>
>I saw such config in the book:
>policy-map LIMIT
>class web
>bandwidth 100
>police 100000 conform-action transmit exceed action drop.
>
>Whe could the bandwidth here be used. Whey to command are used together
>here.
>
>As I know police is really limiting traffic to 100 Mb. But bandwidth is for
>custom queuing.
>Could anybody comment this configuration???? What would be the difference
>between this config with or without bandwidth command.
>
>Thanks.
>
>_________________________________________________________________
>MSN Search Ireland has launched - test-drive it today! http://search.msn.ie
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:14 GMT-3