All language subtitles for Free-CCNA-QoS-Part-1-Day-46-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:01,120 --> 00:00:07,600 Welcome to Jeremy’s IT Lab. This is a free,\xa0\n 2 00:00:07,599 --> 00:00:13,519 videos, please subscribe to follow along with the\xa0\n 3 00:00:13,519 --> 00:00:17,679 and share the video to help spread this\xa0\n 4 00:00:19,039 --> 00:00:25,839 In this video I will introduce Quality of Service,\xa0\n 5 00:00:25,839 --> 00:00:32,799 of network traffic to minimize things like delay\xa0\n 6 00:00:32,799 --> 00:00:39,839 4.7. However, that’s not the only thing we’ll\xa0\n 7 00:00:39,840 --> 00:00:46,480 Power over Ethernet. PoE allows devices to\xa0\n 8 00:00:46,479 --> 00:00:52,000 instead of requiring a separate power\xa0\n 9 00:00:52,000 --> 00:00:56,399 which is a topic I didn’t mention in the\xa0\n 10 00:00:56,399 --> 00:01:02,879 topics aren’t directly related to QoS, they are\xa0\n 11 00:01:03,920 --> 00:01:10,079 QoS is often used to prioritize Voice over IP\xa0\n 12 00:01:10,079 --> 00:01:15,599 is acceptable. So, that’s why I’ve decided to\xa0\n 13 00:01:16,560 --> 00:01:20,079 They are small topics on the CCNA,\xa0\n 14 00:01:21,519 --> 00:01:26,959 Here’s what we’ll cover. First up, I’ll give\xa0\n 15 00:01:26,959 --> 00:01:33,679 as the concept of voice VLANs. IP phones are\xa0\n 16 00:01:33,680 --> 00:01:40,000 over IP networks, such as the Internet. Then\xa0\n 17 00:01:40,000 --> 00:01:44,799 which is commonly used to provide electric\xa0\n 18 00:01:44,799 --> 00:01:49,759 as opposed to using a separate power\xa0\n 19 00:01:49,760 --> 00:01:56,800 an intro to quality of service, QoS. I will\xa0\n 20 00:01:56,799 --> 00:02:02,000 and then in the next video we’ll look at some\xa0\n 21 00:02:02,000 --> 00:02:08,479 for a bonus question from Boson Software’s ExSim\xa0\n 22 00:02:10,319 --> 00:02:16,239 So first let’s cover IP phones. Traditional\xa0\n 23 00:02:16,240 --> 00:02:24,000 network, PSTN. Sometimes this is called POTS,\xa0\n 24 00:02:24,000 --> 00:02:29,919 other hand, use VoIP, Voice over IP, technologies\xa0\n 25 00:02:29,919 --> 00:02:37,439 such as the Internet. Audio data is encapsulated\xa0\n 26 00:02:37,439 --> 00:02:44,079 an example of a Cisco IP phone. Cisco IP phones\xa0\n 27 00:02:44,080 --> 00:02:49,520 although of course there are other vendors that\xa0\n 28 00:02:49,520 --> 00:02:56,080 to a switch just like any other end host. So, you\xa0\n 29 00:02:56,080 --> 00:03:02,800 at each desk, each connected to its own switch\xa0\n 30 00:03:02,800 --> 00:03:07,120 but there is a much better and more common\xa0\n 31 00:03:08,199 --> 00:03:15,359 IP phones have an internal 3-port switch. 1 port\xa0\n 32 00:03:15,360 --> 00:03:22,080 switch. 1 port is the downlink which connects\xa0\n 33 00:03:22,080 --> 00:03:29,440 the phone itself. Let me demonstrate. So, we have\xa0\n 34 00:03:30,400 --> 00:03:34,400 However, within the IP phone there is a\xa0\n 35 00:03:35,280 --> 00:03:40,479 One of these is used to connect to the switch\xa0\n 36 00:03:40,479 --> 00:03:46,079 again with an Ethernet cable. And the last\xa0\n 37 00:03:46,080 --> 00:03:50,160 This one is internal, you don’t actually have\xa0\n 38 00:03:51,120 --> 00:03:56,879 So, why is this setup better? It allows the PC\xa0\n 39 00:03:57,919 --> 00:04:02,079 Traffic from the PC passes through\xa0\n 40 00:04:03,199 --> 00:04:06,239 Traffic from the IP phone itself\xa0\n 41 00:04:07,439 --> 00:04:11,840 So, with the same amount of devices we\xa0\n 42 00:04:11,840 --> 00:04:16,079 meaning we need less switches, so we don’t\xa0\n 43 00:04:17,360 --> 00:04:22,240 Note that it is recommended to separate voice\xa0\n 44 00:04:22,240 --> 00:04:28,400 and data traffic, which is traffic from the\xa0\n 45 00:04:28,399 --> 00:04:33,439 mention this again later, but when configuring\xa0\n 46 00:04:33,439 --> 00:04:38,480 the traffic from the IP phones and give it a\xa0\n 47 00:04:39,439 --> 00:04:45,519 So, we can place them in separate VLANs by\xa0\n 48 00:04:45,519 --> 00:04:51,120 traffic from the PC will be untagged, but traffic\xa0\n 49 00:04:53,279 --> 00:04:55,839 So, how can we configure a\xa0\n 50 00:04:56,720 --> 00:05:01,760 Remember, the PC and the IP phone will use\xa0\n 51 00:05:01,759 --> 00:05:06,560 configure, you only need one additional command\xa0\n 52 00:05:07,839 --> 00:05:14,879 Here’s the configuration. I enter interface config\xa0\n 53 00:05:14,879 --> 00:05:22,639 assign it to access vlan 10, and here’s the\xa0\n 54 00:05:22,639 --> 00:05:28,560 this configuration, PC1 will send its traffic\xa0\n 55 00:05:28,560 --> 00:05:36,399 an access port is an ‘untagged’ port. Usually they\xa0\n 56 00:05:36,399 --> 00:05:43,679 SW1 will use CDP, Cisco Discovery Protocol,\xa0\n 57 00:05:44,879 --> 00:05:50,639 So, this access port is now accepting traffic\xa0\n 58 00:05:50,639 --> 00:05:57,759 usually carries traffic from multiple VLANs?\xa0\n 59 00:05:58,560 --> 00:06:06,319 We configured SWITCHPORT MODE ACCESS, not TRUNK.\xa0\n 60 00:06:06,319 --> 00:06:14,480 I used SHOW INTERFACES G0/0 SWITCHPORT. Here we\xa0\n 61 00:06:14,480 --> 00:06:20,960 voice VLAN of 11. But up here, we can see that\xa0\n 62 00:06:20,959 --> 00:06:26,879 mode are static access. So, even though it\xa0\n 63 00:06:27,439 --> 00:06:31,920 G0/0 is not considered a trunk port.\xa0\n 64 00:06:33,680 --> 00:06:38,959 Let’s take a look at another command to\xa0\n 65 00:06:38,959 --> 00:06:43,199 and nothing was displayed, telling\xa0\n 66 00:06:44,319 --> 00:06:49,920 Now, even if the interface is an access port,\xa0\n 67 00:06:49,920 --> 00:06:55,040 and then TRUNK. That’s what I did here.\xa0\n 68 00:06:55,600 --> 00:07:00,640 again telling us that this isn’t considered\xa0\n 69 00:07:00,639 --> 00:07:05,519 ‘Vlans allowed on trunk’ here, but it always says\xa0\n 70 00:07:07,680 --> 00:07:12,560 So, looking back a few slides, instead of\xa0\n 71 00:07:12,560 --> 00:07:19,519 and each IP phone, we can take these three PCs and\xa0\n 72 00:07:19,519 --> 00:07:26,399 six switchports, we are now using only three. We\xa0\n 73 00:07:26,399 --> 00:07:32,479 sometimes called a data VLAN. And we configure\xa0\n 74 00:07:33,759 --> 00:07:38,560 Okay, so that allows us to use fewer switchports.\xa0\n 75 00:07:38,560 --> 00:07:45,680 to for an IP phone to work. Of course, being an\xa0\n 76 00:07:46,480 --> 00:07:51,040 That means we need to plug them into a wall socket\xa0\n 77 00:07:52,079 --> 00:07:56,240 Or, perhaps there’s a better solution that\xa0\n 78 00:07:56,879 --> 00:08:01,360 And there is such a solution, it is\xa0\n 79 00:08:02,959 --> 00:08:05,759 So, let’s get into PoE, Power over Ethernet.\xa0\xa0 80 00:08:06,800 --> 00:08:14,079 PoE allows Power Sourcing Equipment, PSE, to\xa0\n 81 00:08:14,079 --> 00:08:21,759 over an Ethernet cable. Typically the PSE is a\xa0\n 82 00:08:21,759 --> 00:08:28,079 wireless access points, etc. To clarify, this is\xa0\n 83 00:08:28,079 --> 00:08:34,319 data. You don’t need a separate cable. One cable\xa0\n 84 00:08:35,360 --> 00:08:42,000 The PSE, the switch, receives AC power from the\xa0\n 85 00:08:42,000 --> 00:08:49,120 that DC power to the PDs, for example IP phones.\xa0\n 86 00:08:49,120 --> 00:08:57,600 outlet, it is the PSE, power sourcing equipment.\xa0\n 87 00:08:57,600 --> 00:09:04,159 outlet provides AC power, but electronic devices\xa0\n 88 00:09:04,159 --> 00:09:10,879 DC and provides it to the IP phones. These same\xa0\n 89 00:09:12,399 --> 00:09:16,000 But you have to be careful about\xa0\n 90 00:09:16,960 --> 00:09:23,200 Too much electrical current can harm electrical\xa0\n 91 00:09:23,200 --> 00:09:28,879 a connected device needs power, and how much\xa0\n 92 00:09:28,879 --> 00:09:35,279 simplification, but basically when a device is\xa0\n 93 00:09:35,279 --> 00:09:41,279 sends low power signals, monitors the response,\xa0\n 94 00:09:42,399 --> 00:09:47,279 These first signals are very weak to ensure\xa0\n 95 00:09:47,279 --> 00:09:52,480 the connected device, causing it harm.\xa0\n 96 00:09:52,480 --> 00:09:59,360 the PSE supplies power to allow the PD to boot.\xa0\n 97 00:09:59,360 --> 00:10:06,240 supplying power as needed, but again not too much\xa0\n 98 00:10:06,240 --> 00:10:13,440 which prevents a PD from taking too much power.\xa0\n 99 00:10:13,440 --> 00:10:19,600 but let me demonstrate just a few commands\xa0\n 100 00:10:19,600 --> 00:10:23,600 configured on an interface, configures\xa0\n 101 00:10:24,399 --> 00:10:29,120 It will disable the port and send a Syslog\xa0\n 102 00:10:30,159 --> 00:10:36,879 This is equivalent to the command POWER INLINE\xa0\n 103 00:10:36,879 --> 00:10:42,000 are the default for power policing and have\xa0\n 104 00:10:42,000 --> 00:10:47,440 in an ‘error-disabled’ state and then it can\xa0\n 105 00:10:47,440 --> 00:10:53,360 followed by NO SHUTDOWN. Okay, so that’s one\xa0\n 106 00:10:54,320 --> 00:11:02,000 POWER INLINE POLICE or POWER INLINE POLICE ACTION\xa0\n 107 00:11:02,879 --> 00:11:09,200 POWER INLINE POLICE ACTION LOG does not shut down\xa0\n 108 00:11:10,159 --> 00:11:13,839 It will simply restart the\xa0\n 109 00:11:14,799 --> 00:11:18,159 So, because the interface\xa0\nrestarts, the connected PD\xa0\xa0 110 00:11:18,159 --> 00:11:23,600 will lose power and then restart as well.\xa0\n 111 00:11:25,679 --> 00:11:30,879 Let me show you those commands in\xa0\n 112 00:11:30,879 --> 00:11:38,080 I issued the command POWER INLINE POLICE. Then I\xa0\n 113 00:11:39,120 --> 00:11:43,120 First of all, here you can see how much\xa0\n 114 00:11:43,120 --> 00:11:49,200 and how much capacity it has. But here’s what\xa0\n 115 00:11:49,200 --> 00:11:55,840 specify ACTION ERR-DISABLE in the command, you\xa0\n 116 00:11:56,559 --> 00:12:00,000 Okay, this time I issued the\xa0\n 117 00:12:00,000 --> 00:12:07,919 ACTION LOG. I did SHOW POWER INLINE POLICE G0/0,\xa0\n 118 00:12:07,919 --> 00:12:12,159 the interface won’t be err-disabled if\xa0\n 119 00:12:13,440 --> 00:12:18,080 Power policing is one aspect of PoE that\xa0\n 120 00:12:18,960 --> 00:12:25,200 Just be aware of its purpose, preventing PDs\xa0\n 121 00:12:26,879 --> 00:12:34,879 Here are some standards of PoE. Actually, PoE\xa0\n 122 00:12:34,879 --> 00:12:42,320 ILP. As has happened multiple times, for\xa0\n 123 00:12:42,320 --> 00:12:49,760 the technology first for its devices, and then it\xa0\n 124 00:12:49,759 --> 00:12:56,960 of power per port from the PSE, and 2 wire pairs\xa0\n 125 00:12:56,960 --> 00:13:02,480 how Ethernet and FastEthernet only used 4 of the\xa0\n 126 00:13:03,279 --> 00:13:09,759 They used wires 1, 2, 3, and 6. Well,\xa0\n 127 00:13:09,759 --> 00:13:18,080 4, 5, 7, and 8, to provide power. Later, Cisco ILP\xa0\n 128 00:13:18,080 --> 00:13:26,560 device makers would be able to use the technology.\xa0\n 129 00:13:26,559 --> 00:13:35,039 provide more power than the original Cisco ILP.\xa0\n 130 00:13:36,559 --> 00:13:41,279 Then, Cisco released another original\xa0\n 131 00:13:41,279 --> 00:13:47,839 which stands for Universal Power over Ethernet.\xa0\n 132 00:13:49,200 --> 00:13:56,800 This includes Type 3, offering up to 60 watts,\xa0\n 133 00:13:56,799 --> 00:14:02,879 probably don’t have to memorize this table for the\xa0\n 134 00:14:02,879 --> 00:14:08,639 what it is and what it’s used for. However, just\xa0\n 135 00:14:08,639 --> 00:14:13,759 table in the supplemental resources. It’s up\xa0\n 136 00:14:15,360 --> 00:14:20,399 Returning to that previous slide again, the PCs\xa0\n 137 00:14:20,399 --> 00:14:25,519 get their power. But these phones are able to\xa0\n 138 00:14:25,519 --> 00:14:31,120 to connect to the switch. PoE isn’t a\xa0\n 139 00:14:31,120 --> 00:14:37,360 the information I gave you in this video. Now\xa0\n 140 00:14:38,399 --> 00:14:42,159 Why did I spend all this time\xa0\n 141 00:14:42,159 --> 00:14:48,240 in a video about QoS? It’s because the voice\xa0\n 142 00:14:48,240 --> 00:14:54,159 apply QoS to, to give higher priority to the\xa0\n 143 00:14:56,000 --> 00:14:59,600 First, here’s an extremely simple\xa0\n 144 00:15:00,720 --> 00:15:06,960 Voice traffic and data traffic used to use\xa0\n 145 00:15:06,960 --> 00:15:14,480 PSTN, public switched telephone network. And what\xa0\n 146 00:15:14,480 --> 00:15:20,480 enterprise WAN or the Internet, for example a PC\xa0\n 147 00:15:21,600 --> 00:15:27,200 QoS wasn’t really necessary, because the different\xa0\n 148 00:15:28,000 --> 00:15:32,240 The audio quality of a phone call won’t be\xa0\n 149 00:15:33,519 --> 00:15:40,079 However, modern networks are typically converged\xa0\n 150 00:15:40,080 --> 00:15:46,960 regular data traffic such as web traffic, etc,\xa0\n 151 00:15:46,960 --> 00:15:52,320 hasn’t disappeared, it’s still used all over the\xa0\n 152 00:15:52,320 --> 00:15:58,400 now on. Converged networks enable cost savings\xa0\n 153 00:15:58,399 --> 00:16:05,360 video traffic. For example IP phones can integrate\xa0\n 154 00:16:05,360 --> 00:16:11,039 Microsoft Teams. However, the different kinds\xa0\n 155 00:16:11,919 --> 00:16:15,679 If there is plenty of available bandwidth\xa0\n 156 00:16:15,679 --> 00:16:20,719 that’s not a problem, but a busy network can\xa0\n 157 00:16:20,720 --> 00:16:27,840 which is sensitive to things such as delay. QoS,\xa0\n 158 00:16:27,840 --> 00:16:33,840 network devices to apply different treatment to\xa0\n 159 00:16:33,840 --> 00:16:38,240 higher priority treatment, and other kinds\xa0\n 160 00:16:40,320 --> 00:16:44,640 QoS is used to manage the following\xa0\n 161 00:16:45,519 --> 00:16:48,319 First, bandwidth, a term\xa0\n 162 00:16:49,360 --> 00:16:54,240 This refers to the overall capacity of the\xa0\n 163 00:16:54,240 --> 00:17:00,639 for example kilobits per second, megabits\xa0\n 164 00:17:00,639 --> 00:17:05,440 tools allow you to reserve a certain amount of a\xa0\n 165 00:17:06,400 --> 00:17:10,480 For example, you could reserve 20% of\xa0\n 166 00:17:11,039 --> 00:17:18,079 30% for specific kinds of important data\xa0\n 167 00:17:18,079 --> 00:17:22,720 The next characteristic is delay. There\xa0\n 168 00:17:23,519 --> 00:17:28,240 The amount of time it takes for traffic to go\xa0\n 169 00:17:28,240 --> 00:17:33,920 delay. Let me demonstrate. The amount of time\xa0\n 170 00:17:34,559 --> 00:17:40,799 is called one-way delay. Alternatively, we could\xa0\n 171 00:17:40,799 --> 00:17:46,399 traffic to go from source to destination and\xa0\n 172 00:17:46,400 --> 00:17:52,480 a packet to go from phone1 to phone2, but also\xa0\n 173 00:17:54,400 --> 00:18:00,240 Okay, next up is Jitter. Jitter is the variation\xa0\n 174 00:18:00,240 --> 00:18:07,440 same application. So, if some packets arrive in 10\xa0\n 175 00:18:07,440 --> 00:18:12,000 that’s a lot of jitter, a big difference in\xa0\n 176 00:18:12,000 --> 00:18:17,759 its destination. Jitter will negatively affect\xa0\n 177 00:18:17,759 --> 00:18:23,920 have a jitter buffer to provide a fixed delay\xa0\n 178 00:18:23,920 --> 00:18:29,840 high it will overrun the buffer and the audio\xa0\n 179 00:18:30,559 --> 00:18:36,399 This refers to the percentage of packets sent that\xa0\n 180 00:18:36,400 --> 00:18:42,800 by faulty cables, or if the network is congested\xa0\n 181 00:18:42,799 --> 00:18:48,000 start discarding packets that can’t fit into the\xa0\n 182 00:18:48,000 --> 00:18:53,200 destination, for example, that will obviously\xa0\n 183 00:18:54,960 --> 00:18:59,120 There are a few recommended standards\xa0\n 184 00:19:00,079 --> 00:19:04,639 Interactive audio means something like a\xa0\n 185 00:19:05,519 --> 00:19:11,119 It is recommended that the one-way delay be\xa0\n 186 00:19:11,119 --> 00:19:17,919 the variation in delay, should be 30 milliseconds\xa0\n 187 00:19:18,960 --> 00:19:22,000 If these standards are met, you\xa0\n 188 00:19:22,559 --> 00:19:26,159 but if the standards are not met there\xa0\n 189 00:19:26,160 --> 00:19:30,160 quality of the phone call, the user\xa0\n 190 00:19:31,839 --> 00:19:36,720 Now let me introduce the topic of queuing, which\xa0\n 191 00:19:36,720 --> 00:19:42,799 QoS. If a network device receives messages faster\xa0\n 192 00:19:42,799 --> 00:19:48,879 interface, the messages are placed in a queue.\xa0\n 193 00:19:48,880 --> 00:19:56,560 on its G0/0 and G0/1 interfaces faster than it\xa0\n 194 00:19:56,559 --> 00:20:03,119 as you can see the queue for its G0/2 interface\xa0\n 195 00:20:03,119 --> 00:20:10,239 will be forwarded in a First In First Out, FIFO,\xa0\n 196 00:20:10,240 --> 00:20:15,279 sent in the order they are received. No special\xa0\n 197 00:20:17,039 --> 00:20:23,200 Now, what happens if the queue becomes full?\xa0\n 198 00:20:23,200 --> 00:20:27,519 interfaces faster than the router\xa0\n 199 00:20:27,519 --> 00:20:33,279 and the queue fills up. When this happens,\xa0\n 200 00:20:33,279 --> 00:20:38,720 packet arrives and needs to be forwarded out\xa0\n 201 00:20:39,680 --> 00:20:44,320 This is called tail drop, when there is not\xa0\n 202 00:20:46,480 --> 00:20:51,360 Tail drop is harmful, not just because packets\xa0\n 203 00:20:51,359 --> 00:20:58,159 called TCP global synchronization. To explain\xa0\n 204 00:20:59,279 --> 00:21:04,399 Hosts using TCP use the ‘sliding window’ to\xa0\n 205 00:21:04,400 --> 00:21:09,759 send traffic as needed. So, the host will try\xa0\n 206 00:21:10,319 --> 00:21:15,279 And when a packet is dropped, it will be\xa0\n 207 00:21:15,279 --> 00:21:21,119 the sender will reduce the rate it sends traffic.\xa0\n 208 00:21:21,119 --> 00:21:26,639 and the process will repeat if another packet\xa0\n 209 00:21:26,640 --> 00:21:31,840 drop occurs, all TCP hosts sending traffic will\xa0\n 210 00:21:33,039 --> 00:21:36,000 They will all then increase the\xa0\n 211 00:21:36,000 --> 00:21:41,200 which rapidly leads to more congestion, dropped\xa0\n 212 00:21:42,319 --> 00:21:46,879 So, it creates waves of the network being\xa0\n 213 00:21:46,880 --> 00:21:51,600 rate of transmission, and then congested, when\xa0\n 214 00:21:52,640 --> 00:21:57,440 Let me illustrate it for you. Network\xa0\n 215 00:21:57,440 --> 00:22:04,559 which leads to a global TCP window size decrease.\xa0\n 216 00:22:04,559 --> 00:22:10,319 will decrease their window size. That leads\xa0\n 217 00:22:10,319 --> 00:22:14,799 hosts reduce their transmission rate, so they’re\xa0\n 218 00:22:15,839 --> 00:22:22,079 That leads to a global TCP window size increase.\xa0\n 219 00:22:22,079 --> 00:22:27,199 send traffic more quickly than they currently are,\xa0\n 220 00:22:28,240 --> 00:22:32,400 This leads once again to network congestion,\xa0\n 221 00:22:33,519 --> 00:22:40,319 Overutilization, underutilization,\xa0\n 222 00:22:40,319 --> 00:22:45,359 A solution to prevent tail drop and\xa0\n 223 00:22:45,359 --> 00:22:52,079 is Random Early Detection, RED. When the amount of\xa0\n 224 00:22:52,079 --> 00:22:55,839 the device will start randomly\xa0\n 225 00:22:56,640 --> 00:23:02,560 Why is this better than tail drop? Those TCP flows\xa0\n 226 00:23:02,559 --> 00:23:08,960 traffic is sent, but you will avoid global TCP\xa0\n 227 00:23:08,960 --> 00:23:14,640 and then increase the rate of transmission at\xa0\n 228 00:23:14,640 --> 00:23:21,360 the rate of traffic more even. Now, in standard\xa0\n 229 00:23:21,359 --> 00:23:26,479 There is a global threshold, and if the amount\xa0\n 230 00:23:26,480 --> 00:23:32,640 the device will start dropping traffic randomly as\xa0\n 231 00:23:32,640 --> 00:23:38,640 Weighted Random Early Detection, WRED, allows you\xa0\n 232 00:23:38,640 --> 00:23:44,640 the traffic class. So, you could for example start\xa0\n 233 00:23:45,440 --> 00:23:48,160 FTP packets when the queue is that full, etc.\xa0\xa0 234 00:23:48,960 --> 00:23:52,799 The kinds of traffic that you configure\xa0\n 235 00:23:54,160 --> 00:23:58,720 We will cover traffic classes and more\xa0\n 236 00:23:58,720 --> 00:24:03,839 the next video. For now, I think this is\xa0\n 237 00:24:05,200 --> 00:24:11,440 Okay, before moving on to the quiz let’s review\xa0\n 238 00:24:11,440 --> 00:24:17,440 voice VLANs. I showed you that an IP phone can\xa0\n 239 00:24:17,440 --> 00:24:23,360 connected to the IP phone. A voice VLAN can be\xa0\n 240 00:24:23,359 --> 00:24:29,759 will tag traffic it sends using the voice VLAN.\xa0\n 241 00:24:29,759 --> 00:24:34,640 which allows end devices to receive electric\xa0\n 242 00:24:34,640 --> 00:24:41,040 to send and receive data. It is commonly used for\xa0\n 243 00:24:42,319 --> 00:24:46,639 Finally we got to the main topic of the\xa0\n 244 00:24:46,640 --> 00:24:51,120 QoS, which allows you to give special\xa0\n 245 00:24:51,759 --> 00:24:56,000 and it’s commonly used for delay-sensitive\xa0\n 246 00:24:57,039 --> 00:25:01,839 However, we only covered the foundational\xa0\n 247 00:25:01,839 --> 00:25:08,799 jitter, and loss. In the next video we’ll look at\xa0\n 248 00:25:08,799 --> 00:25:13,839 until the end of the video for a bonus practice\xa0\n 249 00:25:14,400 --> 00:25:19,680 the best practice exams for the CCNA.\xa0\n 250 00:25:21,920 --> 00:25:27,840 Examine G0/0’s interface configuration. Which of\xa0\n 251 00:25:28,480 --> 00:25:32,640 Okay, pause the video now to look at the\xa0\n 252 00:25:37,279 --> 00:25:44,079 Okay, the answers are A, voice traffic received\xa0\n 253 00:25:44,640 --> 00:25:52,000 data traffic received by G0/0 should be untagged.\xa0\n 254 00:25:52,000 --> 00:25:58,559 that it is in VLAN 99, and then it should tag\xa0\n 255 00:25:58,559 --> 00:26:04,399 SWITCHPORT ACCESS VLAN command on the interface,\xa0\n 256 00:26:05,359 --> 00:26:11,759 Data traffic, for example sent by a PC connected\xa0\n 257 00:26:11,759 --> 00:26:19,039 send its traffic untagged. After SW1 receives the\xa0\n 258 00:26:19,039 --> 00:26:24,399 but when it actually receives the traffic it\xa0\n 259 00:26:26,720 --> 00:26:31,120 You issue the power inline police\xa0\n 260 00:26:31,839 --> 00:26:35,279 What will happen if the connected device\xa0\n 261 00:26:36,079 --> 00:26:38,159 Pause the video now to think about the answer. 262 00:26:42,000 --> 00:26:46,720 Okay, the answer is C, the interface will\xa0\n 263 00:26:46,720 --> 00:26:52,400 be generated. To enable it again, you should\xa0\n 264 00:26:52,400 --> 00:26:58,000 command on the interface. When you issue the\xa0\n 265 00:26:58,000 --> 00:27:05,839 so it’s equivalent to POWER INLINE POLICE ACTION\xa0\n 266 00:27:06,799 --> 00:27:10,480 Which of the following are recommended\xa0\n 267 00:27:10,480 --> 00:27:15,120 audio quality? Select three. Pause the\xa0\n 268 00:27:19,440 --> 00:27:26,640 Okay, the answers are B, delay of 150 milliseconds\xa0\n 269 00:27:26,640 --> 00:27:32,560 and E, loss of 1% or less. If these\xa0\n 270 00:27:32,559 --> 00:27:38,399 expect a noticeable reduction in the quality of\xa0\n 271 00:27:41,359 --> 00:27:44,079 Which of the following is a\xa0\n 272 00:27:44,640 --> 00:27:47,840 Pause the video now to think about the answer. 273 00:27:50,720 --> 00:27:58,000 Okay, the answer is D, TCP global synchronization.\xa0\n 274 00:27:58,559 --> 00:28:04,000 all hosts sending TCP traffic will slow down their\xa0\n 275 00:28:04,000 --> 00:28:10,079 it in unison too. This leads to repeating waves\xa0\n 276 00:28:11,119 --> 00:28:14,879 A TCP sliding window, is merely a mechanic in TCP,\xa0\xa0 277 00:28:14,880 --> 00:28:21,680 it’s not a negative thing on its own. RED\xa0\n 278 00:28:21,680 --> 00:28:26,799 so they are not a negative effect of\xa0\n 279 00:28:28,880 --> 00:28:32,240 Which of the following is the default\xa0\n 280 00:28:32,799 --> 00:28:34,799 Pause the video now to think about the answer. 281 00:28:38,880 --> 00:28:45,440 Okay, the answer is A, FIFO, which\xa0\n 282 00:28:45,440 --> 00:28:48,799 it means that packets will be forwarded\xa0\n 283 00:28:49,599 --> 00:28:56,559 Higher priority packets will not be sent to\xa0\n 284 00:28:56,559 --> 00:29:03,440 is something I’ll mention in the next video. RED\xa0\n 285 00:29:03,440 --> 00:29:09,120 methods of forwarding queued packets, they are\xa0\n 286 00:29:09,119 --> 00:29:15,279 all for the quiz. Now let’s take a look at a bonus\xa0\n 287 00:30:57,200 --> 00:30:59,440 There are supplementary materials for this video.\xa0\xa0 288 00:31:00,240 --> 00:31:04,000 There is a flashcard deck to\xa0\n 289 00:31:04,000 --> 00:31:08,000 There will also be a packet tracer practice\xa0\n 290 00:31:08,880 --> 00:31:14,080 That will be in the next video. Sign up for my\xa0\n 291 00:31:14,079 --> 00:31:17,839 and I’ll send you all of the flashcards\xa0\n 292 00:31:20,240 --> 00:31:26,160 Before finishing today’s video I want to\xa0\n 293 00:31:26,160 --> 00:31:32,400 please click the ‘Join’ button under the video.\xa0\n 294 00:31:32,400 --> 00:31:39,200 Pavel, Abraham, Serge, Njoku, Viktor, Roger, Raj,\xa0\n 295 00:31:39,759 --> 00:31:45,519 Donald, C Mohd, Gustavo, Benjamin, Justin,\xa0\n 296 00:31:45,519 --> 00:31:51,519 Ed, John, Funnydart, Velvijaykum, Mark, Yousif,\xa0\n 297 00:31:52,640 --> 00:31:56,640 Sorry if I pronounced your name incorrectly,\xa0\n 298 00:31:57,599 --> 00:32:03,359 This is the list of JCNP-level members at the\xa0\n 299 00:32:04,240 --> 00:32:09,359 If you signed up recently and your name isn’t\xa0\n 300 00:32:11,440 --> 00:32:14,480 Thank you for watching. Please\xa0\n 301 00:32:14,480 --> 00:32:19,279 like the video, leave a comment, and share the\xa0\n 302 00:32:20,319 --> 00:32:25,919 If you want to leave a tip, check the links in the\xa0\n 303 00:32:25,920 --> 00:32:32,480 and accept BAT, or Basic Attention Token, tips\xa0\n 25996

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