1 00:00:13,460 --> 00:00:15,230 In the package tracer lab. 2 00:00:15,260 --> 00:00:19,850 You need to configure quality of service or quads or chaos. 3 00:00:20,480 --> 00:00:27,530 In this lab, we're going to cover quality of service topics such as matching traffic, marking traffic, 4 00:00:27,740 --> 00:00:32,870 doing something with the traffic, such as providing a minimum bandwidth guarantee. 5 00:00:33,940 --> 00:00:38,620 Now, in the real world, you would follow a quality of service policy document. 6 00:00:38,630 --> 00:00:45,020 In other words, you would decide which traffic types are important in your network and then allocate 7 00:00:45,020 --> 00:00:52,820 bandwidth accordingly, or implement quality of service mechanisms such as policing, shaping, queuing 8 00:00:52,820 --> 00:00:53,450 and others. 9 00:00:53,450 --> 00:00:59,690 Based on your quality of service policy document in this lab, we're going to implement a basic quality 10 00:00:59,690 --> 00:01:06,740 of service policy so that you can get familiar with class maps, policy maps, service policies and 11 00:01:06,740 --> 00:01:11,540 other commands used for quality of service in Cisco environments. 12 00:01:12,370 --> 00:01:17,650 On another one, you're going to match traffic using end bar or network based application recognition, 13 00:01:17,830 --> 00:01:25,050 and then you're going to mark the traffic with DHCP values or differentiated services code point values. 14 00:01:25,060 --> 00:01:29,410 In addition, you're going to use queuing on the egress interface. 15 00:01:29,410 --> 00:01:37,270 In other words, on Serial 010 to prioritize voice traffic over other traffic types, voice traffic 16 00:01:37,270 --> 00:01:39,370 will be in a priority queue. 17 00:01:39,820 --> 00:01:44,770 HTTP and ICMP traffic will be given a minimum bandwidth guarantee. 18 00:01:45,520 --> 00:01:50,500 You need to do configuration on both router one and rider two on router one. 19 00:01:50,500 --> 00:01:52,420 You firstly need to match a traffic. 20 00:01:52,450 --> 00:01:59,200 You need to match a voice traffic using end bar and specifically RTP traffic or real time protocol. 21 00:01:59,680 --> 00:02:06,880 You need to set the DHCP to F for matched packets so you're going to match a voice traffic using end 22 00:02:06,880 --> 00:02:13,930 bar and then mark the packets using DHCP and set the marking to expedite it forwarding. 23 00:02:13,930 --> 00:02:23,050 Or if you need to match HTTP traffic using end bar and set the DHCP to AF 31 or should forwarding class 24 00:02:23,080 --> 00:02:30,430 AF 31 ICMP traffic should be matched using end bar and you need to set the DHCP to AF 11. 25 00:02:30,880 --> 00:02:37,660 When traffic leaves the router, you need to prioritize voice traffic, so you need to create an egress 26 00:02:37,660 --> 00:02:46,300 or outbound quality of service policy on serial 010 that prioritizes voice traffic. 27 00:02:46,630 --> 00:02:51,730 So we're going to configure a priority queue of 100 kilobits per second. 28 00:02:52,030 --> 00:03:00,520 But in addition, you need to provide a minimum bandwidth of 50 kilobits per second to HTTP and 25 kilobits 29 00:03:00,520 --> 00:03:02,440 per second to ICMP. 30 00:03:02,770 --> 00:03:10,300 In other words, on this interface you're going to implement low latency queuing or priority queue cross 31 00:03:10,300 --> 00:03:11,890 based waited for queuing. 32 00:03:12,220 --> 00:03:16,270 Now don't worry too much about the figures used here. 33 00:03:16,570 --> 00:03:17,800 This is a lab. 34 00:03:17,800 --> 00:03:18,970 In the real world. 35 00:03:18,970 --> 00:03:25,660 You would allocate specific figures based on your traffic types and the bandwidth you have available. 36 00:03:26,140 --> 00:03:31,900 So as an example, if you had a gigabit interface or 100 megabits per second interface, you would adjust 37 00:03:31,900 --> 00:03:33,370 a values accordingly. 38 00:03:33,760 --> 00:03:39,400 In this lab, I simply want you to understand the mechanisms used for quality of service. 39 00:03:39,460 --> 00:03:45,760 I want you to be able to configure and implement quality of service policies on routers and ensure that 40 00:03:45,760 --> 00:03:51,280 you understand both the theory and practical side of quality of service. 41 00:03:51,640 --> 00:04:01,390 Now on router to ingress or inbound on serial 020, you need to match voice traffic by matching dhcp 42 00:04:01,400 --> 00:04:07,420 CEF and then you need to remark the traffic with an IP precedence of five. 43 00:04:07,540 --> 00:04:15,910 You need to match HTTP traffic by matching DHCP 31 and then setting the IP precedence to three. 44 00:04:16,329 --> 00:04:22,180 You should also match DHCP RF 11 and set the precedence to zero. 45 00:04:22,540 --> 00:04:31,570 Again, see this as an exercise in learning how quality of service works and the mechanisms used for 46 00:04:31,570 --> 00:04:32,980 best practices. 47 00:04:33,220 --> 00:04:38,710 Have a look at Cisco documentation such as the quality of service solution Reference Network Design 48 00:04:38,710 --> 00:04:41,100 Guide or R&D guide available on Cisco. 49 00:04:41,290 --> 00:04:41,890 Com. 50 00:04:42,550 --> 00:04:50,120 Again, you need to bind that policy inbound on serial 020 on router two now for verification. 51 00:04:50,140 --> 00:04:56,410 Open up a browser on PC one and PC two and browse to Cisco dot com and Facebook.com. 52 00:04:57,060 --> 00:05:04,020 In other words, on these PCs, browse to websites on the Internet and verify that you see matches in 53 00:05:04,020 --> 00:05:07,440 your policy on both router one and router two. 54 00:05:09,120 --> 00:05:15,150 Ping Cisco dot com from PC one and PC two and verify that you see matches in your policy. 55 00:05:15,300 --> 00:05:21,060 Now, in this example, we haven't got an IP phone, so we won't be able to simulate IP traffic. 56 00:05:21,300 --> 00:05:28,920 But by sending both HTTP and ICMP traffic, you'll be able to see matches in real time on your quality 57 00:05:28,920 --> 00:05:30,210 of service policies. 58 00:05:30,810 --> 00:05:38,760 Once you've done to that use simulation mode in packet tracer and send both ICMP and HTTP traffic into 59 00:05:38,760 --> 00:05:46,200 the network and verify that you see the markings on the packets on both the serial interface as well 60 00:05:46,200 --> 00:05:47,740 as the interface. 61 00:05:47,760 --> 00:05:56,700 In other words, you should see that your HTTP traffic has a DHCP of a 31 on the serial interface and 62 00:05:56,700 --> 00:06:00,270 IP precedence three on this Ethernet interface. 63 00:06:00,690 --> 00:06:02,730 So can you complete this lab? 64 00:06:02,940 --> 00:06:08,110 Download the attached packet, trace a file and see if you can complete the lab yourself. 65 00:06:08,130 --> 00:06:11,610 Otherwise, watch the next video where I complete the lab.