From: McClure, Allen (Allen.McClure@Yum.com)
Date: Fri Oct 10 2003 - 14:48:10 GMT-3
You shouldn't really mess with max-reserved unless you are required to
IMO.
I think that it's important to realize that the default-class is
generally used as a "best-effort" dumping ground. With that being the
case, you certainly want the classes that you took the time and effort
to define to be allocated bandwidth, policed, or whatever, assuming that
is the goal. Otherwise, what would be the point in defining non-default
classes in the first place?
I could be missing the point, let me know.
Allen G. McClure
CCNP/CCDP/MCSE
Yum! Brands, Inc.
Sr. Network Analyst
allen.mcclure@yum.com
-----Original Message-----
From: Chris Larson [mailto:clarson52@comcast.net]
Sent: Friday, October 10, 2003 12:39 PM
To: ccielab@groupstudy.com
Subject: Class Default
If we are asked to configure multiple classes for CBWFQ and a class for
all other traffic ( a default) then wouldn't it be the case that we
should make max reserved bandwidth 0
Any traffic that does not confirm to the defined classes would go into
the configure default class and therefore I think you would not want to
keep any reserved bandwidth on the interface.
It would all go towards the policy that has the configured default
class?
Is that correct?
***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
This archive was generated by hypermail 2.1.4 : Mon Nov 24 2003 - 07:53:00 GMT-3