From: Chris Lewis \(chrlewis\) (chrlewis@cisco.com)
Date: Wed Jul 27 2005 - 12:58:48 GMT-3
In the first case, LLQ can take 32K of the available 64K, all traffic
will be subject to the 64K shaped rate; in the second case LLQ traffic
can take 32K and all other traffic can take 64K for a total of 96K.
Chris
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
toonsh dosh
Sent: Wednesday, July 27, 2005 9:48 AM
To: ccielab@groupstudy.com
Subject: FRTS query
Hi
I have a question with this sample configuration below take from
MQC-Based Frame-Relay configuration doc:
class-map voice
match ip dscp ef
policy-map llq
class voice
priority 32
policy-map shape
class class-default
shape average 64000
shape adaptive 32000
service-policy llq <---------------------------------- Why
do
they nest this LLQ policy
interface serial0/0
encapsulation frame-relay
interface serial0/0.1 point-to-point
ip address 192.168.1.1 255.255.255.0
frame-relay interface-dlci 100
class shape
Why is it that they create a LLQ policy and then nest it under the
default
class. What would have been the difference if the did it in the
following
manner:
policy-map shape
class llq
priority 32
class class-default
shape average 64000
shape adaptive 32000
So have two seperate classes under the "policy-map shape".
Thanks
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:31 GMT-3