All language subtitles for Free-CCNA-QoS-Day-47-Lab-CCNA-200-301-Complete-Course_en

af Afrikaans
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian
ca Catalan
ceb Cebuano
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
tl Filipino
fi Finnish
fr French
fy Frisian
gl Galician
ka Georgian
de German
el Greek
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
km Khmer
ko Korean
ku Kurdish (Kurmanji)
ky Kyrgyz
lo Lao
la Latin
lv Latvian
lt Lithuanian
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mn Mongolian
my Myanmar (Burmese)
ne Nepali
no Norwegian
ps Pashto
fa Persian
pl Polish
pt Portuguese
pa Punjabi
ro Romanian
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
st Sesotho
sn Shona
sd Sindhi
si Sinhala
sk Slovak
sl Slovenian
so Somali
es Spanish
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
te Telugu
th Thai
tr Turkish
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
or Odia (Oriya)
rw Kinyarwanda
tk Turkmen
tt Tatar
ug Uyghur
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:03,419 --> 00:00:06,839 This is a free, complete course for the CCNA. 2 00:00:06,839 --> 00:00:10,599 If you like these videos, please subscribe\n 3 00:00:10,599 --> 00:00:15,269 Also, please like and leave a comment, and\n 4 00:00:17,899 --> 00:00:21,799 Also, remember to sign up via the link in\n 5 00:00:21,800 --> 00:00:26,670 for this course, so you can try it out yourself\n 6 00:00:26,670 --> 00:00:30,960 If you want more labs like these, I highly\n 7 00:00:32,128 --> 00:00:36,390 It’s a network simulator with tons of guided\n 8 00:00:38,689 --> 00:00:42,640 Click the link in the video description to\ncheck it out. 9 00:00:42,640 --> 00:00:47,390 In this lab we’ll do some basic QoS configurations\non R1. 10 00:00:47,390 --> 00:00:52,999 The design and configuration of QoS isn’t\n 11 00:00:52,999 --> 00:00:56,100 have to worry about remembering these configurations\nfor now. 12 00:00:56,100 --> 00:01:01,149 But I think doing some basic configurations\n 13 00:01:03,749 --> 00:01:08,340 In this network we have PC1 connected to R1\nvia SW1. 14 00:01:08,340 --> 00:01:13,180 On the other side there is SRV1 connected\nto R2 via SW2. 15 00:01:13,180 --> 00:01:17,820 Although I’ve only shown 1 PC, let’s say\n 16 00:01:19,609 --> 00:01:25,609 So, we will configure QoS on R1 to ensure\n 17 00:01:26,849 --> 00:01:33,609 We will mark HTTPS traffic as AF31 and ensure\n 18 00:01:35,650 --> 00:01:42,109 We will mark HTTP traffic as AF32 and ensure\n 19 00:01:42,109 --> 00:01:44,310 it will not be in a priority queue. 20 00:01:44,310 --> 00:01:50,750 We will mark ICMP traffic as CS2 and ensure\n 21 00:01:50,750 --> 00:01:56,370 Now, the actual QoS design of a network depends\n 22 00:01:56,370 --> 00:02:02,140 Which traffic needs to be prioritized, how\n 23 00:02:02,140 --> 00:02:06,569 These values I selected are honestly just\n 24 00:02:08,060 --> 00:02:13,699 Giving HTTPS traffic a priority queue, for\n 25 00:02:13,699 --> 00:02:16,709 Usually priority queues are used for voice\ntraffic. 26 00:02:16,710 --> 00:02:21,670 Anyway, after configuring the QoS rules we\n 27 00:02:25,039 --> 00:02:31,609 So, when R1 forwards traffic out of G0/0/0\n 28 00:02:33,259 --> 00:02:37,689 Now, once the traffic reaches R2 that’s\na different story. 29 00:02:37,689 --> 00:02:42,810 Even if R1 marks the packets as high priority,\n 30 00:02:42,810 --> 00:02:47,479 packets as high priority, it will treat them\nall equally. 31 00:02:47,479 --> 00:02:52,929 In the CCNA exam topics, it is stated that\n 32 00:02:55,069 --> 00:02:58,229 Well, this is the per hop behavior. 33 00:02:58,229 --> 00:03:04,489 We configure QoS on R1 and it will prioritize\n 34 00:03:04,490 --> 00:03:11,209 but then how R2 prioritizes traffic over the\n 35 00:03:11,209 --> 00:03:15,569 You can’t just configure one router to prioritize\n 36 00:03:15,568 --> 00:03:18,189 the network to also prioritize it. 37 00:03:18,189 --> 00:03:22,050 You have to configure QoS all across the network,\n 38 00:03:22,050 --> 00:03:26,439 Okay, I just wanted to make that clear since\n 39 00:03:29,400 --> 00:03:34,879 To show you the basic QoS configurations,\n 40 00:03:34,879 --> 00:03:38,729 Before configuration, though, let me show\n 41 00:03:42,469 --> 00:03:47,550 First, let me try to ping jeremysitlab.com. 42 00:03:48,759 --> 00:03:57,629 So, PC1 will send a DNS query to its DNS server,\n 43 00:03:57,629 --> 00:04:04,739 learn the IP address of jeremysitlab.com,\n 44 00:04:07,650 --> 00:04:09,689 As you can see, the pings work. 45 00:04:09,689 --> 00:04:13,389 Now let’s switch to simulation mode, and\nping again. 46 00:04:16,220 --> 00:04:22,280 In reality PC1 should store the IP address\n 47 00:04:22,279 --> 00:04:27,049 it seems that doesn’t work in packet tracer,\n 48 00:04:27,050 --> 00:04:31,810 Anyway, lets go to the point where the ICMP\npacket is at R1. 49 00:04:31,810 --> 00:04:36,149 And now let’s check that packet, and click\n 50 00:04:36,149 --> 00:04:40,839 So, this is the state of the packet as it\n 51 00:04:40,839 --> 00:04:45,119 Notice the DSCP field is written as hexadecimal\n00. 52 00:04:45,120 --> 00:04:52,680 Technically, two hexadecimal digits is 8 bits,\n 53 00:04:52,680 --> 00:04:55,600 And in packet tracer, the ECN field isn’t\ndisplayed. 54 00:04:55,600 --> 00:05:00,820 Anyway, since the field is displayed in hexadecimal\n 55 00:05:00,819 --> 00:05:05,589 when we check the markings, but for now just\n 56 00:05:08,600 --> 00:05:12,830 This is how PCs send their traffic by default,\n 57 00:05:15,060 --> 00:05:20,180 For time’s sake I won’t show you HTTP\n 58 00:05:22,069 --> 00:05:26,430 Okay, now let’s configure QoS, I’ll go\non R1. 59 00:05:27,800 --> 00:05:34,829 CONF T. So, there are three main steps to\nconfigure QoS. 60 00:05:34,829 --> 00:05:38,069 First, you have to identify the traffic. 61 00:05:38,069 --> 00:05:42,209 In order to give special treatment for certain\n 62 00:05:42,209 --> 00:05:46,339 what kinds of traffic you want to give that\n 63 00:05:46,339 --> 00:05:51,949 To identify traffic in a Cisco IOS QoS configuration,\n 64 00:05:54,399 --> 00:06:02,008 I will call this first class map HTTPS_MAP,\n 65 00:06:02,009 --> 00:06:05,980 Then I will enter MATCH PROTOCOL HTTPS. 66 00:06:06,990 --> 00:06:12,600 So, this class map can be used to identify\n 67 00:06:17,370 --> 00:06:21,780 I’ll use this to match HTTP traffic. 68 00:06:25,649 --> 00:06:28,758 And one more, we’ll match ICMP traffic. 69 00:06:34,560 --> 00:06:38,168 Okay, let’s check those class maps. 70 00:06:38,168 --> 00:06:43,399 DO SHOW RUN | SECTION CLASS-MAP. 71 00:06:43,399 --> 00:06:46,219 There are the three class maps I configured. 72 00:06:46,220 --> 00:06:53,389 Notice that, although I only typed CLASS-MAP\n 73 00:06:53,389 --> 00:06:59,050 ICMP_MAP, the default mode of MATCH-ALL was\napplied. 74 00:06:59,050 --> 00:07:03,900 This means that, to match this class map,\n 75 00:07:05,930 --> 00:07:10,680 In this case, each class map only has one\n 76 00:07:10,680 --> 00:07:15,490 if there are multiple match statements you\n 77 00:07:15,490 --> 00:07:20,400 will match that class map even if it matches\n 78 00:07:21,680 --> 00:07:26,490 So you could, for example, make a class map\n 79 00:07:30,589 --> 00:07:36,959 In that case, if a packet is either an HTTPS\n 80 00:07:40,839 --> 00:07:44,788 So, that’s the first step of QoS configuration. 81 00:07:44,788 --> 00:07:48,029 Identify the kinds of traffic you want to\n 82 00:07:48,029 --> 00:07:54,029 Next, we have to specify what kind of treatment\n 83 00:07:56,620 --> 00:08:04,079 The command is POLICY-MAP, and I’ll name\n 84 00:08:04,079 --> 00:08:08,948 policy map outbound on the G0/0/0 interface. 85 00:08:08,949 --> 00:08:14,670 Then I’ll use CLASS, followed by the name\n 86 00:08:16,329 --> 00:08:22,870 Okay, now we can tell R1 what to do with traffic\n 87 00:08:27,500 --> 00:08:33,610 So, it will mark any HTTPS packets with a\nDSCP value of AF31. 88 00:08:33,610 --> 00:08:40,229 Then, we’ll give HTTPS a priority queue\n 89 00:08:44,350 --> 00:08:48,860 Okay, that’s all for the HTTPS class. 90 00:09:00,100 --> 00:09:04,690 And now we’ll give it a minimum bandwidth\n 91 00:09:19,909 --> 00:09:22,829 And we’ll give it 5% of bandwidth. 92 00:09:28,000 --> 00:09:31,240 Okay let’s check that configuration. 93 00:09:31,240 --> 00:09:35,100 DO SHOW RUNNING-CONFIG | SECTION POLICY-MAP. 94 00:09:35,100 --> 00:09:39,259 So, here’s how this QoS configuration works. 95 00:09:39,259 --> 00:09:44,659 We haven’t actually applied it outbound\n 96 00:09:44,659 --> 00:09:48,730 all traffic that is to be forwarded out of\nG0/0/0. 97 00:09:48,730 --> 00:09:55,379 If its an HTTPS packet, it will mark it as\n 98 00:09:55,379 --> 00:09:58,600 at least 10% of the link’s bandwidth. 99 00:09:58,600 --> 00:10:04,830 If it’s an HTTP packet it will mark it as\n 100 00:10:07,370 --> 00:10:13,850 If it’s ICMP traffic it will mark the packet\n 101 00:10:16,750 --> 00:10:21,539 All other traffic, not matching any of these,\n 102 00:10:24,490 --> 00:10:29,549 Okay, finally let’s apply this policy map\n 103 00:10:31,820 --> 00:10:38,930 SERVICE-POLICY OUTPUT,and then the policy\n 104 00:10:38,929 --> 00:10:44,319 That’s it, our QoS configuration is complete. 105 00:10:46,830 --> 00:10:53,600 For review, here are the class maps, identifying\n 106 00:10:53,600 --> 00:10:58,080 Below them is the policy map, which sets the\n 107 00:10:59,399 --> 00:11:06,889 Finally, I used a service policy to apply\n 108 00:11:06,889 --> 00:11:11,580 Now let’s send some traffic from PC1 to\n 109 00:11:11,580 --> 00:11:13,379 Let me switch to simulation mode. 110 00:11:15,958 --> 00:11:21,639 If I use the name jeremysitlab.com it’ll\n 111 00:11:25,470 --> 00:11:30,399 Let’s bring the packet to R1, and then check. 112 00:11:30,399 --> 00:11:37,519 In the inbound PDU details tab, the DSCP marking\n 113 00:11:37,519 --> 00:11:44,309 state of the packet as it is forwarded by\n 114 00:11:44,309 --> 00:11:46,939 Let me open up this document to show the calculations. 115 00:11:46,940 --> 00:11:55,620 So, we marked it as CS2, and here’s the\n 116 00:11:55,620 --> 00:12:02,769 In hexadecimal that is 1 0, so that’s why\n 117 00:12:02,769 --> 00:12:07,588 Okay, now let’s send some HTTP traffic from\nPC1 to SRV1. 118 00:12:07,589 --> 00:12:13,010 I’ll return to realtime mode, then I’ll\n 119 00:12:14,480 --> 00:12:21,200 I’ll enter the URL here, HTTP://10.0.0.100. 120 00:12:21,200 --> 00:12:26,310 Now, let me switch back to simulation mode. 121 00:12:26,309 --> 00:12:28,049 Now I’ll hit GO in the browser. 122 00:12:28,049 --> 00:12:33,309 Okay, let’s bring the packet to R1, and\nthen check again. 123 00:12:33,309 --> 00:12:36,458 Inbound PDU details, the marking is 0. 124 00:12:39,200 --> 00:12:43,180 Okay we marked it as AF32, let’s check the\nmath. 125 00:12:43,179 --> 00:12:48,328 Here it is in binary, 011 100. 126 00:12:48,328 --> 00:12:56,219 That’s 28 in decimal, 16+8+4, which is 1c\n 127 00:12:57,919 --> 00:13:02,649 Okay, I’ll return to realtime mode. 128 00:13:02,649 --> 00:13:04,970 Finally let’s send some HTTPS traffic. 129 00:13:04,970 --> 00:13:11,528 I’ll go back to the web browser, and add\nan S after HTTP. 130 00:13:11,528 --> 00:13:15,730 Then I’ll switch back to simulation mode\n 131 00:13:15,730 --> 00:13:19,550 Bring the packet to R1, and let’s check. 132 00:13:19,549 --> 00:13:24,659 So, inbound PDU details, the DSCP marking\nis 0. 133 00:13:24,659 --> 00:13:30,269 But outbound, R1 has marked it as DSCP 1A,\nwhich should be AF31. 134 00:13:32,350 --> 00:13:37,990 So, here’s AF31 in binary, 011 010. 135 00:13:37,990 --> 00:13:42,850 That’s 26 in decimal, 16 + 8 + 2. 136 00:13:42,850 --> 00:13:47,750 Convert that to hexadecimal and you get 1A,\n 137 00:13:49,200 --> 00:13:52,910 Okay, in this lab we took a look at QoS configuration. 138 00:13:52,909 --> 00:13:58,269 Once again, you don’t need to know this\n 139 00:13:58,269 --> 00:14:01,649 to see some basic QoS configurations. 140 00:14:01,649 --> 00:14:07,520 Class maps identify traffic, policy maps specify\n 141 00:14:07,520 --> 00:14:10,689 service policies apply the policy maps to\ninterfaces. 142 00:14:12,700 --> 00:14:18,680 Usually, we’d take a look at a lab in Boson\n 143 00:14:18,679 --> 00:14:23,319 a CCNA exam topic there are no QoS labs in\nNetSim for CCNA. 144 00:14:23,320 --> 00:14:30,250 Plus, I think this lab video has been long\n 145 00:14:30,250 --> 00:14:35,139 Before finishing today’s video I want to\n 146 00:14:35,139 --> 00:14:39,559 To join, please click the ‘Join’ button\nunder the video. 147 00:14:39,559 --> 00:14:45,338 Thank you to Khoa, Justin, Christopher, Sam,\n 148 00:14:45,339 --> 00:14:51,940 Serge, Njoku, Viktor, Roger, Raj, Kenneth,\n 149 00:14:51,940 --> 00:14:57,010 Gustavo, Prakaash, Nasir, Erlison, Marko,\n 150 00:14:57,009 --> 00:15:01,549 Mark, Yousif, Boson Software, Devin, Yonatan,\nand Vance. 151 00:15:01,549 --> 00:15:06,088 Sorry if I pronounced your name incorrectly,\n 152 00:15:06,089 --> 00:15:11,800 This is the list of JCNP-level members at\n 153 00:15:12,799 --> 00:15:17,009 If you signed up recently and your name isn’t\n 154 00:15:21,159 --> 00:15:25,059 Please subscribe to the channel, like the\n 155 00:15:25,059 --> 00:15:28,399 with anyone else studying for the CCNA. 156 00:15:28,399 --> 00:15:31,039 If you want to leave a tip, check the links\nin the description. 157 00:15:31,039 --> 00:15:37,028 I'm also a Brave verified publisher and accept\n 12809

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.