So close based, waited for queuing, ensures that traffic classes get fair bandwidth guarantees.
In other words, you can guarantee a minimum bandwidth to HTTP, a minimum bandwidth to FTP, minimum
bandwidth to voice traffic, video traffic and so on.
But there's no latency guarantees.
In other words, there is no priority queue.
Class based weighted for queuing is suitable only for data networks.
So Cisco developed a low latency queuing or long queue, which to give you the full name is pro queue
class based waited for queuing.
In other words, it's class based, waited for queuing with an added priority queue.
So it takes the previous model of class based, waited for queuing and adds a queue with strict priority
for real time traffic.
So the idea is, is when packets arrive based on a class or classification mechanism that you decide
traffic is put into different classes, voice traffic is put into the priority queue and is prioritized
over other traffic types.
FTP http.
And other traffic types are put into their own classes with minimum bandwidth guarantees.
Now to ensure that the priority queue doesn't starve the other queues, the priority queue has a minimum
bandwidth guarantee but is also policed.
So it also has a maximum bandwidth limit.
So when you specify the priority of the low latency priority queue, that is actually a minimum and
maximum.
Which provides a minimum bandwidth guarantee for voice, but also ensures that voice doesn't starve
the other traffic types.