When using Policy Maps for implementing QoS, Is the below terminology correct
Under the Class, when using
Priority --> Mean strict queing and this much BW will Always be set aside and will not be available to non-matching traffic.Matching traffic, however can get more BW if available.
Bandwidth --> Router will try to make this much BW available to the matching application but its not Guaranteed, if the interface is fully congested. Matching traffic can get more BW than the specified value, if available.
Police--> No Min. BW is guaranteed. But router will limit the application to the specified value and drop any excess traffic, even when BW is available on the interface.
There is no real concept of bandwidth reservation when using QoS on a cisco router. When you configure 'priority' and 'bandwidth' statements, the router deducts the specified bandwidth from the available bandwidth for the interface. This just means that you cannot assign bandwidths to classes in a manner that exceeds the interface bandwidth. This, however, is a static allocation. There is no hard bandwidth allocation on the interface to any traffic class. The actual bandwidth split happens when there is actual traffic on the interface.
In the context of the above, the following applies to the various types of QoS actions:
Priority - this is indeed a strict priority queue. You need to consider two cases when thinking about this. In a congested state, the priority traffic will be policed to the confifugred bandwidth and will not be allowed to exceed it. In a non-congested stated, the priority queue can use up any extra bandwidth available. Note that the bandwidth allocated to the priority class is not reserved. If the priority queue is not using up its full bandwidth, other classes are free to use that bandwidth.
Bandwidth - this is the minimum guarantee of bandwidth to the class. This class was always get at least this much bandwidth, even under conditions of congestion. If spare bandwidth is available on the interface, the class can get more than the specified bandwidth.
Police - your understanding of this is correct.
Hope that helps - pls do rate the post if it does.
I think Paresh is making a little mistake, please let me correct you with courtesy.
- the priority class is scheduled before any other queue (up to the configured bandwidth)
: which means priority class is not available more than configured bandwidth, that is right but not by scheduler, by internal policer on PQ, and this is incosistent with your previous statement that "priority class can exceed the configured bandwidth when available".
Like I said before, the configured bandwidth is maximum bandwidth available to PQ, PQ and other Queue are working seperately until reach to queue-scheduler on interface, so without policer at PQ, other queues always being starved.
I thinks you are confusing with IP RPT PRIORITY, it work like exactly what you saying,basically it is activated only when congestion happens.
When the device is not congested, the priority class traffic is allowed to exceed its allocated bandwidth. When the device is congested, the priority class traffic above the allocated bandwidth is discarded.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...