1
00:00:00,800 --> 00:00:06,800
So close based, waited for queuing, ensures that traffic classes get fair bandwidth guarantees.

2
00:00:07,160 --> 00:00:14,690
In other words, you can guarantee a minimum bandwidth to HTTP, a minimum bandwidth to FTP, minimum

3
00:00:14,690 --> 00:00:18,890
bandwidth to voice traffic, video traffic and so on.

4
00:00:19,460 --> 00:00:22,970
But there's no latency guarantees.

5
00:00:23,120 --> 00:00:26,000
In other words, there is no priority queue.

6
00:00:26,360 --> 00:00:30,110
Class based weighted for queuing is suitable only for data networks.

7
00:00:30,590 --> 00:00:39,250
So Cisco developed a low latency queuing or long queue, which to give you the full name is pro queue

8
00:00:39,260 --> 00:00:41,360
class based waited for queuing.

9
00:00:41,690 --> 00:00:47,000
In other words, it's class based, waited for queuing with an added priority queue.

10
00:00:47,510 --> 00:00:54,050
So it takes the previous model of class based, waited for queuing and adds a queue with strict priority

11
00:00:54,050 --> 00:00:55,730
for real time traffic.

12
00:00:56,900 --> 00:01:05,239
So the idea is, is when packets arrive based on a class or classification mechanism that you decide

13
00:01:05,570 --> 00:01:12,680
traffic is put into different classes, voice traffic is put into the priority queue and is prioritized

14
00:01:12,680 --> 00:01:14,270
over other traffic types.

15
00:01:15,270 --> 00:01:17,430
FTP http.

16
00:01:18,140 --> 00:01:23,600
And other traffic types are put into their own classes with minimum bandwidth guarantees.

17
00:01:24,530 --> 00:01:33,020
Now to ensure that the priority queue doesn't starve the other queues, the priority queue has a minimum

18
00:01:33,020 --> 00:01:36,260
bandwidth guarantee but is also policed.

19
00:01:36,350 --> 00:01:39,350
So it also has a maximum bandwidth limit.

20
00:01:39,770 --> 00:01:47,900
So when you specify the priority of the low latency priority queue, that is actually a minimum and

21
00:01:47,900 --> 00:01:48,830
maximum.

22
00:01:50,190 --> 00:01:56,070
Which provides a minimum bandwidth guarantee for voice, but also ensures that voice doesn't starve

23
00:01:56,070 --> 00:01:57,870
the other traffic types.

