WEBVTT 1 00:00.000 --> 00:04.600 This lab challenge is really fun. I think it's really cool to be able to 2 00:04.600 --> 00:09.300 configure a policy map, apply it to an interface, and then check it. Actually 3 00:09.300 --> 00:14.120 see the traffic that's showing up on our interfaces. So if you happen to get 4 00:14.120 --> 00:18.280 stuck, you can follow along in this video or we have the lab script below that 5 00:18.280 --> 00:21.640 would serve as the solution. But if you haven't yet done so, be sure to take 6 00:21.640 --> 00:21.800 the 7 00:21.800 --> 00:26.160 time to fire up the lab and give this a go because some of the best ways to 8 00:26.160 --> 00:30.600 really drive home configuration is to actually put your hands on the CLI and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:26.160 --> 00:30.600 really drive home configuration is to actually put your hands on the CLI and 9 00:30.600 --> 00:35.720 do that configuration. So we're gonna go through this process here and we're 10 00:35.720 --> 00:39.960 going to start with, let's see here. So the challenge ultimately is to get us 11 00:39.960 --> 00:40.600 to 12 00:40.600 --> 00:45.320 deliver some traffic to router 2 and make sure that it's sliding in. We also 13 00:45.320 --> 00:50.200 want to do some weighted random early detect configuration. So on router 1 we 14 00:50.200 --> 00:50.320 're 15 00:50.320 --> 00:55.680 going to get our priority queue and AF2X queue set up. So I'm gonna get my 16 00:55.680 --> 00:56.320 class 17 00:56.320 --> 01:01.760 map and generally speaking with, well if we only have one tag it doesn't really WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 17 00:56.320 --> 01:01.760 map and generally speaking with, well if we only have one tag it doesn't really 18 01:01.760 --> 01:04.800 matter but generally speaking we probably want to do a match any here. So 19 01:04.800 --> 01:11.800 we do class map, match any DSCP, EF, and then match DSCP, EF. I'm gonna do the 20 01:11.800 --> 01:11.960 same 21 01:11.960 --> 01:20.240 thing this time matching AF2X and we'll match all of those AF2Xs. So AF2X 22 01:20.240 --> 01:25.260 AF2X, AF2X, AF2X, AF2X, AF2X. And this is where match any really matters is 23 01:25.260 --> 01:26.000 with a 24 01:26.000 --> 01:30.120 queue with multiple tags. So we're gonna keep it simple and just have two WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 01:26.000 --> 01:30.120 queue with multiple tags. So we're gonna keep it simple and just have two 25 01:30.120 --> 01:30.920 different 26 01:30.920 --> 01:34.760 queues so we're gonna now create a policy map. I'm gonna call this one red 27 01:34.760 --> 01:40.260 just because we're double you red I suppose either way that's the focus here. 28 01:40.260 --> 01:45.640 I'm gonna get on to my one class so I'm gonna do class let's see here which are 29 01:45.640 --> 01:52.620 we doing. We are going to do just the EF first and get the priority statement. 30 01:52.620 --> 01:52.680 So 31 01:52.680 --> 01:58.760 we said we want 100 mag that's 100,000 kilobits per second and then we're gonna 32 01:58.760 --> 02:06.150 get on to our AF2X and we were told to configure the of the rest of the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 01:58.760 --> 02:06.150 get on to our AF2X and we were told to configure the of the rest of the 33 02:06.150 --> 02:06.480 bandwidth 34 02:06.480 --> 02:10.600 we want to give 75% to this queue. Well, so maybe the last 25 would go to class 35 02:10.600 --> 02:10.960 default. 36 02:10.960 --> 02:16.320 So I'm gonna use this bandwidth remaining percent command and I'm gonna say 37 02:16.320 --> 02:21.470 remaining percent 75. Next up we want to configure weighted random early detect 38 02:21.470 --> 02:21.480 . 39 02:21.480 --> 02:27.080 So I'm gonna do this random detect DSCP based we have to enable it first and 40 02:27.080 --> 02:32.520 then I can start to configure my queues. So we're going off of the concept of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 02:27.080 --> 02:32.520 then I can start to configure my queues. So we're going off of the concept of 41 02:32.520 --> 02:32.720 the 42 02:32.720 --> 02:40.400 the queue length being 40 and so I'm going to add on here DSCP AF 23 and we 43 02:40.400 --> 02:40.400 were 44 02:40.400 --> 02:48.280 told to create a queue that's based on it being 50% full dropping 20% of the 45 02:48.280 --> 02:52.360 traffic when it gets to 70% full. So we got to do a little bit of math here 46 02:52.360 --> 02:52.880 again 47 02:52.880 --> 02:58.040 if we're at 50% of 40 packets that would be 20 and then we're gonna go all the 48 02:58.040 --> 02:58.120 way 49 02:58.120 --> 03:03.920 up to 28 which is 70% and if we're at dropping one out of five packets that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 02:58.120 --> 03:03.920 up to 28 which is 70% and if we're at dropping one out of five packets that's 50 03:03.920 --> 03:09.640 20% the denominator is five. So we're gonna hit enter there and then we'll do 51 03:09.640 --> 03:20.200 random detect AF 22. Now we're talking about 60 to 80% so 60% is 24, 80% is 32 52 03:20.200 --> 03:27.400 and we want a one-third so that'd be 1 over 3 which means we need a 3 here and 53 03:27.400 --> 03:35.600 then random detect a DSCP AF 21 and here we're going to go from 75% which is 30 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 03:27.400 --> 03:35.600 then random detect a DSCP AF 21 and here we're going to go from 75% which is 30 54 03:35.600 --> 03:42.680 to 100% which is 40 and up to a 50% drop probability at the end which is 1 55 03:42.680 --> 03:46.080 over 2. So that would be our random detect configuration we're gonna get on 56 03:46.080 --> 03:52.600 to an interface here and gig 00 and do notice here if we do a show int gig 00 57 03:52.600 --> 03:58.160 actually let's see here so we've got our queuing strategy is FIFO so by default 58 03:58.160 --> 04:04.560 in our queue size is 40 here which is what we were expecting so if I add so WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 03:58.160 --> 04:04.560 in our queue size is 40 here which is what we were expecting so if I add so 59 04:04.560 --> 04:09.640 let's see here so we'll do a service policy and we called that red and we 60 04:09.640 --> 04:14.800 need to do it in the outbound direction so output red if I do that same command 61 04:14.800 --> 04:18.240 now that's been applied we'll see a couple of things first of all we're now 62 04:18.240 --> 04:21.640 running class-based queuing second of all notice on this platform it actually 63 04:21.640 --> 04:25.040 increases the output queue size to a thousand so that's something they keep 64 04:25.040 --> 04:27.880 in mind in a real-world scenario we're gonna keep operating under the 65 04:27.880 --> 04:32.560 assumption that this is a 40 length but because we've applied class-based WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 65 04:27.880 --> 04:32.560 assumption that this is a 40 length but because we've applied class-based 66 04:32.560 --> 04:38.320 queuing it has increased the queue size to have a thousand in there so it's 67 04:38.320 --> 04:43.080 something we absolutely need to pay attention to now from here that's that's 68 04:43.080 --> 04:49.960 it for our first section if I do a show policy map interface gig 00 we see that 69 04:49.960 --> 04:55.680 we've got our weighted random early detect configuration here as well as 70 04:55.680 --> 05:00.800 we're now able to start tracking our packets that are coming in now what we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 04:55.680 --> 05:00.800 we're now able to start tracking our packets that are coming in now what we 71 05:00.800 --> 05:04.960 want to do is shift gears and we want to make sure that our policy maps are 72 05:04.960 --> 05:09.680 working along with the queues as we think and so what we're gonna do is we're 73 05:09.680 --> 05:13.720 gonna send packets over to router 2 that have a DSCP tag and make sure 74 05:13.720 --> 05:18.680 they're showing up correctly so you do a config T here do a class map DSCP 75 05:18.680 --> 05:27.000 E F and match that DSCP and then also here class map we've got to do the 76 05:27.000 --> 05:36.560 match any on this one and then match DSCP AF 21 AF 22 AF 23 okay so now we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 76 05:27.000 --> 05:36.560 match any on this one and then match DSCP AF 21 AF 22 AF 23 okay so now we're 77 05:36.560 --> 05:40.200 going to apply this to a policy map on an interface I'm gonna say policy map I 78 05:40.200 --> 05:40.240 'm 79 05:40.240 --> 05:43.400 just gonna call this monitor because we're gonna monitor traffic using it and 80 05:43.400 --> 05:47.200 I'm gonna add the classes but we're not gonna have any policy we don't actually 81 05:47.200 --> 05:52.000 need policy on this because we're just going to use it to track how things are 82 05:52.000 --> 05:57.760 going so you get onto the interface apply this with service policy input notice 83 05:57.760 --> 06:03.680 input monitor all right so what are we trying to accomplish here what we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 83 05:57.760 --> 06:03.680 input monitor all right so what are we trying to accomplish here what we're 84 06:03.680 --> 06:07.640 trying to say is we've got a router router one and this is going through a 85 06:07.640 --> 06:12.760 switch here in the middle switch one and router two so what I want to do is I 86 06:12.760 --> 06:18.040 want to send traffic marked with like AF 21 here and by marking the traffic we 87 06:18.040 --> 06:26.240 have applied a policy map here that has three queues so we've got our EF Q our 88 06:26.240 --> 06:33.680 AF to X Q and then our class default Q down here so what we're gonna do is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 88 06:26.240 --> 06:33.680 AF to X Q and then our class default Q down here so what we're gonna do is 89 06:33.680 --> 06:38.000 because this is on input we're not gonna apply policy on input we're just going 90 06:38.000 --> 06:43.680 to monitor this we're gonna run show commands to make sure that packets are 91 06:43.680 --> 06:48.440 showing up if I send an AF 21 packet from router one I expect it to land in 92 06:48.440 --> 06:53.960 the middle queue there now quick note a lot of platforms allow me to just say 93 06:53.960 --> 07:00.160 ping and this is I believe 10 dot 12 dot 0 dot 2 over here and then I could WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 06:53.960 --> 07:00.160 ping and this is I believe 10 dot 12 dot 0 dot 2 over here and then I could 94 07:00.160 --> 07:06.520 actually specify a tag so I could say something like DSCP AF 21 well in our 95 07:06.520 --> 07:10.080 lab environment this platform doesn't allow us to do that so we're going to 96 07:10.080 --> 07:16.520 specify TOS the TOS is a one byte field and so we're going to need to know 97 07:16.520 --> 07:23.000 what exactly we're going to mark it with and so how do we go about doing this 98 07:23.000 --> 07:30.640 well let's pay attention to what AF 21 is AF 21 is saying that I've got three WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 98 07:23.000 --> 07:30.640 well let's pay attention to what AF 21 is AF 21 is saying that I've got three 99 07:30.640 --> 07:35.790 bytes here and our three bits rather and then another three bits and then two 100 07:35.790 --> 07:36.000 bits 101 07:36.000 --> 07:42.920 in the type of service so this first three bits would be the two two is 0 1 0 102 07:42.920 --> 07:47.640 the second three bits this last one with the shirt forwarding is always a 0 and 103 07:47.640 --> 07:54.050 so the other digit is a one so I say 0 1 here and then these last two are can 104 07:54.050 --> 07:54.120 be 105 07:54.120 --> 07:59.240 anything ultimately but we're just gonna leave it as a 0 set of 0s because of 106 07:59.240 --> 08:05.630 this we are now going to need to translate this into a decimal value that we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 106 07:59.240 --> 08:05.630 this we are now going to need to translate this into a decimal value that we 107 08:05.630 --> 08:05.920 send 108 08:05.920 --> 08:13.360 so if this is the that's the 8 so that's an 8 and this is the 64's 64 plus 8 109 08:13.360 --> 08:20.040 this would be 72 so this command is going to send this in the type of service 110 08:20.040 --> 08:27.040 field which ultimately translates to AF 21 because of the bits being here and 111 08:27.040 --> 08:33.720 these two bits here so if any of that is a little bit off-putting then we just WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 111 08:27.040 --> 08:33.720 these two bits here so if any of that is a little bit off-putting then we just 112 08:33.720 --> 08:38.320 covered this in a great amount of detail just a few skills ago so make sure to 113 08:38.320 --> 08:41.680 go back and review that if necessary but that is what we're trying to 114 08:41.680 --> 08:49.440 accomplish here so if I do a show policy map interface gig 1 0 I can see 115 08:49.440 --> 08:55.720 that I've got my cues here as defined EF 2x and we see we've got zero packets 116 08:55.720 --> 09:02.040 on the AF 2x so if I come back to router 1 I say ping 10 dot 12 dot 0 dot 2 and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 116 08:55.720 --> 09:02.040 on the AF 2x so if I come back to router 1 I say ping 10 dot 12 dot 0 dot 2 and 117 09:02.040 --> 09:02.160 I 118 09:02.160 --> 09:07.960 can do this a few times I go back to router 2 I run this command again and 119 09:07.960 --> 09:13.480 still zero packets in these cues well that's what we expect because we're just 120 09:13.480 --> 09:17.240 pinging normally but we see a lot of packets racking up here in the class 121 09:17.240 --> 09:21.480 default which is the catch-all and it's going to receive packets with a default 122 09:21.480 --> 09:28.760 tag of zero well what if now I add that TOS and we said 72 so I'm going to ping 123 09:28.760 --> 09:33.480 and let's just do two batches of ping so that was 10 packets I just sent go WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 123 09:28.760 --> 09:33.480 and let's just do two batches of ping so that was 10 packets I just sent go 124 09:33.480 --> 09:33.640 back 125 09:33.640 --> 09:40.200 to router 2 take a look at it look at that 10 packets have arrived inside of 126 09:40.200 --> 09:40.400 our 127 09:40.400 --> 09:48.520 AF 2x that's pretty cool I love that and so we're going to we're just going to 128 09:48.520 --> 09:54.400 be able to use policy maps to be able to look at traffic and again make sure 129 09:54.400 --> 09:58.760 using this command that traffic is showing up in the queue where we think 130 09:58.760 --> 10:02.360 it's supposed to show up so that's why I said this is really fun lab be sure to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 130 09:58.760 --> 10:02.360 it's supposed to show up so that's why I said this is really fun lab be sure to 131 10:02.360 --> 10:05.120 go through this if you haven't already done so and if you have just always 132 10:05.120 --> 10:09.840 remember the power of the show policy map interface command tell us a lot of 133 10:09.840 --> 10:14.320 what's going on it shows us our weighted red configuration and it also shows us 134 10:14.320 --> 10:18.560 the packet count that's showing up in a particular queue I hope there's been 135 10:18.560 --> 10:22.520 informative for you and I'd like to thank you for viewing