All language subtitles for Free-CCNA-DHCP-Day-39-CCNA-200-301-Complete-Course_en

af Afrikaans
ak Akan
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
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
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (Soranî)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian
pl Polish
pt-BR Portuguese (Brazil)
pt Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
si Sinhalese
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:00,480 --> 00:00:07,039 Welcome to Jeremy’s IT Lab. This is a free,\xa0\n 2 00:00:07,040 --> 00:00:12,480 videos, please subscribe to follow along with the\xa0\n 3 00:00:12,480 --> 00:00:16,320 and share the video to help spread this\xa0\n 4 00:00:17,679 --> 00:00:22,239 In this video we will cover DHCP,\xa0\n 5 00:00:22,960 --> 00:00:28,800 Just like DNS, DHCP is a protocol that you’re\xa0\n 6 00:00:28,800 --> 00:00:37,359 aware of it. DHCP allows DHCP clients, usually end\xa0\n 7 00:00:37,359 --> 00:00:43,840 learn which IP address to use from a DHCP server,\xa0\n 8 00:00:44,479 --> 00:00:49,759 However DHCP allows devices to learn much more\xa0\n 9 00:00:49,759 --> 00:00:58,239 video. DHCP is part of exam topics 4.3, explain\xa0\n 10 00:00:58,240 --> 00:01:06,079 and 4.6, configure and verify DHCP client and\xa0\n 11 00:01:06,079 --> 00:01:11,840 5.0, security fundamentals, however we’ll leave\xa0\n 12 00:01:13,359 --> 00:01:18,879 Here’s what we’ll cover in this video. First\xa0\n 13 00:01:18,879 --> 00:01:24,879 and why we use it. Then I’ll introduce the\xa0\n 14 00:01:24,879 --> 00:01:29,920 four-message exchange that clients use\xa0\n 15 00:01:31,120 --> 00:01:38,160 Then I’ll show you how to configure DHCP in\xa0\n 16 00:01:38,159 --> 00:01:44,399 a DHCP client, or something called a ‘DHCP\xa0\n 17 00:01:44,400 --> 00:01:49,359 all of those. Make sure to watch until\xa0\n 18 00:01:49,359 --> 00:01:55,200 question from Boson Software’s ExSim for\xa0\n 19 00:01:56,959 --> 00:02:04,479 Here’s a brief overview of DHCP. DHCP is used to\xa0\n 20 00:02:04,480 --> 00:02:08,480 various aspects of their network\xa0\n 21 00:02:08,479 --> 00:02:14,239 subnet mask, default gateway, DNS server,\xa0\n 22 00:02:15,360 --> 00:02:21,440 It is an essential part of modern networks, I’m\xa0\n 23 00:02:21,439 --> 00:02:26,960 when you connect a phone to WiFi, do you ask the\xa0\n 24 00:02:26,960 --> 00:02:33,680 which IP address, subnet mask, default gateway,\xa0\n 25 00:02:34,319 --> 00:02:39,039 we all expect that once we connect to WiFi\xa0\n 26 00:02:39,039 --> 00:02:44,879 and the Internet. It’s probably the same in your\xa0\n 27 00:02:44,879 --> 00:02:50,319 home router, you probably don’t need to manually\xa0\n 28 00:02:50,319 --> 00:02:57,359 etc. Of course, you can do that if you want, and\xa0\n 29 00:02:57,360 --> 00:03:03,840 configuration isn’t such a difficult task. However\xa0\n 30 00:03:04,879 --> 00:03:11,599 Note that DHCP is typically used for ‘client’\xa0\n 31 00:03:12,400 --> 00:03:16,400 Devices such as routers, servers,\xa0\n 32 00:03:17,280 --> 00:03:20,800 This is because they need to have a fixed\xa0\n 33 00:03:21,840 --> 00:03:26,319 If the default gateway of the network kept\xa0\n 34 00:03:27,520 --> 00:03:32,800 In small networks (such as home networks) the\xa0\n 35 00:03:32,800 --> 00:03:38,560 hosts in the LAN. If you have a router in your\xa0\n 36 00:03:38,560 --> 00:03:44,400 for all of your devices. However in larger\xa0\n 37 00:03:44,400 --> 00:03:48,159 the DHCP server is usually\xa0\na Windows or Linux server. 38 00:03:50,240 --> 00:03:54,800 Now I’ll give a brief demonstration\xa0\n 39 00:03:54,800 --> 00:03:59,840 which is running Windows 10. If your PC is\xa0\n 40 00:04:00,879 --> 00:04:06,479 This is the ‘network and sharing center’, which\xa0\n 41 00:04:06,479 --> 00:04:12,319 to select my PC’s Ethernet0 connection, which is\xa0\n 42 00:04:13,759 --> 00:04:19,279 This is what you’ll see after opening it. Here\xa0\n 43 00:04:19,279 --> 00:04:26,079 connection, Ethernet0. Then the properties are\xa0\n 44 00:04:26,959 --> 00:04:34,000 This window opens up. Here I can confirm that\xa0\n 45 00:04:34,000 --> 00:04:39,600 IP address automatically’. And down here it\xa0\n 46 00:04:40,639 --> 00:04:43,919 ‘Automatically’ means that my PC will use DHCP\xa0\xa0 47 00:04:43,920 --> 00:04:49,040 to learn which IP address, subnet mask,\xa0\n 48 00:04:51,040 --> 00:04:57,120 Let’s take a look at what was automatically\xa0\n 49 00:04:57,120 --> 00:05:02,560 which you already know. First off, notice\xa0\n 50 00:05:03,279 --> 00:05:06,879 If I had manually configured my PC’s\xa0\n 51 00:05:07,439 --> 00:05:12,800 ‘No’ would display here. And here is\xa0\n 52 00:05:12,800 --> 00:05:21,439 192.168.0.167 with a /24 subnet mask. Notice that\xa0\n 53 00:05:22,240 --> 00:05:27,040 It means that this PC was previously\xa0\n 54 00:05:28,240 --> 00:05:33,680 Then, when it asked the server for an IP address\xa0\n 55 00:05:34,639 --> 00:05:39,039 If this address was no longer available, my PC\xa0\n 56 00:05:39,759 --> 00:05:46,319 However, the address was available, so my PC got\xa0\n 57 00:05:46,319 --> 00:05:53,759 of DHCP, the lease time. IPCONFIG /ALL displays\xa0\n 58 00:05:53,759 --> 00:06:00,879 it will expire. What exactly does this mean?\xa0\n 59 00:06:01,839 --> 00:06:06,959 These leases are usually not permanent, and the\xa0\n 60 00:06:06,959 --> 00:06:12,639 the lease. A client can also release the address\xa0\n 61 00:06:13,600 --> 00:06:18,640 Now, I said ‘usually’ not permanent, because\xa0\n 62 00:06:18,639 --> 00:06:24,240 to permanently assign IP addresses. However,\xa0\n 63 00:06:25,279 --> 00:06:29,519 For example, think about a cafe that provides\xa0\n 64 00:06:30,560 --> 00:06:35,439 If the IP address leases were permanent,\xa0\n 65 00:06:35,439 --> 00:06:40,800 and connects to the WiFi, the customer’s devices\xa0\n 66 00:06:40,800 --> 00:06:47,280 unless the client device releases it. Or how about\xa0\n 67 00:06:47,279 --> 00:06:53,599 why it’s best to limit the lease time, to preserve\xa0\n 68 00:06:53,600 --> 00:06:58,400 longer than the lease time, their device will\xa0\n 69 00:06:58,959 --> 00:07:03,199 but if they stop using the network the IP\xa0\n 70 00:07:04,639 --> 00:07:09,279 Okay, here at the bottom we can see some\xa0\n 71 00:07:10,399 --> 00:07:15,839 The default gateway, DHCP server,\xa0\n 72 00:07:16,800 --> 00:07:21,280 which is my home router. This\xa0\n 73 00:07:21,279 --> 00:07:25,279 the home router provides all of these\xa0\n 74 00:07:26,800 --> 00:07:31,759 I want to demonstrate the process that a DHCP\xa0\n 75 00:07:31,759 --> 00:07:38,079 a DHCP server, but first I need to make my PC\xa0\n 76 00:07:38,079 --> 00:07:46,240 again. The command in the Windows command prompt\xa0\n 77 00:07:46,240 --> 00:07:53,759 /RELEASE. Now no information is displayed for the\xa0\n 78 00:07:53,759 --> 00:08:01,439 just happened. My PC sent a DHCP Release message\xa0\n 79 00:08:01,439 --> 00:08:09,279 IP address isn’t needed anymore. So, 192.168.0.167\xa0\n 80 00:08:10,399 --> 00:08:13,919 I used Wireshark to capture\xa0\n 81 00:08:14,959 --> 00:08:20,639 For the CCNA you should focus on learning the four\xa0\n 82 00:08:20,639 --> 00:08:26,560 a DHCP server, which I will show you next. But\xa0\n 83 00:08:27,680 --> 00:08:33,919 Of course, the message is an Ethernet frame so\xa0\n 84 00:08:33,919 --> 00:08:43,519 inside, from source IP address 192.168.0.167, the\xa0\n 85 00:08:44,720 --> 00:08:51,680 Inside is a UDP header, and notice the\xa0\n 86 00:08:52,879 --> 00:09:02,480 DHCP servers use UDP port 67 and DHCP clients use\xa0\n 87 00:09:02,480 --> 00:09:08,960 it’s the DHCP client, and the destination\xa0\n 88 00:09:11,120 --> 00:09:16,320 This is different than DNS, for example, in\xa0\n 89 00:09:16,320 --> 00:09:22,480 and the client uses a random ephemeral port.\xa0\n 90 00:09:22,480 --> 00:09:29,360 DHCP release message. The client IP is indicated\xa0\n 91 00:09:30,320 --> 00:09:36,560 DHCP has various options used for different\xa0\n 92 00:09:37,120 --> 00:09:43,600 indicates what kind of DHCP message it is. And\xa0\n 93 00:09:43,600 --> 00:09:49,840 part of DHCP messages, the magic cookie. Do a\xa0\n 94 00:09:50,720 --> 00:09:55,440 Now that I’ve released the IP address of\xa0\n 95 00:09:55,440 --> 00:10:03,040 get an IP address from the DHCP server. From the\xa0\n 96 00:10:03,039 --> 00:10:09,599 /RENEW. My PC contacts the DHCP server, and\xa0\n 97 00:10:10,559 --> 00:10:14,000 This process involves four\xa0\n 98 00:10:15,840 --> 00:10:21,840 The first message is the DHCP Discover message.\xa0\n 99 00:10:22,960 --> 00:10:28,000 Basically, it’s asking if there are any DHCP\xa0\n 100 00:10:28,000 --> 00:10:34,399 needs an IP address. Let’s use Wireshark to take\xa0\n 101 00:10:36,080 --> 00:10:42,080 Here it is. Here’s the Ethernet header. Notice\xa0\n 102 00:10:42,879 --> 00:10:49,120 My PC doesn’t know the IP address or MAC address\xa0\n 103 00:10:49,120 --> 00:10:54,480 if there is a DHCP server on the network, so\xa0\n 104 00:10:55,759 --> 00:11:00,960 Here’s the IPv4 header. Notice\xa0\n 105 00:11:02,080 --> 00:11:10,240 Basically, this means my PC doesn’t have an IP\xa0\n 106 00:11:10,240 --> 00:11:15,279 so it’s a broadcast message. Once again,\xa0\n 107 00:11:15,279 --> 00:11:23,600 client to the server, the source port is UDP\xa0\n 108 00:11:23,600 --> 00:11:29,600 the actual DHCP message. You don’t need to know\xa0\n 109 00:11:29,600 --> 00:11:36,480 just know their basic purpose. But here are a few\xa0\n 110 00:11:37,519 --> 00:11:42,799 Bootp is actually the predecessor of DHCP, but\xa0\n 111 00:11:43,759 --> 00:11:50,799 I just want to point out the value of ‘unicast’\xa0\n 112 00:11:50,799 --> 00:11:56,559 message is broadcast but this field says unicast.\xa0\n 113 00:11:57,840 --> 00:12:03,280 Then we can see here that the client IP\xa0\n 114 00:12:03,279 --> 00:12:09,199 an IP address yet. The client MAC is also\xa0\n 115 00:12:09,759 --> 00:12:14,159 notice they are different than the ones used in\xa0\n 116 00:12:15,279 --> 00:12:21,519 Let me just point out this option, Requested\xa0\n 117 00:12:21,519 --> 00:12:29,519 address 192.168.0.167, it requested that address\xa0\n 118 00:12:29,519 --> 00:12:35,519 might grant it that same IP address again. But if\xa0\n 119 00:12:36,799 --> 00:12:39,919 If this is the first time my PC is using DHCP\xa0\xa0 120 00:12:39,919 --> 00:12:44,479 it won’t request an IP address like this, it\xa0\n 121 00:12:45,840 --> 00:12:52,639 The next message is the DHCP Offer message, it is\xa0\n 122 00:12:52,639 --> 00:12:58,480 an address for the client to use, as well as other\xa0\n 123 00:13:00,399 --> 00:13:03,919 So let’s check out the DHCP\xa0\n 124 00:13:05,200 --> 00:13:10,400 First off, notice the Offer is sent as a\xa0\n 125 00:13:10,399 --> 00:13:13,679 since the server learned the client’s\xa0\n 126 00:13:14,799 --> 00:13:19,839 It’s also unicast at Layer 3, the destination\xa0\n 127 00:13:21,120 --> 00:13:24,960 This time the source and destination port\xa0\n 128 00:13:24,960 --> 00:13:31,600 from the server to the client. The source\xa0\n 129 00:13:32,639 --> 00:13:38,399 And here’s the Offer message. Let’s look at\xa0\n 130 00:13:38,399 --> 00:13:46,559 it says unicast. When my PC sent the DHCP Discover\xa0\n 131 00:13:47,440 --> 00:13:51,920 This means that the server will send its messages\xa0\n 132 00:13:52,799 --> 00:13:58,319 However, that’s not always the case. The DHCP\xa0\n 133 00:13:58,320 --> 00:14:04,800 either broadcast or unicast. It depends on the\xa0\n 134 00:14:04,799 --> 00:14:11,439 the Offer using unicast, so it did. If my PC told\xa0\n 135 00:14:11,440 --> 00:14:19,120 destination MAC of this message would be all F’s\xa0\n 136 00:14:20,480 --> 00:14:25,279 At this point in the DHCP process, the\xa0\n 137 00:14:26,080 --> 00:14:31,120 Some clients won’t accept unicast messages before\xa0\n 138 00:14:31,120 --> 00:14:37,840 why sometimes broadcast must be used instead of\xa0\n 139 00:14:37,840 --> 00:14:44,560 example option 51 indicates the lease time, option\xa0\n 140 00:14:45,120 --> 00:14:51,039 and option 3 is ‘router’, which tells the client\xa0\n 141 00:14:51,039 --> 00:14:58,319 to memorize these option numbers, definitely not\xa0\n 142 00:14:58,320 --> 00:15:04,320 Okay, the next message is the DHCP Request\xa0\n 143 00:15:04,320 --> 00:15:08,640 to the server, telling the server that it\xa0\n 144 00:15:09,600 --> 00:15:14,159 This is important, there may be multiple\xa0\n 145 00:15:14,159 --> 00:15:17,919 and all of them will reply to the\xa0\n 146 00:15:18,960 --> 00:15:22,879 So, the client has to tell which\xa0\n 147 00:15:22,879 --> 00:15:29,120 and request to use that IP address. Typically, the\xa0\n 148 00:15:31,120 --> 00:15:33,360 Let’s look at that Request message in Wireshark.\xa0\xa0 149 00:15:34,399 --> 00:15:38,879 The destination MAC is all Fs, so this\xa0\n 150 00:15:39,600 --> 00:15:44,080 If there are multiple DHCP servers on the\xa0\n 151 00:15:44,080 --> 00:15:49,440 message. One of the later fields will indicate\xa0\n 152 00:15:50,720 --> 00:15:56,879 The source IP is still 0.0.0.0, since the offered\xa0\n 153 00:15:57,679 --> 00:16:05,359 The destination is broadcast, 255.255.255.255.\xa0\n 154 00:16:05,360 --> 00:16:13,279 server, the source port is UDP 68 and the\xa0\n 155 00:16:13,279 --> 00:16:19,279 message. Here’s the flags field again, telling\xa0\n 156 00:16:19,279 --> 00:16:24,799 even though the client itself uses broadcast. And\xa0\n 157 00:16:25,919 --> 00:16:31,279 Notice that the server’s IP address is\xa0\n 158 00:16:31,279 --> 00:16:36,720 multiple DHCP servers on the local network, this\xa0\n 159 00:16:38,799 --> 00:16:45,279 Now the final message in the process, the DHCP\xa0\n 160 00:16:45,279 --> 00:16:51,519 to the client, confirming that the client may\xa0\n 161 00:16:51,519 --> 00:16:56,000 is received the client finally configures\xa0\n 162 00:16:57,759 --> 00:16:59,679 Here’s that Ack message in Wireshark.\xa0\xa0 163 00:17:00,799 --> 00:17:06,000 Notice that these messages from the server to the\xa0\n 164 00:17:06,000 --> 00:17:12,160 not broadcast. Let me point out once\xa0\n 165 00:17:12,160 --> 00:17:17,840 so that’s the source port, and the client uses\xa0\n 166 00:17:19,200 --> 00:17:25,039 And here’s the Ack message. The Bootp flags field\xa0\n 167 00:17:25,039 --> 00:17:32,879 requested unicast messages. Just like the DHCP\xa0\n 168 00:17:32,880 --> 00:17:39,280 broadcast or unicast, depending on what the client\xa0\n 169 00:17:39,279 --> 00:17:46,319 message. There are many different DHCP options, if\xa0\n 170 00:17:46,319 --> 00:17:51,200 page lists a bunch of them, and a quick Google\xa0\n 171 00:17:51,200 --> 00:17:56,799 their various functions. But that’s just\xa0\n 172 00:17:59,039 --> 00:18:06,240 Here’s a quick summary of that process. A common\xa0\n 173 00:18:06,240 --> 00:18:12,319 for Discover, Offer, Request, and Ack. Make\xa0\n 174 00:18:12,319 --> 00:18:18,799 client to server, server to client, and also which\xa0\n 175 00:18:18,799 --> 00:18:25,519 sent either broadcast or unicast. Also, here’s\xa0\n 176 00:18:25,519 --> 00:18:31,920 unicast from the client to the server. There are\xa0\n 177 00:18:32,559 --> 00:18:36,000 but if you know these message\xa0\n 178 00:18:38,640 --> 00:18:41,840 Next let me introduce the concept of DHCP Relay.\xa0\xa0 179 00:18:42,960 --> 00:18:48,079 Some network engineers might choose to\xa0\n 180 00:18:48,079 --> 00:18:55,359 for its connected LANs. However, large enterprises\xa0\n 181 00:18:55,359 --> 00:19:00,559 which will assign IP addresses to DHCP clients\xa0\n 182 00:19:01,759 --> 00:19:07,279 If the server is centralized, it won’t receive\xa0\n 183 00:19:08,160 --> 00:19:14,800 Remember, broadcast messages don’t leave the local\xa0\n 184 00:19:14,799 --> 00:19:21,680 fix this you can configure a router to act as a\xa0\n 185 00:19:21,680 --> 00:19:28,160 will forward the clients’ broadcast DHCP messages\xa0\n 186 00:19:29,599 --> 00:19:36,879 Let me use this network to demonstrate. PC1\xa0\n 187 00:19:36,880 --> 00:19:42,560 Discover message to ask DHCP servers on the\xa0\n 188 00:19:43,680 --> 00:19:50,880 However, in this case R1 isn’t a DHCP server.\xa0\n 189 00:19:51,440 --> 00:19:56,240 so R1 will need to forward any\xa0\n 190 00:19:58,400 --> 00:20:05,840 Let me demonstrate that visually. SRV1 is a\xa0\n 191 00:20:06,960 --> 00:20:15,440 PC1 broadcasts a DHCP Discover message to get an\xa0\n 192 00:20:15,440 --> 00:20:21,920 message to SRV1. Notice that the source address\xa0\n 193 00:20:22,559 --> 00:20:27,839 and the destination is SRV1’s IP\xa0\n 194 00:20:29,039 --> 00:20:35,359 Then SRV1 replies with the DHCP Offer, sending\xa0\n 195 00:20:35,359 --> 00:20:42,879 192.168.1.1. R1 then forwards it to\xa0\n 196 00:20:43,440 --> 00:20:51,039 and the message is either sent unicast to PC1 or\xa0\n 197 00:20:51,039 --> 00:20:59,599 and R1 relays it to SRV1. Finally SRV1 replies\xa0\n 198 00:20:59,599 --> 00:21:05,199 which configures the IP address it was\xa0\n 199 00:21:06,319 --> 00:21:11,200 So, that’s a quick overview of how DHCP\xa0\n 200 00:21:11,200 --> 00:21:16,080 configure a DHCP relay agent, you just need\xa0\n 201 00:21:17,039 --> 00:21:22,639 In the next section I’ll show you how to configure\xa0\n 202 00:21:22,640 --> 00:21:30,160 Cisco router as a DHCP server, and then how to\xa0\n 203 00:21:30,160 --> 00:21:34,080 Finally I’ll show you how to configure\xa0\n 204 00:21:36,559 --> 00:21:41,359 So, let me show you how to configure a\xa0\n 205 00:21:42,160 --> 00:21:50,680 Let’s use these two devices here, R1 and PC1. Here\xa0\n 206 00:21:50,680 --> 00:21:58,320 DCHP EXCLUDED-ADDRESS command to specify a range\xa0\n 207 00:21:58,319 --> 00:22:02,799 These are addresses you want to reserve,\xa0\n 208 00:22:02,799 --> 00:22:08,879 the local subnet. The first address in the command\xa0\n 209 00:22:08,880 --> 00:22:17,520 is the top of the range. So, this reserves all\xa0\n 210 00:22:18,799 --> 00:22:24,159 This command isn’t necessary, but it’s a good idea\xa0\n 211 00:22:24,160 --> 00:22:31,920 assigned to servers, network devices, or whatever.\xa0\n 212 00:22:31,920 --> 00:22:40,560 the pool name, to create a DHCP pool. What is a\xa0\n 213 00:22:40,559 --> 00:22:46,879 that can be assigned to DHCP clients, as well as\xa0\n 214 00:22:48,000 --> 00:22:53,839 You should create a separate DHCP pool for each\xa0\n 215 00:22:55,359 --> 00:23:03,679 In this case R1 is only acting as the DHCP server\xa0\n 216 00:23:03,680 --> 00:23:09,279 pool. Here’s where you actually configure the\xa0\n 217 00:23:10,000 --> 00:23:15,680 The command is NETWORK, followed by the network\xa0\n 218 00:23:15,680 --> 00:23:24,880 length. So, you can write /24 or 255.255.255.0,\xa0\n 219 00:23:24,880 --> 00:23:30,960 from 192.168.1.0/24 to clients, although it\xa0\n 220 00:23:32,319 --> 00:23:35,839 Then you can configure the DNS server\xa0\n 221 00:23:36,720 --> 00:23:44,559 So, in this case R1 would tell PC1 to use Google’s\xa0\n 222 00:23:45,839 --> 00:23:52,000 You can also configure the domain name of the\xa0\n 223 00:23:52,000 --> 00:23:58,160 is part of the domain ‘jeremysitlab.com’.\xa0\n 224 00:23:58,160 --> 00:24:06,160 What’s this? It’s the default gateway. So, R1 will\xa0\n 225 00:24:06,160 --> 00:24:14,960 their default gateway. You can also configure the\xa0\n 226 00:24:14,960 --> 00:24:21,600 5 hours, and 30 minutes. You can also enter LEASE\xa0\n 227 00:24:21,599 --> 00:24:28,719 not recommended. So, when PC1 comes online\xa0\n 228 00:24:28,720 --> 00:24:34,319 it will be assigned .11, the first available\xa0\n 229 00:24:36,079 --> 00:24:41,599 Let’s confirm. Here’s a really useful command\xa0\n 230 00:24:42,400 --> 00:24:49,600 SHOW IP DHCP BINDING. It shows all of the DHCP\xa0\n 231 00:24:50,640 --> 00:24:58,880 Here’s PC1, with an IP address of 192.168.1.11.\xa0\n 232 00:24:58,880 --> 00:25:05,440 lease expiration date and time, and the binding\xa0\n 233 00:25:05,440 --> 00:25:09,680 but we didn’t do that in this\xa0\n 234 00:25:10,480 --> 00:25:16,720 Here’s the domain name, jeremysitlab.com. Here’s\xa0\n 235 00:25:18,079 --> 00:25:21,359 Here we can see when the lease was\xa0\n 236 00:25:22,400 --> 00:25:28,640 Notice that the lease period is 5 hours and 30\xa0\n 237 00:25:28,640 --> 00:25:33,600 times on PC1 and R1 are different, but that’s\xa0\n 238 00:25:34,799 --> 00:25:38,480 And finally we can see the\xa0\n 239 00:25:38,480 --> 00:25:44,240 and DNS server. So, we successfully\xa0\n 240 00:25:45,599 --> 00:25:51,439 Now, how about DHCP relay agent configuration?\xa0\n 241 00:25:52,000 --> 00:25:58,319 SRV1 is a DHCP server and R1 will be a\xa0\n 242 00:25:59,680 --> 00:26:05,279 To configure it as a relay agent, first enter\xa0\n 243 00:26:05,279 --> 00:26:13,680 to the client devices. PC1 is connected to R1’s\xa0\n 244 00:26:13,680 --> 00:26:19,840 all you need is one command, IP HELPER-ADDRESS,\xa0\n 245 00:26:21,119 --> 00:26:24,719 Of course, make sure R1 actually\xa0\n 246 00:26:25,839 --> 00:26:31,199 If it doesn’t have a route, configure a static\xa0\n 247 00:26:32,559 --> 00:26:38,960 After configuring that I checked the interface\xa0\n 248 00:26:38,960 --> 00:26:47,120 ‘helper address’ is listed here, 192.168.10.10,\xa0\n 249 00:26:47,119 --> 00:26:54,799 to do to configure a router as a DHCP relay agent.\xa0\n 250 00:26:56,640 --> 00:27:01,440 Okay, one last thing you need to be able to\xa0\n 251 00:27:01,440 --> 00:27:07,519 be a DHCP client, meaning it can use DHCP to\xa0\n 252 00:27:08,559 --> 00:27:12,960 This is rare, as I mentioned earlier usually\xa0\n 253 00:27:12,960 --> 00:27:20,079 fixed IP address. However here’s how you\xa0\n 254 00:27:20,079 --> 00:27:28,240 on its G0/1 interface. From interface config\xa0\n 255 00:27:29,279 --> 00:27:37,759 That’s it, now R2 will broadcast a DHCP Discover\xa0\n 256 00:27:37,759 --> 00:27:45,599 it did, I checked with SHOW IP INTERFACE G0/1.\xa0\n 257 00:27:46,880 --> 00:27:52,560 Note that its G0/0 interface is still\xa0\n 258 00:27:54,799 --> 00:27:57,200 Here’s a summary of the commands\xa0\n 259 00:27:57,839 --> 00:28:00,399 A couple commands for the Windows command prompt,\xa0\xa0 260 00:28:00,400 --> 00:28:07,519 then Cisco IOS commands to configure a DHCP\xa0\n 261 00:28:08,640 --> 00:28:13,920 If you don’t remember any of these commands, go\xa0\n 262 00:28:13,920 --> 00:28:18,400 practice with some of these commands in today’s\xa0\n 263 00:28:20,720 --> 00:28:24,240 Before moving on to the quiz, let’s\xa0\n 264 00:28:25,279 --> 00:28:30,960 First, I introduced the purpose of DHCP. It\xa0\n 265 00:28:30,960 --> 00:28:36,400 configuration parameters, such as their IP\xa0\n 266 00:28:37,519 --> 00:28:44,480 I introduced the basic functions of DHCP. Make\xa0\n 267 00:28:44,480 --> 00:28:50,400 and Ack. You should also know the basic\xa0\n 268 00:28:51,759 --> 00:28:55,200 Finally I showed you how to\xa0\n 269 00:28:56,000 --> 00:29:02,720 First, how to configure a Cisco router as a DHCP\xa0\n 270 00:29:02,720 --> 00:29:09,120 DHCP client. Make sure to watch until the end\xa0\n 271 00:29:09,119 --> 00:29:16,639 Software’s ExSim for CCNA, the best practice exams\xa0\n 272 00:29:18,640 --> 00:29:23,840 What is the correct order of messages when a\xa0\n 273 00:29:24,720 --> 00:29:27,839 Here are the options. Pause the\xa0\n 274 00:29:31,680 --> 00:29:38,480 The answer is B, Discover, Offer, Request, Ack.\xa0\n 275 00:29:38,480 --> 00:29:43,120 remember D-O-R-A, DORA.\xa0\nOkay, let’s go to question 2. 276 00:29:45,440 --> 00:29:50,640 Which of the following Windows command prompt\xa0\n 277 00:29:50,640 --> 00:29:55,840 Discover message? Here are the options.\xa0\n 278 00:29:58,480 --> 00:30:06,319 The answer is D, IPCONFIG /RENEW. This will\xa0\n 279 00:30:06,319 --> 00:30:09,439 to get an IP address from any\xa0\n 280 00:30:10,559 --> 00:30:16,480 C, IPCONFIG /RELEASE will make the\xa0\n 281 00:30:16,480 --> 00:30:23,599 to release its current IP address. A and B are\xa0\n 282 00:30:26,319 --> 00:30:33,679 Examine the following DHCP Offer message that\xa0\n 283 00:30:33,680 --> 00:30:39,120 did SRV1 send it to? Here are the options.\xa0\n 284 00:30:42,960 --> 00:30:50,319 The answer is D, 255.255.255.255. How can\xa0\n 285 00:30:50,319 --> 00:30:56,559 I didn’t show the IP header? It’s here, the\xa0\n 286 00:30:58,160 --> 00:31:03,519 In the previous examples, this field was unicast,\xa0\n 287 00:31:03,519 --> 00:31:09,519 client. However in this case it is broadcast, so\xa0\n 288 00:31:10,559 --> 00:31:18,319 Therefore, the destination IP address is\xa0\n 289 00:31:20,480 --> 00:31:27,519 Which of the following DHCP messages can be sent\xa0\n 290 00:31:27,519 --> 00:31:32,879 the options. Note that this includes messages\xa0\n 291 00:31:32,880 --> 00:31:38,160 as well as messages that are always sent unicast.\xa0\n 292 00:31:42,000 --> 00:31:49,359 The answers are A, DHCP Ack, C,\xa0\n 293 00:31:50,400 --> 00:31:54,160 A and E are messages sent from\xa0\n 294 00:31:54,720 --> 00:31:59,839 and they can be sent using unicast if the\xa0\n 295 00:32:00,799 --> 00:32:07,759 C is sent by a DHCP client to its DHCP server, to\xa0\n 296 00:32:08,559 --> 00:32:15,919 It is sent unicast. B and D are always broadcast\xa0\n 297 00:32:18,160 --> 00:32:24,400 In which of the following situations would you\xa0\n 298 00:32:24,400 --> 00:32:29,759 are the options. Read them carefully, and\xa0\n 299 00:32:34,160 --> 00:32:40,880 Okay the answer is A, when the router is\xa0\n 300 00:32:40,880 --> 00:32:45,600 in the router’s connected LAN, and there is\xa0\n 301 00:32:46,720 --> 00:32:53,039 B, C, and D do not require the router to\xa0\n 302 00:32:53,039 --> 00:32:59,119 for the quiz. Now let’s take a look at a bonus\xa0\n 303 00:33:00,960 --> 00:33:03,519 Okay here's today's Boson ExSim practice question.\xa0\xa0 304 00:33:04,799 --> 00:33:10,240 You are the administrator for the network\xa0\n 305 00:33:10,240 --> 00:33:16,799 are provided by the DHCP server on NetworkB.\xa0\n 306 00:33:17,440 --> 00:33:21,680 Which of the following commands should you\xa0\n 307 00:33:21,680 --> 00:33:27,840 IP addresses from the DHCP server? Select the\xa0\n 308 00:33:28,400 --> 00:33:34,480 IP HELPER-ADDRESS commands, so which router\xa0\n 309 00:33:34,480 --> 00:33:39,599 be the IP address you enter in the command? Okay,\xa0\n 310 00:33:44,960 --> 00:33:51,680 Okay let's check. So, these clients\xa0\n 311 00:33:51,680 --> 00:33:57,120 or they want to be DHCP clients. So they\xa0\n 312 00:33:57,119 --> 00:34:04,959 So they will broadcast DHCP Discover messages\xa0\n 313 00:34:04,960 --> 00:34:14,159 a DHCP server, but we have to configure it as a\xa0\n 314 00:34:14,159 --> 00:34:19,839 and F have you issuing the command on RouterA.\xa0\n 315 00:34:21,440 --> 00:34:27,840 Okay, so what should be the IP address? The\xa0\n 316 00:34:27,840 --> 00:34:36,880 address of the DHCP server. So that is 10.10.3.5,\xa0\n 317 00:34:38,400 --> 00:34:43,039 And that is correct. So, you can\xa0\n 318 00:34:45,679 --> 00:34:51,359 including some explanation about the IP\xa0\n 319 00:34:57,360 --> 00:35:02,160 Okay and that's Boson's explanation, and they\xa0\n 320 00:35:02,159 --> 00:35:04,079 about the IP HELPER-ADDRESS command.\xa0\xa0 321 00:35:07,440 --> 00:35:12,159 Okay so that's Boson ExSim for the CCNA.\xa0\n 322 00:35:12,159 --> 00:35:16,239 exams for the CCNA, and they're the\xa0\n 323 00:35:16,880 --> 00:35:20,640 If you want to get Boson ExSim, follow\xa0\n 324 00:35:23,119 --> 00:35:25,440 There are supplementary materials for this video.\xa0\xa0 325 00:35:26,320 --> 00:35:30,480 There is a flashcard deck to use with\xa0\n 326 00:35:30,480 --> 00:35:33,760 be a packet tracer practice lab so\xa0\n 327 00:35:34,639 --> 00:35:40,079 That will be in the next video. Sign up for my\xa0\n 328 00:35:40,079 --> 00:35:43,840 and I’ll send you all of the flashcards\xa0\n 329 00:35:46,320 --> 00:35:52,160 Before finishing today’s video I want to\xa0\n 330 00:35:52,159 --> 00:35:59,119 please click the ‘Join’ button under the video.\xa0\n 331 00:35:59,119 --> 00:36:05,519 Marcel, Magrathea, Kone, Donald, C Mohd,\xa0\n 332 00:36:05,519 --> 00:36:12,000 Benjamin, Tshepiso, Justin, Prakaash, Nasir,\xa0\n 333 00:36:12,000 --> 00:36:18,719 Value, John, Funnydart, Velvijaykum, Mark, Yousif,\xa0\n 334 00:36:19,840 --> 00:36:24,000 Sorry if I pronounced your name incorrectly,\xa0\n 335 00:36:25,039 --> 00:36:31,599 This is the list of JCNP-level members at the\xa0\n 336 00:36:32,639 --> 00:36:40,319 If you signed up recently and your name isn’t\xa0\n 337 00:36:40,320 --> 00:36:43,440 Thank you for watching. Please\xa0\n 338 00:36:43,440 --> 00:36:48,159 like the video, leave a comment, and share the\xa0\n 339 00:36:49,199 --> 00:36:54,799 If you want to leave a tip, check the links in the\xa0\n 340 00:36:54,800 --> 00:37:01,440 and accept BAT, or Basic Attention Token, tips\xa0\n 29237

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