WEBVTT

1
00:00.000 --> 00:05.280
All right, let's go ahead and do a quick configuration demonstration, seeing

2
00:05.280 --> 00:05.600
all the

3
00:05.600 --> 00:09.120
different ways that we can carve up the bandwidth on our interface.

4
00:09.120 --> 00:13.380
So we're going to do a config T, create a policy map here, we'll just call this

5
00:13.380 --> 00:13.880
policy

6
00:13.880 --> 00:19.720
map test, and we'll get on to the class default queue.

7
00:19.720 --> 00:24.280
And now what we can look at here is the different options that we have.

8
00:24.280 --> 00:28.740
So that priority command, remember, I, first of all, I can't configure the

9
00:28.740 --> 00:29.680
class default

10
00:29.680 --> 00:31.280
as a priority queue.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:29.680 --> 00:31.280
as a priority queue.

11
00:31.280 --> 00:34.280
But we do start to see some of the commands that we can use here.

12
00:34.280 --> 00:38.580
So as we've seen before, we can use the priority command to specify the

13
00:38.580 --> 00:39.760
bandwidth that not

14
00:39.760 --> 00:43.160
only is reserved, but also turns into that limit.

15
00:43.160 --> 00:47.800
If we don't just hit enter, if I just hit enter here, this will turn the queue

16
00:47.800 --> 00:48.600
into a strict

17
00:48.600 --> 00:49.600
priority queue.

18
00:49.600 --> 00:52.740
We have to be very careful about deploying that into an environment with

19
00:52.740 --> 00:54.080
intentionality.

20
00:54.080 --> 00:56.280
We definitely don't want to do it accidentally.

21
00:56.280 --> 00:59.680
So we should usually specify our bandwidth.

22
00:59.680 --> 01:01.240
Here's where we can specify the level.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.680 --> 01:01.240
Here's where we can specify the level.

23
01:01.240 --> 01:04.380
If I say priority level, now we get the one or two.

24
01:04.380 --> 01:07.880
So we'd want to configure this as level one, if it's for voice and level two,

25
01:07.880 --> 01:08.280
if it's for

26
01:08.280 --> 01:10.080
anything else, basically.

27
01:10.080 --> 01:13.020
And again, we have to be careful about deploying a second priority queue into

28
01:13.020 --> 01:13.880
the environment.

29
01:13.880 --> 01:17.320
That's not necessarily a recommendation every case.

30
01:17.320 --> 01:19.040
And here's where we can do percent as well.

31
01:19.040 --> 01:22.580
So if I do percent question mark, we're going to see that I can specify a

32
01:22.580 --> 01:23.480
percentage of

33
01:23.480 --> 01:25.360
the link bandwidth.

34
01:25.360 --> 01:30.510
I'm on a burst in there, but or we could just hit enter and allow us to reserve
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:25.360 --> 01:30.510
I'm on a burst in there, but or we could just hit enter and allow us to reserve

35
01:30.510 --> 01:31.440
50%.

36
01:31.440 --> 01:33.320
So that's the priority statement.

37
01:33.320 --> 01:37.160
So let's say I reserve 50% of the link for the priority queue.

38
01:37.160 --> 01:39.520
And now I'm on class with this other class.

39
01:39.520 --> 01:42.200
Now I can look at the bandwidth command.

40
01:42.200 --> 01:45.200
When I look at bandwidth, a lot of the same options exist.

41
01:45.200 --> 01:47.760
It's just no longer a priority situation.

42
01:47.760 --> 01:52.880
So I can't set a level, but I do number one, have the ability to specify kilob

43
01:52.880 --> 01:53.360
its per

44
01:53.360 --> 01:55.040
second as a raw value.

45
01:55.040 --> 01:56.800
I can also say percent.

46
01:56.800 --> 01:57.800
So same thing.

47
01:57.800 --> 02:02.480
I could say, hey, for this queue, I want to reserve 25% of my bandwidth, right?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:57.800 --> 02:02.480
I could say, hey, for this queue, I want to reserve 25% of my bandwidth, right?

48
02:02.480 --> 02:03.480
And hit enter.

49
02:03.480 --> 02:04.760
And there we go.

50
02:04.760 --> 02:07.560
Or I can use this bandwidth remaining command.

51
02:07.560 --> 02:10.040
So remaining, I just have to say percent.

52
02:10.040 --> 02:17.770
And now I can perform my logic as if I'm talking about 100% outside the

53
02:17.770 --> 02:19.840
priority queue.

54
02:19.840 --> 02:23.890
So just to be clear about this, if I'm doing a raw percent and I said, hey,

55
02:23.890 --> 02:24.800
that priority

56
02:24.800 --> 02:27.920
queue gets 50% of the link bandwidth.

57
02:27.920 --> 02:33.040
And let's say I have two other queues that I want to divide the bandwidth among
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:27.920 --> 02:33.040
And let's say I have two other queues that I want to divide the bandwidth among

58
02:33.040 --> 02:33.720
Q1 here

59
02:33.720 --> 02:36.640
and then Q2, which is probably our class default.

60
02:36.640 --> 02:41.320
So if I'm doing a raw percentage, I do 50% of the priority queue.

61
02:41.320 --> 02:43.840
Q1 would be 25%.

62
02:43.840 --> 02:46.280
Q2 would be 25%.

63
02:46.280 --> 02:48.920
And there is my 100%.

64
02:48.920 --> 02:55.590
If I'm doing a remaining methodology, the remaining percent, my priority is

65
02:55.590 --> 02:56.680
still going

66
02:56.680 --> 03:01.800
to be 50% because this is still specified as a raw value.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
02:56.680 --> 03:01.800
to be 50% because this is still specified as a raw value.

67
03:01.800 --> 03:07.860
But the remaining, remember, it removes the priority queue from the calculation

68
03:07.860 --> 03:07.880
.

69
03:07.880 --> 03:14.510
So if I want to divide the rest of the interface bandwidth between those two

70
03:14.510 --> 03:16.400
queues, Q1 would

71
03:16.400 --> 03:27.080
get remaining 50% and Q2 would get remaining 50% as well.

72
03:27.080 --> 03:31.610
And so this just makes the math a little easier where here with the raw, this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:27.080 --> 03:31.610
And so this just makes the math a little easier where here with the raw, this

73
03:31.610 --> 03:32.600
whole thing adds

74
03:32.600 --> 03:34.360
up to 100%.

75
03:34.360 --> 03:40.080
With remaining percent, it's all of these non-priority queues that add up to

76
03:40.080 --> 03:41.360
100%.

77
03:41.360 --> 03:45.050
And so this can make it easier, for example, what if I had a situation where,

78
03:45.050 --> 03:45.720
yeah, the

79
03:45.720 --> 03:51.390
priority queue gets 50%, but now I actually have three queues and I want to

80
03:51.390 --> 03:52.520
divide things

81
03:52.520 --> 03:55.320
up evenly among these three queues.

82
03:55.320 --> 04:00.770
Well with the raw percentage, I'm going to have to take a third of 50% and so
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
03:55.320 --> 04:00.770
Well with the raw percentage, I'm going to have to take a third of 50% and so

83
04:00.770 --> 04:01.400
that is

84
04:01.400 --> 04:08.540
like 16ish percent, something like that is 16.5% and try to get maybe 16, 16,

85
04:08.540 --> 04:10.120
17, something

86
04:10.120 --> 04:11.560
like that.

87
04:11.560 --> 04:14.800
Or with the remaining side, I could just say, hey, you know what?

88
04:14.800 --> 04:19.720
I just want all of these to have 33% and I'll assign one extra percent to one

89
04:19.720 --> 04:20.320
of the other

90
04:20.320 --> 04:21.320
queues.

91
04:21.320 --> 04:26.320
This math is typically a little bit easier with the remaining concept rather

92
04:26.320 --> 04:26.960
than the

93
04:26.960 --> 04:31.690
raw over here, which has to take into account the percentage that was reserved
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
04:26.960 --> 04:31.690
raw over here, which has to take into account the percentage that was reserved

94
04:31.690 --> 04:32.680
for the priority

95
04:32.680 --> 04:33.680
queue.

96
04:33.680 --> 04:37.900
So it's a little bit of a shortcut method and we do see a lot of remaining

97
04:37.900 --> 04:39.120
percent out there

98
04:39.120 --> 04:43.880
in the real world, but again, just find the configuration you're most

99
04:43.880 --> 04:45.120
comfortable with

100
04:45.120 --> 04:48.780
that makes the most sense for you and the environment that you're configuring

101
04:48.780 --> 04:49.320
this in.