Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:00,880 --> 00:00:07,280
Welcome to Jeremy’s IT Lab. This is a free,\xa0\n
2
00:00:07,280 --> 00:00:12,720
videos, please subscribe to follow along with the\xa0\n
3
00:00:12,720 --> 00:00:16,640
and share the video to help spread this\xa0\n
4
00:00:17,839 --> 00:00:21,759
In this video we will cover\xa0\n
5
00:00:21,760 --> 00:00:24,880
and TFTP, Trivial File Transfer Protocol.\xa0\xa0
6
00:00:26,000 --> 00:00:32,320
As the names suggest, both of these protocols are\xa0\n
7
00:00:32,320 --> 00:00:38,000
exam topic 4.9, which states that you must be\xa0\n
8
00:00:38,000 --> 00:00:44,719
of TFTP and FTP in the network. So, make sure\xa0\n
9
00:00:44,719 --> 00:00:48,799
and make sure you know the differences between\xa0\n
10
00:00:50,560 --> 00:00:55,679
Here’s what we’ll cover in this video.\xa0\n
11
00:00:55,679 --> 00:01:02,560
and TFTP. The names tell you what their basic\xa0\n
12
00:01:02,560 --> 00:01:06,320
we’ll compare the two protocols to learn about\xa0\n
13
00:01:07,680 --> 00:01:13,440
Then I’ll introduce the various file systems\xa0\n
14
00:01:13,439 --> 00:01:19,920
files are stored on Cisco devices is important.\xa0\n
15
00:01:19,920 --> 00:01:25,840
TFTP in Cisco IOS. As always, watch until\xa0\n
16
00:01:25,840 --> 00:01:31,760
question from Boson Software’s ExSim for\xa0\n
17
00:01:33,519 --> 00:01:39,840
Here’s a quick summary of FTP and TFTP. FTP,\xa0\n
18
00:01:40,400 --> 00:01:45,600
and TFTP, which stands for Trivial File\xa0\n
19
00:01:45,599 --> 00:01:51,759
standard protocols used to transfer files over\xa0\n
20
00:01:52,879 --> 00:01:59,199
Clients can use FTP or TFTP to copy\xa0\n
21
00:02:00,159 --> 00:02:08,079
They can also use FTP or TFTP to copy files to a\xa0\n
22
00:02:08,080 --> 00:02:14,000
for FTP and TFTP is in the process of upgrading\xa0\n
23
00:02:15,199 --> 00:02:21,280
You can use FTP or TFTP on the device to\xa0\n
24
00:02:21,280 --> 00:02:28,000
reboot the device with the new IOS image. This is,\xa0\n
25
00:02:28,639 --> 00:02:32,879
They can be used to transfer all kinds of\xa0\n
26
00:02:33,919 --> 00:02:40,719
But for this video, we’ll use this example. So,\xa0\n
27
00:02:40,719 --> 00:02:48,639
cables or anything, we don’t need any details. So,\xa0\n
28
00:02:48,639 --> 00:02:54,719
network admin will download the new IOS image\xa0\n
29
00:02:54,719 --> 00:03:00,319
to a server that is reachable by the device he\xa0\n
30
00:03:00,319 --> 00:03:06,959
on the right. Finally, the network admin will\xa0\n
31
00:03:06,960 --> 00:03:14,480
into the flash memory of R1. The last step after\xa0\n
32
00:03:15,599 --> 00:03:20,639
So, later in this video I’ll show you how\xa0\n
33
00:03:20,639 --> 00:03:27,439
files using FTP and TFTP, and then how to reboot\xa0\n
34
00:03:29,599 --> 00:03:34,479
Okay, now let’s move on to talk about\xa0\n
35
00:03:35,840 --> 00:03:42,640
TFTP was first standardized in 1981.\xa0\n
36
00:03:42,639 --> 00:03:48,959
simpler I want to introduce it first. It was\xa0\n
37
00:03:48,960 --> 00:03:54,640
because it is simple and has only basic\xa0\n
38
00:03:54,639 --> 00:04:01,279
allows a client to copy a file to or from a\xa0\n
39
00:04:02,879 --> 00:04:09,519
As I said, it was released after FTP, but it’s\xa0\n
40
00:04:09,520 --> 00:04:15,120
tool to use when a lightweight, simple protocol\xa0\n
41
00:04:16,720 --> 00:04:21,440
TFTP doesn’t use any authentication,\xa0\n
42
00:04:21,439 --> 00:04:27,839
so servers will respond to all TFTP requests.\xa0\n
43
00:04:28,399 --> 00:04:34,560
Also, there is no encryption so all data is\xa0\n
44
00:04:34,560 --> 00:04:40,480
security, TFTP is best used in a controlled\xa0\n
45
00:04:41,519 --> 00:04:45,519
You probably shouldn’t use it to transfer\xa0\n
46
00:04:47,120 --> 00:04:53,759
TFTP servers listen on UDP port 69. So, when\xa0\n
47
00:04:54,319 --> 00:05:02,159
they will use UDP port 69 as the destination port.\xa0\n
48
00:05:02,160 --> 00:05:08,720
doesn’t provide reliability using retransmissions.\xa0\n
49
00:05:08,720 --> 00:05:14,480
connection and reliability features within\xa0\n
50
00:05:16,240 --> 00:05:23,079
First I’ll introduce how TFTP provides reliability\xa0\n
51
00:05:23,839 --> 00:05:29,839
TFTP data message is acknowledged. So, if the\xa0\n
52
00:05:29,839 --> 00:05:33,119
the server will send Ack messages,\xa0\n
53
00:05:34,160 --> 00:05:38,800
However, if the server is transferring a file\xa0\n
54
00:05:38,800 --> 00:05:45,040
messages, one for each data message from the\xa0\n
55
00:05:45,040 --> 00:05:49,920
message isn’t received in time, the waiting\xa0\n
56
00:05:50,959 --> 00:05:58,000
Let me demonstrate. The PC on the right is a\xa0\n
57
00:05:58,000 --> 00:06:04,160
server. To download a file from the server,\xa0\n
58
00:06:04,959 --> 00:06:08,719
The server then replies with a data\xa0\n
59
00:06:09,839 --> 00:06:14,560
The client replies with an Ack, but for some\xa0\n
60
00:06:15,839 --> 00:06:22,079
Because the client sent the Ack, it is waiting for\xa0\n
61
00:06:22,079 --> 00:06:27,759
the client retransmits the Ack message, which\xa0\n
62
00:06:27,759 --> 00:06:34,159
replies with the next data message, and the client\xa0\n
63
00:06:34,160 --> 00:06:40,160
until the client has received the entire file.\xa0\n
64
00:06:41,040 --> 00:06:46,480
The client and server alternately send a message\xa0\n
65
00:06:46,480 --> 00:06:52,800
wait for a reply, etc. The server will never\xa0\n
66
00:06:52,800 --> 00:07:00,000
except in the case of retransmission. So, this\xa0\n
67
00:07:00,000 --> 00:07:03,839
forward acknowledgment and sliding\xa0\n
68
00:07:05,680 --> 00:07:11,759
Next, let me introduce TFTP’s connections.\xa0\n
69
00:07:12,480 --> 00:07:16,560
First, the connection phase. The\xa0\n
70
00:07:16,560 --> 00:07:22,319
and the server responds back, initializing the\xa0\n
71
00:07:22,319 --> 00:07:28,639
data and acknowledgment messages are exchanged.\xa0\n
72
00:07:28,639 --> 00:07:34,959
is sent, terminating the connection. Let me\xa0\n
73
00:07:34,959 --> 00:07:40,799
and the server replies by sending the first data\xa0\n
74
00:07:41,600 --> 00:07:48,000
The client responds with an Ack, and there is an\xa0\n
75
00:07:48,000 --> 00:07:54,399
including the first data packet, are the data\xa0\n
76
00:07:54,399 --> 00:08:00,159
the client sends an Ack for the last data packet,\xa0\n
77
00:08:00,160 --> 00:08:06,400
TFTP doesn’t use TCP, it does have a basic way of\xa0\n
78
00:08:08,319 --> 00:08:13,759
Now I’m going to introduce an interesting part\xa0\n
79
00:08:13,759 --> 00:08:18,719
have to know for the CCNA exam, I just thought it\xa0\n
80
00:08:20,079 --> 00:08:23,519
As expected, when the client sends\xa0\n
81
00:08:23,519 --> 00:08:32,319
the destination port is UDP port 69 and the source\xa0\n
82
00:08:32,320 --> 00:08:38,560
port is called a ‘Transfer Identifier’, TID, and\xa0\n
83
00:08:39,519 --> 00:08:42,960
However, here’s where the functionality\xa0\n
84
00:08:43,600 --> 00:08:48,480
The server then also selects a random TID\xa0\n
85
00:08:49,200 --> 00:08:55,920
It doesn’t use port 69 as the source port.\xa0\n
86
00:08:55,919 --> 00:09:02,399
the destination port will be the server’s TID,\xa0\n
87
00:09:03,440 --> 00:09:08,720
The client sends a message to the server with a\xa0\n
88
00:09:09,679 --> 00:09:16,639
When the server replies, instead of using 69 as\xa0\n
89
00:09:16,639 --> 00:09:22,879
the client replies, and uses that random port as\xa0\n
90
00:09:23,759 --> 00:09:30,080
And the devices continue to use these two random\xa0\n
91
00:09:30,080 --> 00:09:36,560
well-known port of 69 is only used in the very\xa0\n
92
00:09:36,559 --> 00:09:42,559
I mentioned, this is beyond the scope of the CCNA,\xa0\n
93
00:09:45,039 --> 00:09:49,839
Okay, so that was a brief overview of TFTP\xa0\n
94
00:09:50,720 --> 00:09:57,920
Next I’ll introduce FTP and then we’ll compare\xa0\n
95
00:09:58,720 --> 00:10:04,160
This is actually before TCP and\xa0\n
96
00:10:04,159 --> 00:10:10,319
although it has of course been updated\xa0\n
97
00:10:10,879 --> 00:10:17,840
instead of just a single well-known port. In\xa0\n
98
00:10:18,399 --> 00:10:23,519
usernames and passwords are used for\xa0\n
99
00:10:23,519 --> 00:10:28,720
there is no encryption. Everything is sent in\xa0\n
100
00:10:30,159 --> 00:10:37,759
For greater security, FTPS, FTP over SSL/TLS,\xa0\n
101
00:10:37,759 --> 00:10:46,960
FTP Secure. Another option is SSH File Transfer\xa0\n
102
00:10:46,960 --> 00:10:53,040
FTP, adding greater security, whereas SFTP is a\xa0\n
103
00:10:54,320 --> 00:10:59,040
FTP is more complex than TFTP and\xa0\n
104
00:10:59,039 --> 00:11:04,879
but clients can also navigate file directories,\xa0\n
105
00:11:05,919 --> 00:11:11,120
In TFTP, the client could only tell the server\xa0\n
106
00:11:11,759 --> 00:11:18,240
it couldn’t even ask the server ‘what files do\xa0\n
107
00:11:18,240 --> 00:11:23,519
the server to perform FTP’s functions.\xa0\n
108
00:11:23,519 --> 00:11:27,840
and you can view a list of them here\xa0\n
109
00:11:28,799 --> 00:11:34,319
As I said, FTP uses two different\xa0\n
110
00:11:35,279 --> 00:11:42,319
That’s because FTP uses two types of connections.\xa0\n
111
00:11:42,320 --> 00:11:48,879
is established and used to send FTP commands. The\xa0\n
112
00:11:48,879 --> 00:11:54,240
action, such as retrieving a file from the server,\xa0\n
113
00:11:55,600 --> 00:11:59,360
However, the actual data transfer isn’t\xa0\n
114
00:12:00,480 --> 00:12:06,240
When files or data are to be transferred,\xa0\n
115
00:12:06,240 --> 00:12:12,960
are established and terminated as needed. So, let\xa0\n
116
00:12:12,960 --> 00:12:19,120
initiates the TCP connection, and the usual\xa0\n
117
00:12:20,320 --> 00:12:26,080
Now the FTP control connection is established.\xa0\n
118
00:12:26,639 --> 00:12:32,639
for example to say that the PC wants to get\xa0\n
119
00:12:32,639 --> 00:12:37,840
acknowledge the command. But now we need an FTP\xa0\n
120
00:12:39,279 --> 00:12:43,839
There are actually two different modes which\xa0\n
121
00:12:45,039 --> 00:12:50,159
The default method of establishing FTP data\xa0\n
122
00:12:50,159 --> 00:12:56,559
initiates the TCP connection. So, as you can see\xa0\n
123
00:12:56,559 --> 00:13:02,799
SYN message, is from the server to the client.\xa0\n
124
00:13:02,799 --> 00:13:09,039
and the data can be exchanged. So, the point I\xa0\n
125
00:13:09,039 --> 00:13:14,879
the server initiates the data connection. Also,\xa0\n
126
00:13:14,879 --> 00:13:19,840
throughout this whole process. It isn’t\xa0\n
127
00:13:21,200 --> 00:13:25,360
So, active is considered the ‘normal’\xa0\n
128
00:13:26,240 --> 00:13:32,639
However, notice the network has changed. The\xa0\n
129
00:13:32,639 --> 00:13:38,480
mode, the client initiates the data connection.\xa0\n
130
00:13:38,480 --> 00:13:44,000
a firewall, which could block the incoming\xa0\n
131
00:13:44,000 --> 00:13:51,120
message in the TCP connection is initiated by the\xa0\n
132
00:13:51,120 --> 00:13:55,679
but it would block the message if the server\xa0\n
133
00:13:57,039 --> 00:14:03,439
Once the FTP data connection is established, the\xa0\n
134
00:14:03,440 --> 00:14:09,200
to remember. Firewalls usually don’t permit\xa0\n
135
00:14:10,080 --> 00:14:15,120
In this case, FTP passive mode is used and\xa0\n
136
00:14:15,120 --> 00:14:20,480
initiates the TCP connection. By the way,\xa0\n
137
00:14:20,480 --> 00:14:25,840
firewalls, consider studying for the CCNP security\xa0\n
138
00:14:28,080 --> 00:14:34,400
Okay, that’s enough about FTP. FTP is more\xa0\n
139
00:14:34,399 --> 00:14:38,959
time to really cover all there is to know\xa0\n
140
00:14:38,960 --> 00:14:47,920
now. So let’s briefly compare FTP and TFTP. FTP\xa0\n
141
00:14:48,799 --> 00:14:53,679
Port 20 is used for data connections, and\xa0\n
142
00:14:54,879 --> 00:14:59,840
TFTP on the other hand uses UDP port\xa0\n
143
00:15:00,399 --> 00:15:03,679
although there is a basic form of\xa0\n
144
00:15:05,519 --> 00:15:12,480
FTP clients can use commands to perform various\xa0\n
145
00:15:12,480 --> 00:15:18,560
clients can only copy files to or from the\xa0\n
146
00:15:19,679 --> 00:15:26,159
FTP uses usernames and passwords to limit who\xa0\n
147
00:15:26,159 --> 00:15:33,279
has no authentication system at all. So, FTP is\xa0\n
148
00:15:36,399 --> 00:15:42,399
Okay, let’s move on to look at the IOS file\xa0\n
149
00:15:42,399 --> 00:15:46,799
introduction, just this slide, but I want\xa0\n
150
00:15:46,799 --> 00:15:55,359
at transferring files from TFTP and FTP servers\xa0\n
151
00:15:55,360 --> 00:16:01,360
of controlling how data is stored and retrieved.\xa0\n
152
00:16:01,360 --> 00:16:08,080
system. You can view the file systems of a Cisco\xa0\n
153
00:16:08,879 --> 00:16:14,559
And here’s some sample output. Note that there\xa0\n
154
00:16:14,559 --> 00:16:19,839
a few because the output was too long. And note\xa0\n
155
00:16:20,960 --> 00:16:27,360
The disk type refers to storage devices such as\xa0\n
156
00:16:27,360 --> 00:16:36,159
IOS file itself is stored. When the device boots\xa0\n
157
00:16:36,159 --> 00:16:42,159
The opaque disk type is used for specific internal\xa0\n
158
00:16:42,159 --> 00:16:51,199
systems, not actual separate storage devices. The\xa0\n
159
00:16:51,200 --> 00:16:56,480
of the device. Normal RAM loses all of\xa0\n
160
00:16:57,360 --> 00:17:05,839
However NVRAM does not. The startup-config file is\xa0\n
161
00:17:06,480 --> 00:17:13,440
This represents external file systems, for\xa0\n
162
00:17:13,440 --> 00:17:18,240
you’ll find any questions about these file\xa0\n
163
00:17:18,240 --> 00:17:25,039
in the newest version of the CCNA. So, we’ll\xa0\n
164
00:17:25,039 --> 00:17:31,839
look at how to use TFTP and FTP to transfer\xa0\n
165
00:17:33,599 --> 00:17:40,399
So, here’s a very simple network we’ll use\xa0\n
166
00:17:40,400 --> 00:17:48,320
router running Cisco IOS, and we have downloaded\xa0\n
167
00:17:48,319 --> 00:17:53,839
is a server running both TFTP and FTP, and\xa0\n
168
00:17:53,839 --> 00:18:01,919
version of IOS from SRV1 onto R1. First, you can\xa0\n
169
00:18:01,920 --> 00:18:11,200
SHOW VERSION. Here you can see the image name,\xa0\n
170
00:18:11,200 --> 00:18:20,799
supports cryptographic features like SSH. Then\xa0\n
171
00:18:20,799 --> 00:18:28,079
video I’ll talk about the naming conventions of\xa0\n
172
00:18:28,079 --> 00:18:32,240
output of SHOW VERSION is actually quite\xa0\n
173
00:18:33,519 --> 00:18:38,480
By the way, for simplicity’s sake I’m actually\xa0\n
174
00:18:38,480 --> 00:18:45,120
although usually I use GNS3. You can also\xa0\n
175
00:18:46,160 --> 00:18:52,400
Here it is, and you can see the IOS image\xa0\n
176
00:18:52,400 --> 00:18:59,680
TFTP to copy a new version of IOS from SRV1\xa0\n
177
00:18:59,680 --> 00:19:04,240
with the new version of IOS, and then\xa0\n
178
00:19:06,240 --> 00:19:12,799
And here’s how to copy the file using TFTP. The\xa0\n
179
00:19:12,799 --> 00:19:18,879
destination. By using TFTP as the source,\xa0\n
180
00:19:18,880 --> 00:19:24,640
a TFTP server. The router then asks you\xa0\n
181
00:19:25,680 --> 00:19:31,920
This is where you enter the TFTP server’s IP\xa0\n
182
00:19:31,920 --> 00:19:38,640
of the file you want to download. Note that you\xa0\n
183
00:19:38,640 --> 00:19:44,320
of asking a server ‘what files do you have?’. I\xa0\n
184
00:19:44,319 --> 00:19:49,679
so I entered it. Then you’re asked what name\xa0\n
185
00:19:50,720 --> 00:19:55,839
You can just hit enter to accept the default name,\xa0\n
186
00:19:56,720 --> 00:20:01,360
And that’s it, the file is then transferred\xa0\n
187
00:20:03,200 --> 00:20:09,680
I used SHOW FLASH to check the contents of flash.\xa0\n
188
00:20:09,680 --> 00:20:16,640
copied from the TFTP server. Now, how do we make\xa0\n
189
00:20:16,640 --> 00:20:23,520
the old file? From global config mode, use the\xa0\n
190
00:20:24,640 --> 00:20:28,960
Note that, if you don’t use this command\xa0\n
191
00:20:28,960 --> 00:20:34,720
file it finds in flash. So, you should use this\xa0\n
192
00:20:35,920 --> 00:20:41,279
After that, make sure you save the configuration\xa0\n
193
00:20:41,279 --> 00:20:47,839
command won’t take effect. Then simply use\xa0\n
194
00:20:49,519 --> 00:20:54,799
After the device finished restarting I used SHOW\xa0\n
195
00:20:55,440 --> 00:21:03,200
and R1 is now using the new version, 15.5,\xa0\n
196
00:21:03,200 --> 00:21:08,240
delete that old version of IOS. We don’t need it\xa0\n
197
00:21:09,440 --> 00:21:13,600
The command to delete a file is\xa0\n
198
00:21:14,640 --> 00:21:20,800
It asks you to confirm, so I did. And then I\xa0\n
199
00:21:21,519 --> 00:21:26,879
and now the old file is gone.\xa0\n
200
00:21:26,880 --> 00:21:34,960
to copy an IOS file to R1 from a TFTP server. We\xa0\n
201
00:21:34,960 --> 00:21:40,720
and then reloaded R1. Finally, we deleted\xa0\n
202
00:21:42,720 --> 00:21:47,759
Now let’s take a look at FTP. I’ll only show\xa0\n
203
00:21:47,759 --> 00:21:53,119
server to the router, because the rest is\xa0\n
204
00:21:53,119 --> 00:21:58,319
the other steps such as the BOOT SYSTEM command,\xa0\n
205
00:22:00,079 --> 00:22:03,759
First, you should configure the username\xa0\n
206
00:22:03,759 --> 00:22:09,839
connecting to an FTP server. Remember, FTP\xa0\n
207
00:22:10,960 --> 00:22:14,559
So, this same username and password\xa0\n
208
00:22:16,079 --> 00:22:22,079
In this case, I configured the username and\xa0\n
209
00:22:22,079 --> 00:22:29,839
is basically the same. COPY FTP: FLASH:, and then\xa0\n
210
00:22:29,839 --> 00:22:36,319
name, and the name you want to save the file\xa0\n
211
00:22:36,319 --> 00:22:42,559
upgrade the IOS we could use the same BOOT SYSTEM\xa0\n
212
00:22:44,799 --> 00:22:49,519
Okay, here are the commands we just used.\xa0\n
213
00:22:49,519 --> 00:22:54,000
go back in the video to review. I\xa0\n
214
00:22:54,000 --> 00:23:00,720
COPY command. This actually isn’t the first time\xa0\n
215
00:23:00,720 --> 00:23:06,720
it as COPY RUNNING-CONFIG STARTUP-CONFIG, as a\xa0\n
216
00:23:07,599 --> 00:23:12,879
It copies the source, the current running\xa0\n
217
00:23:15,119 --> 00:23:21,839
Okay, before the quiz let’s review what we\xa0\n
218
00:23:22,880 --> 00:23:26,080
Basically, they allow you to\xa0\n
219
00:23:26,079 --> 00:23:35,279
over a network. Then I gave an overview of TFTP\xa0\n
220
00:23:35,279 --> 00:23:39,839
and useful for quickly transferring\xa0\n
221
00:23:39,839 --> 00:23:43,119
but has no advanced functionalities\xa0\n
222
00:23:44,640 --> 00:23:50,880
FTP has much greater functionality, and includes\xa0\n
223
00:23:50,880 --> 00:23:56,800
use FTPS, it has many other security benefits,\xa0\n
224
00:23:58,400 --> 00:24:05,600
Then I very briefly introduced the file systems in\xa0\n
225
00:24:05,599 --> 00:24:12,240
FTP to get a new IOS file from a server, and then\xa0\n
226
00:24:13,440 --> 00:24:17,840
Once again, make sure to watch until the end\xa0\n
227
00:24:17,839 --> 00:24:24,959
Software’s ExSim, the best practice exams for the\xa0\n
228
00:24:27,119 --> 00:24:30,399
Which of the following\xa0\n
229
00:24:30,400 --> 00:24:34,000
Select two. Pause the video\xa0\nnow to think about the answers.
230
00:24:38,000 --> 00:24:42,160
The answers are B, FTP control\xa0\n
231
00:24:42,799 --> 00:24:46,559
and D, FTP data connections use TCP port 20.\xa0\xa0
232
00:24:47,839 --> 00:24:55,439
FTP uses TCP to provide reliable communications\xa0\n
233
00:24:55,440 --> 00:25:01,600
control connection for sending FTP commands and\xa0\n
234
00:25:01,599 --> 00:25:07,679
20 to establish data connections for the actual\xa0\n
235
00:25:09,440 --> 00:25:14,480
Which of the following commands can be used to\xa0\n
236
00:25:14,480 --> 00:25:19,360
to the local device’s flash storage? Pause\xa0\n
237
00:25:23,680 --> 00:25:31,759
The answer is A, COPY TFTP: FLASH:. The command\xa0\n
238
00:25:31,759 --> 00:25:37,839
so this copies a file from a TFTP server\xa0\n
239
00:25:40,160 --> 00:25:44,800
R1 is behind a firewall and wants to\xa0\n
240
00:25:45,759 --> 00:25:50,240
Which of the following statements is true?\xa0\n
241
00:25:55,279 --> 00:26:00,319
The answer is C, R1 should use FTP\xa0\n
242
00:26:01,440 --> 00:26:05,440
Active and passive mode only\xa0\n
243
00:26:05,440 --> 00:26:11,200
because the client always initiates the control\xa0\n
244
00:26:11,200 --> 00:26:15,279
the data connection. But in passive mode,\xa0\n
245
00:26:16,000 --> 00:26:24,319
When a client is behind a firewall, passive mode\xa0\n
246
00:26:24,319 --> 00:26:29,599
Which type of file system is used to store the\xa0\n
247
00:26:30,640 --> 00:26:32,720
Pause the video now to think about the answer.
248
00:26:36,960 --> 00:26:44,240
The answer is D, NVRAM. NVRAM, non-volatile\xa0\n
249
00:26:44,240 --> 00:26:49,200
even after the device loses power. It\xa0\n
250
00:26:49,200 --> 00:26:52,799
of the device. Okay, let’s go to question 5.
251
00:26:55,519 --> 00:26:59,680
Which of the following functions\xa0\n
252
00:26:59,680 --> 00:27:05,840
(select two). Pause the video\xa0\n
253
00:27:08,880 --> 00:27:14,960
The answers are B, create a new directory on a\xa0\n
254
00:27:16,079 --> 00:27:20,079
TFTP is very simple and only\xa0\n
255
00:27:20,079 --> 00:27:26,960
to or from a server, it has no other functions.\xa0\n
256
00:27:26,960 --> 00:27:33,920
a look at a bonus question from\xa0\n
257
00:27:33,920 --> 00:27:38,960
Okay here's today's Boson ExSim practice\xa0\n
258
00:27:38,960 --> 00:27:44,559
layer protocols use UDP for unsynchronized,\xa0\n
259
00:27:45,680 --> 00:27:49,519
So, here are the choices. Pause the\xa0\n
260
00:27:54,319 --> 00:28:01,759
Okay let's check. So, I think the correct answers\xa0\n
261
00:28:01,759 --> 00:28:07,920
connectionless data transfer. Now, it says\xa0\n
262
00:28:07,920 --> 00:28:10,960
some basic kind of connection\xa0\n
263
00:28:11,920 --> 00:28:19,200
But it doesn't use TCP connections at Layer 4, so\xa0\n
264
00:28:19,200 --> 00:28:24,640
Simple Network Management Protocol. As we covered\xa0\n
265
00:28:24,640 --> 00:28:33,759
not TCP-based, it doesn't use TCP connections.\xa0\n
266
00:28:33,759 --> 00:28:39,119
which we don't cover in the course, but that is\xa0\n
267
00:28:40,240 --> 00:28:46,799
Okay, so I will click on show answer. And that\xa0\n
268
00:28:47,359 --> 00:28:53,039
which just outlines the different protocols and\xa0\n
269
00:28:53,039 --> 00:29:03,039
video now to read Boson's explanation. Okay, so\xa0\n
270
00:29:03,039 --> 00:29:09,440
Software's ExSim for CCNA. These are without\xa0\n
271
00:29:09,440 --> 00:29:13,840
So, if you want to get Boson ExSim, please\xa0\n
272
00:29:17,200 --> 00:29:19,600
There are supplementary materials for this video.\xa0\xa0
273
00:29:20,480 --> 00:29:23,440
There is a flashcard deck to\xa0\n
274
00:29:24,400 --> 00:29:28,640
There will also be a packet tracer practice\xa0\n
275
00:29:29,440 --> 00:29:35,200
That will be in the next video. Sign up for my\xa0\n
276
00:29:35,200 --> 00:29:39,840
and I’ll send you all of the flashcards\xa0\n
277
00:29:41,119 --> 00:29:45,679
Before finishing today’s video I want\xa0\n
278
00:29:46,400 --> 00:29:53,519
To join, please click the ‘Join’ button under the\xa0\n
279
00:29:53,519 --> 00:30:01,359
Raj, Kenneth, Seamus, H W, Brandon, Samil, Aaron,\xa0\n
280
00:30:01,359 --> 00:30:06,879
Junhong, Benjamin, Tshepiso, Justin, Prakaash,\xa0\n
281
00:30:06,880 --> 00:30:13,120
Value, John, Funnydart, Velvijaykum, Mark, Yousif,\xa0\n
282
00:30:14,000 --> 00:30:17,920
Sorry if I pronounced your name incorrectly,\xa0\n
283
00:30:18,960 --> 00:30:24,960
This is the list of JCNP-level members at the\xa0\n
284
00:30:25,759 --> 00:30:30,799
If you signed up recently and your name isn’t\xa0\n
285
00:30:32,799 --> 00:30:36,799
Thank you for watching. Please subscribe\xa0\n
286
00:30:36,799 --> 00:30:40,639
leave a comment, and share the video\xa0\n
287
00:30:41,680 --> 00:30:47,279
If you want to leave a tip, check the links in the\xa0\n
288
00:30:47,279 --> 00:30:53,839
and accept BAT, or Basic Attention Token, tips\xa0\n
24628
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.