From: Steven A. Ridder (saridder@xxxxxxxxx)
Date: Thu Jul 04 2002 - 18:12:15 GMT-3
CAR is incoming, as in you use it on an incoming interface such as what
a frame switch does to you to enforce the CIR.
CBWFQ is a queuing mechanism on outgoing interfaces. It does not drop
packet, but will delay to send after more important traffic has been
passed. Car will shoot traffic dead if you exceed a limit.
--- RFC 1149 Compliant.-----Original Message----- From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of William Wong Kun Sing Sent: Tuesday, July 02, 2002 6:27 AM To: 'Colin Barber'; ccielab@groupstudy.com Subject: RE: CAR vs CBWFQ
CAR is basically used for the traffic policing which to prevent the global sync (TCP slow start behaviour waste the bandwidth) so that the bandwidth will be fully utilised. CAR will not shape the traffic which is done by GTS or FRTS or what we call as traffic shaping.
CBWFQ is a Congestion Management Tool which do the scheduling of packet forwarding. Yes, car is for ip only at the moment.
-----Original Message----- From: Colin Barber [mailto:Colin.Barber@telewest.co.uk] Sent: Tuesday, July 02, 2002 3:49 PM To: ccielab@groupstudy.com Subject: RE: CAR vs CBWFQ
I think CAR always 'shapes' your traffic as you defined. CBWFQ only 'shapes' when there is congestion and therefore is more bandwidth efficient.
Also does CAR only support IP?
Colin. -----Original Message----- From: Ted Richmond [mailto:rich_ted@yahoo.com] Sent: 02 July 2002 07:52 To: ccielab@groupstudy.com Subject: CAR vs CBWFQ
I am totally confused now!!! Can someone tell me when to use CAR / CBWFQ. Looks like both can be used to allocate bandwidth to different connections.
Thanks.
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:19 GMT-3