From: Alex De Gruiter \(AU\) (Alex.deGruiter@didata.com.au)
Date: Thu Oct 05 2006 - 21:42:13 ART
Right... I think I'm getting it. I definitely had misinterpretations of
the max-reserved-bandwidth command! I actually thought for some odd
reason that the maximum bandwidth available was 75% unless max-reserved
was entered - in hindsight that was a little silly of me!
On the note of "rest of traffic", if you were asked in the exam to
distribute the remaining bandwidth among the remaining traffic, would
you employ a queuing strategy for class-default (such as fair-queuing),
or would you use FIFO? If the exam doesn't stipulate either way, is
there a preference?
________________________________
From: sabrina pittarel [mailto:sabri_esame@yahoo.com]
Sent: Friday, 6 October 2006 10:32 AM
To: Alex De Gruiter (AU); ccielab@groupstudy.com
Subject: Re: max-reserved-bandwidth?
You have at least to set max-reserved-bandwidth to 90% (20 + 40 + 30),
otherwise you won't be able to apply the policy map on the interface.
The 10% will be left for overhead and rest of traffic.
Sabrina
----- Original Message ----
From: Alex De Gruiter (AU) <Alex.deGruiter@didata.com.au>
To: ccielab@groupstudy.com
Sent: Thursday, October 5, 2006 3:21:33 PM
Subject: max-reserved-bandwidth?
Hey Guys,
I have a question - I searched the archives and found a similar
reference, however I wasn't satisfied that the answer was definitively
defined.
If a question in the lab asks us to use CBWFQ in such a way as to
provide the following bandwidth allocations:
Class A : 20%
Class B : 40%
Class C : 30%
Then, distribute the remaining bandwidth among other classes, do we need
to modify the max-reserved-bandwidth? I tried this in my home lab and
received an error relating to the bandwidth available (which, by
default, is 75%).
What does everyone think? When would we need to change
max-reserved-bandwidth?
Alex
************************************************************************
******
- NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally
privileged information. If you have received this email in error,
please notify the sender and delete it immediately.
Internet communications are not secure. You should scan this message and
any attachments for viruses. Under no circumstances do we accept
liability for any loss or damage which may result from your receipt of
this message or any attachments.
************************************************************************
******
This archive was generated by hypermail 2.1.4 : Wed Nov 01 2006 - 07:29:04 ART