TO sum it up, it guarantees and limits bandwidth. The PQ gets services over
all the other queues (proably voice traffic) and then the CBQ gets serviced
according to the bandwidth you configure for each class. So when you config
the bandwidth you could consider is guaranteing what you put down or
Yes, but you can only do it once per policy map
R.
Dom Stocqueler.
"John
Neiberger"
cc:
If you want to truly guarantee bandwidth, use 'priority 2048' instead of
'bandwidth 2048'. This creates a true priority queue for that class of
traffic. The bandwidth command does its best to provide a certain
amount of bandwidth but it is not a true priority queue.
For more information, look u
> circuit.
>
> Regards,
>
> Dom Stocqueler
>
>
>
>
>
> "Hamid"
>
> cc:
> Sent by: Subject: CBWFQ (Class-Based
> Weighted Fair Queing) Question [7:26197]
>
> nobody@groups
>
> tudy.com
>
e a minimum bandwidth when there is congestion on the
> circuit.
>
> Regards,
>
> Dom Stocqueler
>
>
>
>
>
> "Hamid"
>
> cc:
> Sent by: Subject: CBWFQ (Class-Based
> Weighted Fair Queing) Question [7:26197]
>
cc:
Sent by: Subject: CBWFQ (Class-Based
Weighted Fair Queing) Question [7:26197]
nobody@groups
Hi
Studying CBWFQ, I was wondering if it guarantees bandwidth or just limits
the bandwidth:
class-map my-map
match access-group 151
policy-map my-policy
class my-map
bandwidth 2048
int fast0/0
service-policy input my-policy
access-list 151 permit ip
7 matches
Mail list logo
