10-22-2012 04:56 AM - edited 03-05-2019 06:48 AM
Hello everyone!
I have the following:
policy-map subnets
class VLAN20
priority percent 20
class VLAN40
priority percent 20
class VLAN60
bandwidth percent 40
class VLAN80
bandwidth percent 10
interface Serial0/0:0
bandwidth 2000
ip address 172.23.0.1 255.255.255.252
max-reserved-bandwidth 90
service-policy output subnets
VLAN20 and VLAN40 classes are needed to be low-latency because it will be used for VoIP, that's why I used priority commands for LLQ.
I have noticed that during no congestion, the classes that use priority command do not utilize the whole bandwidth, seems like there is a policer. Is that a normal behavior? Can I make it utilize the entire bandwidth when the link is free?
I used iperf to measure. See the attachment for more details. Note that in this case there is no activity in VLAN20 and VLAN80.
Hoping to get some help here.
Thanks. =)
Solved! Go to Solution.
10-23-2012 09:43 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
LLQ classes have an implicit policer that normally only engages when there's link congestion.
If your LLQ classes already don't push to saturate the link, changing their class parameters shoudln't result in their using more bandwidth.
10-22-2012 09:53 PM
Hi Haji,
You have applied two classes to the priority queue. Inside the priority queue it is basically FIFO.
Moreover, you have reserved only 20% on interface bandwidth to be used by Priority Queue, so even if there is bandwidth available in other class, it won't be using that bandwidth.
As per Cisco's recommendation, they suggest to assign atleast 33% of interface bandwidth to the Priority Queue.
Kindly let us know if you have more concerns.
Regards,
Smitesh
PS: Please rate helpful posts.
10-23-2012 09:43 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
LLQ classes have an implicit policer that normally only engages when there's link congestion.
If your LLQ classes already don't push to saturate the link, changing their class parameters shoudln't result in their using more bandwidth.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide