WEBVTT 1 00:00.000 --> 00:04.680 Well, what luck that we have another very fun lab for us to do. 2 00:04.680 --> 00:09.330 I really do enjoy the QOS labs because it takes a very difficult concept and it 3 00:09.330 --> 00:09.720 makes 4 00:09.720 --> 00:10.720 it reality. 5 00:10.720 --> 00:14.030 We kind of see it come to life when we're looking at those show commands and we 6 00:14.030 --> 00:14.340 see 7 00:14.340 --> 00:16.000 what the packets are doing. 8 00:16.000 --> 00:19.910 And here in this lab, if you did it, you probably saw that the police are able 9 00:19.910 --> 00:21.480 to block traffic. 10 00:21.480 --> 00:25.210 So if you had any issues, then we're going to go through the solution together 11 00:25.210 --> 00:25.600 and the 12 00:25.600 --> 00:29.640 lab script is once again provided below for the solution. 13 00:29.640 --> 00:31.560 So let's go through this process here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:29.640 --> 00:31.560 So let's go through this process here. 14 00:31.560 --> 00:36.280 What we're going to do is we're going to get on to router two and we want to 15 00:36.280 --> 00:37.080 configure 16 00:37.080 --> 00:38.080 a policeor. 17 00:38.080 --> 00:41.830 Now to start with, we suggested that we come over to router one and we do a 18 00:41.830 --> 00:42.480 ping over 19 00:42.480 --> 00:43.480 to 10.12.0.2. 20 00:43.480 --> 00:49.690 With a size of 1500 bytes, we could repeat it a few times, 50 or 100 times and 21 00:49.690 --> 00:50.280 we see that 22 00:50.280 --> 00:53.830 all of our pings are going through because we don't have anything configured on 23 00:53.830 --> 00:54.240 router 24 00:54.240 --> 00:55.240 two yet. 25 00:55.240 --> 01:00.190 So we're going to configure a policy map as a policeor and we're told to start WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 00:55.240 --> 01:00.190 So we're going to configure a policy map as a policeor and we're told to start 26 01:00.190 --> 01:00.640 with a 27 01:00.640 --> 01:04.280 two color just sort of that basic policeor concept. 28 01:04.280 --> 01:08.890 So the way we're going to do that is by simply creating a policy map and we'll 29 01:08.890 --> 01:09.480 call this 30 01:09.480 --> 01:17.590 policeor, we'll call it, this is the single rate dual, we'll just call this 31 01:17.590 --> 01:18.640 basic. 32 01:18.640 --> 01:20.240 Police are basic, we'll keep it simple. 33 01:20.240 --> 01:24.800 And we'll get on to our class default, just to block all traffic here, we're 34 01:24.800 --> 01:25.440 going to 35 01:25.440 --> 01:30.200 use the police command and we were told to block it down to eight kilobits per WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 01:25.440 --> 01:30.200 use the police command and we were told to block it down to eight kilobits per 36 01:30.200 --> 01:30.960 second. 37 01:30.960 --> 01:34.390 Now if we do a question mark, we'll see that the CIR, that's the lowest rate 38 01:34.390 --> 01:35.040 possible. 39 01:35.040 --> 01:39.520 And we're sending 1500 byte pings, 8000 isn't a whole lot. 40 01:39.520 --> 01:43.960 So feel free to play with this number a little bit, see how that impacts things 41 01:43.960 --> 01:43.960 . 42 01:43.960 --> 01:47.800 I'll also stick with the lab script here and say we're going to do 8000. 43 01:47.800 --> 01:52.920 And that CIR parameter is actually optional as we talked about. 44 01:52.920 --> 01:55.480 And then we want the bucket size to be 2000. 45 01:55.480 --> 01:58.280 So I can just say 2000 here. 46 01:58.280 --> 02:00.280 And that's the entirety of the command. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 01:58.280 --> 02:00.280 And that's the entirety of the command. 47 02:00.280 --> 02:03.920 Now I could keep going on this one line and say my conform action. 48 02:03.920 --> 02:09.200 I usually like to hit enter here and add the conform action within the police 49 02:09.200 --> 02:10.440 configuration. 50 02:10.440 --> 02:16.640 And so we know we want to transmit our conform action and our exceed action. 51 02:16.640 --> 02:19.080 We want this to drop. 52 02:19.080 --> 02:25.600 So let's go and apply that to the interface and gig one zero service policy. 53 02:25.600 --> 02:29.000 And we'll say police are basic. 54 02:29.000 --> 02:30.440 And I didn't specify the direction. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 02:29.000 --> 02:30.440 And I didn't specify the direction. 55 02:30.440 --> 02:36.520 This police is going to go in the input direction. 56 02:36.520 --> 02:43.760 So show policy map interface gig one zero. 57 02:43.760 --> 02:48.220 And we see our policing configuration with the CIR and the BC and how many 58 02:48.220 --> 02:48.920 packets have 59 02:48.920 --> 02:50.880 conformed and exceeded. 60 02:50.880 --> 02:53.740 So now if I come back here and do my pings, we're going to start to see that we 61 02:53.740 --> 02:54.360 're dropping 62 02:54.360 --> 02:55.360 packets. 63 02:55.360 --> 02:59.510 This is what we demoed earlier on with that's about every other packets going 64 02:59.510 --> 03:00.240 through. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 02:59.510 --> 03:00.240 through. 65 03:00.240 --> 03:03.920 And over here now when we run this command again, we will see that we are 66 03:03.920 --> 03:04.640 having some 67 03:04.640 --> 03:07.880 packets fall into that exceeded bucket. 68 03:07.880 --> 03:10.520 So that's the basic police. 69 03:10.520 --> 03:14.670 And our ones, you know, I'm just going to go ahead and stop that with control 70 03:14.670 --> 03:16.560 shift six. 71 03:16.560 --> 03:19.640 And that makes it so that we don't have to ping all 50 times. 72 03:19.640 --> 03:23.480 But we do see that that ended up making an impact. 73 03:23.480 --> 03:27.530 Now the three color police are is going to be a little bit different going to 74 03:27.530 --> 03:27.960 involve 75 03:27.960 --> 03:29.440 some additional parameters. 76 03:29.440 --> 03:31.880 So for this, we're going to create a different policy map. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 76 03:29.440 --> 03:31.880 So for this, we're going to create a different policy map. 77 03:31.880 --> 03:37.270 We'll call this police are advanced or adv there and then do a class class 78 03:37.270 --> 03:38.320 default to put 79 03:38.320 --> 03:40.880 everything into the default queue. 80 03:40.880 --> 03:45.790 And now we're told to once again, use the police command, we're told traffic 81 03:45.790 --> 03:46.480 less than 82 03:46.480 --> 03:47.960 eight kilobits per second. 83 03:47.960 --> 03:49.680 So I could just say 8k here, 8000. 84 03:49.680 --> 03:54.200 We've got so many different ways of doing things. 85 03:54.200 --> 03:57.750 And it's going to be classified one way and then between eight and 10 as 86 03:57.750 --> 03:58.440 another. 87 03:58.440 --> 04:00.640 So we're talking about between two rates. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 87 03:58.440 --> 04:00.640 So we're talking about between two rates. 88 04:00.640 --> 04:05.050 Now we have a two rate police are so we're going to have two buckets BC and B 89 04:05.050 --> 04:05.480 we're going 90 04:05.480 --> 04:09.580 to have the two different rates of tokens flowing into those buckets and our 91 04:09.580 --> 04:10.120 packets 92 04:10.120 --> 04:14.360 are going to try to consume both of those tokens if they're available. 93 04:14.360 --> 04:17.750 Otherwise it's going to drop down to exceeding if there's a B E token available 94 04:17.750 --> 04:18.480 and if there's 95 04:18.480 --> 04:22.080 no tokens available, it's going to be a violating packet. 96 04:22.080 --> 04:26.920 So when we can use question mark to kind of figure out what we're doing here. 97 04:26.920 --> 04:28.520 In fact, let's just go and be clear. 98 04:28.520 --> 04:30.680 We're going to enter all the parameters this time. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 98 04:28.520 --> 04:30.680 We're going to enter all the parameters this time. 99 04:30.680 --> 04:38.250 So I'm going to say CIR of 8000 BC, we were told to use bucket sizes of 2000 100 04:38.250 --> 04:38.720 bytes. 101 04:38.720 --> 04:45.220 And then we can specify the PIR to be that 10,000 or 10k and then be to be 2000 102 04:45.220 --> 04:46.120 as well. 103 04:46.120 --> 04:49.520 Now once again, I can hit question mark and see I can specify my actions on the 104 04:49.520 --> 04:50.160 same line 105 04:50.160 --> 04:52.680 or I can hit enter and start to do that. 106 04:52.680 --> 04:59.010 So we're going to do our conform action transmit our violate action is going to 107 04:59.010 --> 05:00.440 be drop. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 107 04:59.010 --> 05:00.440 be drop. 108 05:00.440 --> 05:03.880 And then in the middle here, our exceed action, what are we going to do? 109 05:03.880 --> 05:06.760 Well, we were told to wipe the DSCP tag. 110 05:06.760 --> 05:10.040 So I'm going to say set DSCP transmit. 111 05:10.040 --> 05:14.210 And then the tag that I want is again, either zero here, so I can just enter 112 05:14.210 --> 05:15.200 the raw number 113 05:15.200 --> 05:19.360 or I can use default, which is also zero. 114 05:19.360 --> 05:24.560 So I'm just going to say default here, exit out. 115 05:24.560 --> 05:30.200 And now we could apply this into gig one slash zero. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 115 05:24.560 --> 05:30.200 And now we could apply this into gig one slash zero. 116 05:30.200 --> 05:38.080 So we should have to remove the previous service policy. 117 05:38.080 --> 05:45.360 Basic and now say service policy input, please or a DV. 118 05:45.360 --> 05:51.650 All right, so show policy map interface will show us pretty much the same type 119 05:51.650 --> 05:53.280 of configuration, 120 05:53.280 --> 05:56.160 but we do now see that we have dual rates happening here. 121 05:56.160 --> 06:00.400 We've got PIR and CIR, we have BC and BE. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 05:56.160 --> 06:00.400 We've got PIR and CIR, we have BC and BE. 122 06:00.400 --> 06:05.240 Notice if we had BC and BE, but not a second rate, that would be a single rate 123 06:05.240 --> 06:06.160 three color 124 06:06.160 --> 06:10.000 policeor and it would use the overflow bucket method. 125 06:10.000 --> 06:14.280 So now we have conformed, exceeded and violated. 126 06:14.280 --> 06:16.280 Let's go ahead and generate some traffic here. 127 06:16.280 --> 06:19.320 We see that we are still losing some packets. 128 06:19.320 --> 06:22.000 So those would be packets that classify as violated. 129 06:22.000 --> 06:23.400 Let's see if we nailed the. 130 06:23.400 --> 06:24.400 Yeah. 131 06:24.400 --> 06:26.700 We're not going to have a whole lot falling into the exceeded range just 132 06:26.700 --> 06:27.240 because those 133 06:27.240 --> 06:31.540 ranges are so close to each other, but we should occasionally get an exceeded WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 133 06:27.240 --> 06:31.540 ranges are so close to each other, but we should occasionally get an exceeded 134 06:31.540 --> 06:32.020 packet 135 06:32.020 --> 06:33.020 in here. 136 06:33.020 --> 06:36.650 Doesn't look like we're going to get any this time, but we could actually tweak 137 06:36.650 --> 06:36.960 that 138 06:36.960 --> 06:41.640 configuration to see if we are getting any packets that fall into that category 139 06:41.640 --> 06:41.720 . 140 06:41.720 --> 06:46.900 So let's do a config T and actually what we want to do next is we want to 141 06:46.900 --> 06:47.920 configure the 142 06:47.920 --> 06:54.080 shaper on router one, so we're going to flip over to router one and create that 143 06:54.080 --> 06:54.760 policy 144 06:54.760 --> 06:56.000 map. 145 06:56.000 --> 07:02.300 This will be very similar to what we did in the video, but that's fine. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 145 06:56.000 --> 07:02.300 This will be very similar to what we did in the video, but that's fine. 146 07:02.300 --> 07:03.460 Good exercise. 147 07:03.460 --> 07:07.200 Get onto that class default to do a shape average command. 148 07:07.200 --> 07:11.460 And we were told to shape it to match the eight kilobits per second. 149 07:11.460 --> 07:15.820 So I'm just going to say eight thousand here and we don't worry about BC or 150 07:15.820 --> 07:16.720 anything like 151 07:16.720 --> 07:17.720 that. 152 07:17.720 --> 07:20.320 We're going to get a shape average eight thousand. 153 07:20.320 --> 07:22.920 Yeah, actually we're supposed to use the 2000. 154 07:22.920 --> 07:24.440 So let's go and do that. 155 07:24.440 --> 07:27.320 So one of the key things here again is that it's in bits. 156 07:27.320 --> 07:31.920 So we multiply it by eight to get bits instead of bytes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 156 07:27.320 --> 07:31.920 So we multiply it by eight to get bits instead of bytes. 157 07:31.920 --> 07:39.120 So our 2000 becomes a 16,000 for both of those bucket sizes. 158 07:39.120 --> 07:47.240 Now we can get onto our interface gig zero zero service policy output shaper. 159 07:47.240 --> 07:55.090 And then we're just going to ping and see if things operate a little bit better 160 07:55.090 --> 07:55.400 . 161 07:55.400 --> 07:57.960 Probably not in this case for the most part. 162 07:57.960 --> 07:59.440 It looks like we did get a little bit. 163 07:59.440 --> 08:00.440 Oh, yeah, look at that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 163 07:59.440 --> 08:00.440 Oh, yeah, look at that. 164 08:00.440 --> 08:03.120 We've actually got some things coming through now at a slower pace. 165 08:03.120 --> 08:08.320 Notice how it's going at a slower pace than what it would otherwise. 166 08:08.320 --> 08:13.390 But the reality is that at 1500 byte pings, we should be able to get every one 167 08:13.390 --> 08:14.000 of those 168 08:14.000 --> 08:15.480 through if we go slow enough. 169 08:15.480 --> 08:17.200 So this is what we're talking about here. 170 08:17.200 --> 08:20.920 If we're just firing them off as fast as we can, packets are going to drop 171 08:20.920 --> 08:21.240 because we 172 08:21.240 --> 08:23.560 don't match the police. 173 08:23.560 --> 08:26.360 So now we see every packet is actually going through. 174 08:26.360 --> 08:29.600 I think this is really cool actually. 175 08:29.600 --> 08:33.670 So they're all going through, but they we have had to slow down our rate to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 175 08:29.600 --> 08:33.670 So they're all going through, but they we have had to slow down our rate to 176 08:33.670 --> 08:34.200 match the 177 08:34.200 --> 08:37.240 eight kilovits per second that the police are is. 178 08:37.240 --> 08:40.490 But because we've matched that rate, even though we got off to a rough start, 179 08:40.490 --> 08:40.800 we did 180 08:40.800 --> 08:45.920 find equilibrium and we're now sending all of those packets in a way that they 181 08:45.920 --> 08:46.360 're not 182 08:46.360 --> 08:48.800 getting dropped by the upstream police. 183 08:48.800 --> 08:53.000 So make sure you take the time to play in this lab as much as needed to drill 184 08:53.000 --> 08:53.360 that or 185 08:53.360 --> 08:58.280 drive these points home, build the different types of police. 186 08:58.280 --> 09:01.630 Make sure you can form a shaper that works and all of these different WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 186 08:58.280 --> 09:01.630 Make sure you can form a shaper that works and all of these different 187 09:01.630 --> 09:02.680 configurations are 188 09:02.680 --> 09:06.360 going to be important because we're going to want to be able, as the blueprint 189 09:06.360 --> 09:06.800 says, 190 09:06.800 --> 09:11.240 to interpret QOS results or QOS configurations. 191 09:11.240 --> 09:14.750 And it all comes down to all of these class maps and policy maps and policing 192 09:14.750 --> 09:15.560 and shaping. 193 09:15.560 --> 09:18.080 I hope there's been informative for you and I'd like to thank you for viewing.