1 00:00:13,590 --> 00:00:19,860 In Packet Trace, I'm going to start simulation mode and then on PC one, I'm going to open up a web 2 00:00:19,860 --> 00:00:23,490 browser and go to Cisco dot com. 3 00:00:25,210 --> 00:00:32,920 Now the first thing the PC needs to do is determine the IP address of Cisco dot com. 4 00:00:34,710 --> 00:00:40,590 So it's going to send out a DNS request message for Cisco dot com. 5 00:00:40,740 --> 00:00:46,740 So scrolling down here, notice we've got a DNS query for Cisco dot com. 6 00:00:47,570 --> 00:00:51,530 Capture forward or that gets sent to the rotor. 7 00:00:53,580 --> 00:00:55,590 When it gets sent across. 8 00:00:57,370 --> 00:00:58,690 The serial link. 9 00:00:59,050 --> 00:01:02,020 Notice the DHCP is set to zero. 10 00:01:02,680 --> 00:01:06,040 No quality of service is applied to this packet. 11 00:01:07,450 --> 00:01:10,180 So that will go to the DNS server. 12 00:01:13,130 --> 00:01:15,500 DNS server will reply back. 13 00:01:18,760 --> 00:01:21,250 Packet will go back to the PC. 14 00:01:22,390 --> 00:01:24,790 And now the peace he can send. 15 00:01:26,800 --> 00:01:29,920 TCP traffic to the router. 16 00:01:31,700 --> 00:01:34,280 PC is going through the three way handshake. 17 00:01:36,010 --> 00:01:36,490 Notice. 18 00:01:36,490 --> 00:01:38,590 Now we get HTTP traffic. 19 00:01:41,330 --> 00:01:45,650 Notice on inbound HTTP traffic. 20 00:01:46,430 --> 00:01:53,600 In this case we've got an HTTP request, doesn't have DHCP markings, but on outbound. 21 00:01:55,070 --> 00:01:56,150 Out of the water. 22 00:01:56,180 --> 00:02:00,020 The DCP is set to capture forward. 23 00:02:00,020 --> 00:02:03,680 Notice how this packet has a little square here. 24 00:02:04,500 --> 00:02:06,630 Showing us that. 25 00:02:08,490 --> 00:02:11,160 DHCP was set on ingress. 26 00:02:11,730 --> 00:02:14,370 DHCP is also set on egress. 27 00:02:15,040 --> 00:02:16,600 So capture forward. 28 00:02:17,260 --> 00:02:21,160 What you'll notice is we have this little square. 29 00:02:24,640 --> 00:02:29,710 To indicate that a quality of service of value has been specified on the packet. 30 00:02:30,660 --> 00:02:34,470 Inbound and outbound shows us the DHCP marking. 31 00:02:37,750 --> 00:02:39,040 On the return. 32 00:02:39,340 --> 00:02:47,050 No quality of service has been applied because we applied to the policy inbound on this interface and 33 00:02:47,050 --> 00:02:48,760 outbound on this interface. 34 00:02:49,270 --> 00:02:55,480 So on right of one notice, no quality of service is configured on the packet. 35 00:02:55,690 --> 00:03:00,580 You have to think about your direction when configuring quality of service. 36 00:03:02,130 --> 00:03:04,410 No quality of service is configured here. 37 00:03:07,070 --> 00:03:08,810 But notice on this packet. 38 00:03:10,220 --> 00:03:12,230 Going from the inside PC to the outside. 39 00:03:12,230 --> 00:03:20,660 PC ingress has no DHCP egress, however, does have a DHCP marking configured. 40 00:03:23,220 --> 00:03:25,740 So quality of service has been configured. 41 00:03:27,390 --> 00:03:31,530 Ingress en route to and egress en route to. 42 00:03:35,280 --> 00:03:42,330 So that was HDPE or let's try the same thing using ICMP. 43 00:03:42,750 --> 00:03:44,700 So ping cisco dot com. 44 00:03:45,120 --> 00:03:46,980 I'll put this to simulation mode. 45 00:03:48,770 --> 00:03:49,760 Presenter. 46 00:03:50,550 --> 00:03:52,290 Notice we have a dense. 47 00:03:53,330 --> 00:03:54,290 Message. 48 00:03:56,020 --> 00:03:59,230 No quality of service is applied. 49 00:04:00,600 --> 00:04:01,860 On this packet. 50 00:04:03,020 --> 00:04:07,940 So the package received from writer one doesn't have the DHCP configured and right. 51 00:04:07,940 --> 00:04:12,050 A two is not setting DHCP on egress. 52 00:04:13,340 --> 00:04:14,870 Because back to the PC. 53 00:04:14,910 --> 00:04:17,120 Here's our ICMP message. 54 00:04:17,810 --> 00:04:20,240 Notice inbound. 55 00:04:20,870 --> 00:04:24,800 No DCP marking, but outbound out of the router. 56 00:04:24,800 --> 00:04:26,810 We do have a DHCP marking. 57 00:04:29,630 --> 00:04:31,460 And you can see the color here. 58 00:04:31,490 --> 00:04:34,910 Notice the little pink square inbound. 59 00:04:34,910 --> 00:04:38,270 We've got this DCP marking outbound. 60 00:04:38,420 --> 00:04:40,730 We don't have a DHCP marking. 61 00:04:41,120 --> 00:04:45,410 And that's because we configured the router to reset. 62 00:04:47,520 --> 00:04:52,560 The TCP IP precedence of value to zero on egress. 63 00:04:52,560 --> 00:04:55,830 So this is set to zero ingress. 64 00:04:56,520 --> 00:04:58,440 A DHCP value is configured. 65 00:04:59,280 --> 00:05:01,440 Now these values can be difficult to read. 66 00:05:01,440 --> 00:05:08,520 Remember, the type of service field is eight bits in length, so you'd have to convert this into your 67 00:05:08,670 --> 00:05:11,520 DCP value of AFI 11. 68 00:05:11,940 --> 00:05:18,030 AFI 11 has a decimal value of ten or hexadecimal value of A. 69 00:05:18,210 --> 00:05:25,980 You can get details of all those calculations in my CCNA course, or you can have a look online capture 70 00:05:25,980 --> 00:05:29,070 forward for that ICMP packet. 71 00:05:29,580 --> 00:05:36,990 There is no DHCP value, no precedence value because we reset it to zero. 72 00:05:41,320 --> 00:05:44,230 Let's do something similar with PC two. 73 00:05:45,520 --> 00:05:48,940 So in PC two, I'll ping facebook.com. 74 00:05:50,630 --> 00:05:52,820 First packet generated as dense. 75 00:05:54,010 --> 00:05:54,700 Dennis. 76 00:05:57,030 --> 00:05:59,760 Will not have DHCP values configured. 77 00:06:00,590 --> 00:06:03,230 Because we didn't configure that in our policy. 78 00:06:04,110 --> 00:06:14,700 But notice now when an ICMP packet hits router one ingress, DHCP zero egress or outbound, the DHCP 79 00:06:14,700 --> 00:06:19,950 value has been configured capture forward when it gets to router two. 80 00:06:21,580 --> 00:06:29,560 Ingress of value is thus a grace of value is set to zero because we overrode it once again. 81 00:06:30,750 --> 00:06:34,160 Let's do something similar with HTTP. 82 00:06:34,930 --> 00:06:36,430 So on PC two. 83 00:06:37,540 --> 00:06:38,950 Open up a web browser. 84 00:06:39,340 --> 00:06:41,470 Go to Facebook.com. 85 00:06:42,490 --> 00:06:44,740 First packet generated as dense. 86 00:06:47,490 --> 00:06:50,730 No quality of service is configured on this packet again. 87 00:06:53,360 --> 00:06:54,140 But. 88 00:06:56,210 --> 00:06:59,720 When we get the HTTP packet. 89 00:07:00,480 --> 00:07:08,760 From PC to the DHCP value is configured accordingly to one a which is a 31. 90 00:07:10,200 --> 00:07:13,050 When it gets to right to. 91 00:07:13,880 --> 00:07:25,650 Ingress is dhcp 0x1a egress is dhcp 0x18 and that's forwarded into the internet. 92 00:07:25,670 --> 00:07:31,730 Not that the internet would do anything with the quality of service markings. 93 00:07:32,850 --> 00:07:38,850 But The Slap shows you how to configure quality of service markings in packet tracer. 94 00:07:39,120 --> 00:07:41,400 So were you able to complete the lab? 95 00:07:41,550 --> 00:07:45,330 Were you able to configure quality of service in your network? 96 00:07:45,630 --> 00:07:48,180 Did you prove that it worked correctly?