1 00:00:13,670 --> 00:00:15,080 So here's Robert a two. 2 00:00:20,270 --> 00:00:21,200 Showrun. 3 00:00:22,920 --> 00:00:27,540 No quality of service configuration has been configured on this router. 4 00:00:27,990 --> 00:00:31,890 Interface that we working on is serial 020. 5 00:00:35,790 --> 00:00:37,080 So rather to. 6 00:00:38,990 --> 00:00:39,980 CLOs map. 7 00:00:40,310 --> 00:00:44,030 We could use different names here, but I'm going to use the same names. 8 00:00:44,270 --> 00:00:46,100 We've got a class map for voice. 9 00:00:47,340 --> 00:00:47,640 Here. 10 00:00:47,640 --> 00:00:50,340 We need to match on dhcp. 11 00:00:50,370 --> 00:00:53,940 So match ip dhcp. 12 00:00:54,290 --> 00:01:01,260 F per these instructions, we're going to set the IP precedence to five, but that needs to be done 13 00:01:01,260 --> 00:01:02,430 in the policy map. 14 00:01:02,820 --> 00:01:04,709 Next class is http. 15 00:01:05,250 --> 00:01:15,720 So class map http match ip dhcp if 31. 16 00:01:17,590 --> 00:01:29,770 CLOs map icmp match IP DCP af 11 so rather two. 17 00:01:29,980 --> 00:01:33,340 We are matching DHCP values. 18 00:01:33,520 --> 00:01:35,890 We are not using end bar. 19 00:01:36,190 --> 00:01:42,070 We are going to read the DHCP values of packets received on the serial interface. 20 00:01:44,210 --> 00:01:53,420 And then we're going to do something with it such as remark the DHCP values sole trader policy map called 21 00:01:53,420 --> 00:01:54,440 remark. 22 00:01:54,590 --> 00:02:01,910 The first class that we're going to match is voice and we told to set the IP precedence to five. 23 00:02:02,150 --> 00:02:07,190 So set precedence and notice the words. 24 00:02:07,190 --> 00:02:13,760 We could either use the word critical or we could use a value such as five. 25 00:02:13,790 --> 00:02:15,950 So here I'm going to specify critical. 26 00:02:16,460 --> 00:02:17,900 But notice what happens. 27 00:02:17,900 --> 00:02:19,130 Do show run. 28 00:02:20,060 --> 00:02:23,420 It's been changed to the number five. 29 00:02:26,160 --> 00:02:30,450 So either will work, but in the output you'll see numbers. 30 00:02:30,960 --> 00:02:37,200 So you could either enter critical or five, but it gets converted to the number class. 31 00:02:38,620 --> 00:02:42,060 HTTP set precedence. 32 00:02:42,390 --> 00:02:45,600 And we've been told to set the precedence to three. 33 00:02:48,380 --> 00:02:50,630 Klaus ICMP. 34 00:02:50,960 --> 00:02:53,450 And are we going to set the precedents? 35 00:02:54,320 --> 00:02:56,690 To routine or zero. 36 00:02:57,860 --> 00:02:59,450 So again, show run. 37 00:03:00,620 --> 00:03:04,850 Here are our class maps matching different traffic types. 38 00:03:05,630 --> 00:03:07,190 Here's our policy map. 39 00:03:07,340 --> 00:03:10,790 Where we changing the DHCP values? 40 00:03:10,910 --> 00:03:18,290 In other words, we are rewriting the type of service field or toss field in the IP header and using 41 00:03:18,290 --> 00:03:20,960 precedence rather than DHCP values. 42 00:03:22,610 --> 00:03:26,210 Next step is to bind the policy map. 43 00:03:26,450 --> 00:03:29,240 So interface serial is 0 to 0. 44 00:03:30,560 --> 00:03:36,620 Service policy inbound or input in this case remark. 45 00:03:38,060 --> 00:03:41,330 So we've completed the configuration. 46 00:03:42,380 --> 00:03:44,090 There are our class maps. 47 00:03:44,120 --> 00:03:45,860 Here's our policy map. 48 00:03:47,980 --> 00:03:49,270 Scrolling down. 49 00:03:49,870 --> 00:03:54,580 Here's the service policy bound to the serial interface. 50 00:03:55,510 --> 00:03:57,670 I'll save the rudder configuration. 51 00:03:59,010 --> 00:04:05,550 So now that we've configured the routers, we need to verify that things are working as expected. 52 00:04:06,900 --> 00:04:10,560 Sun rata one show policy map enter. 53 00:04:13,130 --> 00:04:13,640 Yes. 54 00:04:13,640 --> 00:04:16,370 Our policy map called Mark. 55 00:04:17,519 --> 00:04:20,730 This is what we've configured on the policy. 56 00:04:21,510 --> 00:04:27,570 But let's look at the statistics of the policy on this interface. 57 00:04:28,530 --> 00:04:34,380 What you'll notice after the moment is there are no matches for voice. 58 00:04:35,130 --> 00:04:38,310 They are no matches for HTTP. 59 00:04:38,820 --> 00:04:41,070 They are no matches for ICMP. 60 00:04:43,550 --> 00:04:45,590 En route a to show policy map. 61 00:04:47,570 --> 00:04:48,890 There's our policy map. 62 00:04:50,210 --> 00:04:54,470 Let's look at the binding on serial 0 to 0. 63 00:04:54,980 --> 00:04:59,630 So this command shows us that there are no matches for voice. 64 00:04:59,660 --> 00:05:01,610 No matches for HTTP. 65 00:05:02,500 --> 00:05:04,460 No matches for ICMP. 66 00:05:05,150 --> 00:05:07,940 Default clause is seeing matches. 67 00:05:08,540 --> 00:05:09,680 Same over here. 68 00:05:09,680 --> 00:05:12,170 We've got matches on the default class. 69 00:05:12,440 --> 00:05:14,690 Default class matches. 70 00:05:14,690 --> 00:05:19,760 Anything that we've not specifically specified in our policy map. 71 00:05:19,910 --> 00:05:29,390 So in other words, OSPF routing updates would match the default policy because we haven't specified 72 00:05:29,570 --> 00:05:36,920 matching of OSPF in our policy map and any other traffic that's being used across the network would 73 00:05:36,920 --> 00:05:39,410 also match the default class. 74 00:05:41,610 --> 00:05:41,820 Okay. 75 00:05:41,820 --> 00:05:45,270 So let's send some traffic on PC one. 76 00:05:45,540 --> 00:05:50,370 Open up a web browser and open up a web browser to Cisco dot com. 77 00:05:51,000 --> 00:05:51,960 Click go. 78 00:05:52,230 --> 00:05:53,160 And there you go. 79 00:05:53,160 --> 00:05:56,070 We have connected to Cisco AECOM. 80 00:05:56,780 --> 00:05:57,590 On Rata one. 81 00:05:57,590 --> 00:06:01,550 Previously we had no matches for http traffic. 82 00:06:01,790 --> 00:06:03,620 Look at the policy again. 83 00:06:04,690 --> 00:06:07,630 Notice we are now getting matches for HDPE. 84 00:06:08,730 --> 00:06:10,410 Go to Facebook.com. 85 00:06:14,970 --> 00:06:16,290 Should policy map. 86 00:06:18,710 --> 00:06:23,600 The number of matches has increased from the previous show command. 87 00:06:24,380 --> 00:06:27,770 Previously we had 72 packets match the class. 88 00:06:29,640 --> 00:06:33,690 Now we have 140 packets that match the class. 89 00:06:35,370 --> 00:06:35,880 Click. 90 00:06:35,910 --> 00:06:37,020 Go again. 91 00:06:38,790 --> 00:06:41,970 Notice we now have 206 packet matches. 92 00:06:43,090 --> 00:06:44,470 On, wrote a two. 93 00:06:45,420 --> 00:06:48,990 Show Policy Map interface serial 020. 94 00:06:49,350 --> 00:06:54,330 Notice we've got matches on HTTP, but no matches on ICMP. 95 00:06:55,250 --> 00:06:57,560 Open up a web browser on PC to. 96 00:06:59,880 --> 00:07:01,410 Go to Cisco dot com. 97 00:07:04,030 --> 00:07:04,860 En route to. 98 00:07:04,870 --> 00:07:08,230 We previously had 206 matches. 99 00:07:08,410 --> 00:07:10,990 Now we've got 275 matches. 100 00:07:13,400 --> 00:07:16,220 Go to Facebook dot com. 101 00:07:19,870 --> 00:07:22,660 Now we have 341 matches. 102 00:07:23,200 --> 00:07:27,370 So the policy map is working on both Rider one and Rider two. 103 00:07:27,640 --> 00:07:30,070 We are matching HTTP traffic. 104 00:07:30,780 --> 00:07:32,760 Back on rata one. 105 00:07:35,780 --> 00:07:42,830 Open up a command prompt and I'll ping Cisco dot com before I press enter. 106 00:07:44,920 --> 00:07:46,000 On to one. 107 00:07:48,290 --> 00:07:50,990 They are no matches on ICMP traffic. 108 00:07:52,900 --> 00:07:57,130 En route to no matches on ICMP traffic. 109 00:07:59,160 --> 00:08:00,240 Presenter. 110 00:08:02,360 --> 00:08:05,150 Look at the policy map on rather one again. 111 00:08:05,690 --> 00:08:08,000 Notice we can see three packet matches. 112 00:08:08,480 --> 00:08:11,540 Rather two four packet matches. 113 00:08:11,810 --> 00:08:13,190 Go back to write a one. 114 00:08:15,680 --> 00:08:17,150 Full packet matches. 115 00:08:18,480 --> 00:08:24,180 Do something similar on PC to ping facebook.com. 116 00:08:26,130 --> 00:08:29,490 En route a18 packet matches. 117 00:08:30,690 --> 00:08:34,530 Wrote a28 packet matches. 118 00:08:35,230 --> 00:08:40,000 So the quality of service policies are working for ICMP traffic as well.