Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,409 --> 00:00:07,520
Welcome to Jeremy’s IT Lab. This is a free,\n
2
00:00:07,519 --> 00:00:12,359
these videos, please subscribe to follow along\n
3
00:00:12,359 --> 00:00:17,350
a comment, and share the video to help spread\n
4
00:00:18,870 --> 00:00:24,330
In this video we will cover Syslog. Syslog\n
5
00:00:24,329 --> 00:00:30,129
events that happen on the device, for example\n
6
00:00:30,129 --> 00:00:36,030
relationships going up or down, etc. The log\n
7
00:00:36,030 --> 00:00:40,960
CLI of the device to inform you of important\n
8
00:00:40,960 --> 00:00:47,539
stored in the device or on an external server\n
9
00:00:47,539 --> 00:00:53,739
so understanding Syslog is essential for network\n
10
00:00:53,738 --> 00:00:59,378
in exam topic 4.5, which says you must be\n
11
00:00:59,378 --> 00:01:04,489
including facilities and levels. In this video\n
12
00:01:06,859 --> 00:01:12,310
Here’s what we’ll cover in this video.\n
13
00:01:12,311 --> 00:01:18,250
and outline how it works. Then I’ll introduce\n
14
00:01:18,250 --> 00:01:22,680
have a standard format, and it’s important\n
15
00:01:22,680 --> 00:01:28,850
understand Syslog messages. Then I’ll introduce\n
16
00:01:28,849 --> 00:01:33,799
levels. You probably aren’t sure exactly\n
17
00:01:33,799 --> 00:01:37,819
yet, but they were both mentioned in the exam\n
18
00:01:37,819 --> 00:01:45,789
video. Then I’ll introduce some basic Syslog\n
19
00:01:45,790 --> 00:01:49,810
isn’t mentioned in the exam topics, but\n
20
00:01:49,810 --> 00:01:56,359
practice. So, I’ll go over the basic Syslog\n
21
00:01:56,359 --> 00:02:00,989
until the end of the video for a bonus practice\n
22
00:02:00,989 --> 00:02:05,619
CCNA, the best practice exams for the CCNA.
23
00:02:05,620 --> 00:02:11,710
Here’s a quick overview of Syslog. Syslog\n
24
00:02:11,710 --> 00:02:17,710
logging. On network devices, Syslog can be\n
25
00:02:17,710 --> 00:02:22,840
status, changes in OSPF neighbor status, or\n
26
00:02:22,840 --> 00:02:30,099
like EIGRP and BGP, also system restarts,\n
27
00:02:30,099 --> 00:02:34,849
so I’m not going to try to list them all.\n
28
00:02:34,849 --> 00:02:40,900
you configure the device, saved in the device’s\n
29
00:02:40,900 --> 00:02:46,010
I’m sure you’ve seen these messages as\n
30
00:02:46,009 --> 00:02:52,069
example, I used NO SHUTDOWN to enable a router\n
31
00:02:52,069 --> 00:02:58,039
are displayed, indicating that the interface\n
32
00:02:58,039 --> 00:03:04,419
when troubleshooting issues, examining the\n
33
00:03:04,419 --> 00:03:10,099
both used for monitoring and troubleshooting\n
34
00:03:10,099 --> 00:03:14,979
but their functionalities are quite different.\n
35
00:03:14,979 --> 00:03:20,919
give a brief summary of how Syslog and SNMP\n
36
00:03:20,919 --> 00:03:25,479
Now let’s take a look at the Syslog message\n
37
00:03:25,479 --> 00:03:31,079
to see in a standard Syslog message. Let’s\n
38
00:03:31,080 --> 00:03:36,719
number indicating the order, the sequence,\n
39
00:03:36,719 --> 00:03:42,659
indicating at what time the message was generated.\n
40
00:03:42,659 --> 00:03:47,709
especially when comparing the logs of different\n
41
00:03:47,709 --> 00:03:52,479
time thanks to NTP, you can use these timestamps\n
42
00:03:52,479 --> 00:03:58,318
on different devices. Note that these two\n
43
00:03:58,318 --> 00:04:04,379
on the device’s configuration. Sequence\n
44
00:04:04,379 --> 00:04:10,818
are very important and I highly recommend\n
45
00:04:10,818 --> 00:04:15,848
is the facility, this is a value that indicates\n
46
00:04:15,848 --> 00:04:22,418
message. For example, if OSPF generated the\n
47
00:04:22,418 --> 00:04:28,659
would be displayed in this field. Next is\n
48
00:04:28,660 --> 00:04:35,740
of the event. Some messages are just informational,\n
49
00:04:35,740 --> 00:04:41,230
Other messages indicate something much more\n
50
00:04:41,230 --> 00:04:46,370
There are 8 severity levels, and you’ll\n
51
00:04:46,370 --> 00:04:51,490
is a mnemonic, which is a short code for the\n
52
00:04:51,490 --> 00:04:56,720
example, if the facility is OSPF, this mnemonic\n
53
00:04:56,720 --> 00:05:03,400
is about OSPF neighbor adjacencies. If the\n
54
00:05:03,399 --> 00:05:09,629
that the message is about an interface going\n
55
00:05:09,629 --> 00:05:13,560
This is the detailed information about the\n
56
00:05:15,740 --> 00:05:19,629
Before looking at some examples of Syslog\n
57
00:05:19,629 --> 00:05:25,490
severity levels. As I briefly mentioned, these\n
58
00:05:25,490 --> 00:05:31,280
event is. For example, something like a serious\n
59
00:05:31,279 --> 00:05:37,530
neighbor moving to the FULL state. There are\n
60
00:05:37,531 --> 00:05:43,680
severity level has a number, 0 being the most\n
61
00:05:43,680 --> 00:05:49,259
level also has a keyword, which is a name\n
62
00:05:49,259 --> 00:05:55,370
description. I took these descriptions directly\n
63
00:05:55,370 --> 00:06:02,090
is level 0, emergency, events which render\n
64
00:06:02,089 --> 00:06:08,509
events for which action must be taken immediately.\n
65
00:06:08,509 --> 00:06:13,810
2 is called critical, and the description\n
66
00:06:13,810 --> 00:06:20,370
for level 3, error, and level 4, warning.\n
67
00:06:20,370 --> 00:06:27,060
representing a ‘normal but significant condition’.\n
68
00:06:27,060 --> 00:06:33,160
for level 5 is ‘Notice’, but in the CLI\n
69
00:06:33,160 --> 00:06:40,520
make sure you know of both names. Notice and\n
70
00:06:40,519 --> 00:06:46,359
and then finally the least severe level, level\n
71
00:06:46,360 --> 00:06:52,090
messages. Now, the RFC doesn’t give detailed\n
72
00:06:52,089 --> 00:06:57,989
into each severity level. So, each vendor\n
73
00:06:57,990 --> 00:07:04,800
a quote from the RFC. Because severities are\n
74
00:07:04,800 --> 00:07:09,639
that means a Syslog server) should not assume\n
75
00:07:09,639 --> 00:07:16,519
of severity. That’s from RFC 5424, The Syslog\n
76
00:07:16,519 --> 00:07:21,459
you Google it. Basically it means that you\n
77
00:07:21,459 --> 00:07:26,699
level to be exactly the same as a Juniper\n
78
00:07:26,699 --> 00:07:32,649
Each vendor may interpret each level differently.\n
79
00:07:32,649 --> 00:07:38,569
the levels and keywords. You should know that\n
80
00:07:38,569 --> 00:07:44,829
6, for example. If you want some help remembering\n
81
00:07:44,829 --> 00:07:50,709
Engineer Will Need Ice cream Daily. Just like\n
82
00:07:50,709 --> 00:07:55,000
ways to remember these levels post them in\nthe comment section!
83
00:07:55,000 --> 00:08:02,209
Let’s look at some examples of Syslog messages.\n
84
00:08:02,209 --> 00:08:08,198
indicating the month, date, hours, minutes,\n
85
00:08:08,199 --> 00:08:13,520
is no sequence number before the timestamp.\n
86
00:08:13,519 --> 00:08:19,129
and timestamp fields may or may not be displayed,\n
87
00:08:19,129 --> 00:08:26,269
Here’s the facility, LINK. And the severity\n
88
00:08:26,269 --> 00:08:31,709
us the message is about an interface going\n
89
00:08:31,709 --> 00:08:38,019
which tells us exactly what happened. Interface\n
90
00:08:38,019 --> 00:08:43,418
that’s an example Syslog message. Make sure\n
91
00:08:43,418 --> 00:08:49,000
message. For example, you might be asked,\n
92
00:08:49,000 --> 00:08:53,990
You should be able to answer ‘LINK’. Or\n
93
00:08:53,990 --> 00:08:59,370
able to answer ‘3’ or ‘error’, depending\n
94
00:08:59,370 --> 00:09:03,838
judging by the exam topics list those seem\n
95
00:09:03,839 --> 00:09:10,230
the exam. Okay, let’s see some more examples.\n
96
00:09:10,230 --> 00:09:17,528
moving to the FULL state. The facility is\n
97
00:09:17,528 --> 00:09:26,360
level, message. The mnemonic is A D J C H\n
98
00:09:26,360 --> 00:09:31,220
and for this one I turned on the sequence\n
99
00:09:31,220 --> 00:09:37,110
In this case the facility is SYS for system,\n
100
00:09:37,110 --> 00:09:44,039
keywords for level 5, ‘notice’ or ‘notification’.\n
101
00:09:44,039 --> 00:09:49,948
of ‘configured from console by jeremy on\n
102
00:09:49,948 --> 00:09:56,109
you exit global config mode and return to\n
103
00:09:56,110 --> 00:10:01,550
this time I just changed the timezone from\n
104
00:10:01,549 --> 00:10:07,250
Again, the facility is SYS, but this time\n
105
00:10:07,250 --> 00:10:13,730
level 6? It’s ‘informational’. And the\n
106
00:10:13,730 --> 00:10:18,240
sure you can identify each part of a Syslog\n
107
00:10:19,360 --> 00:10:24,818
Soon we’ll take a look at how to configure\n
108
00:10:24,818 --> 00:10:30,578
an overview of the different locations Syslog\n
109
00:10:30,578 --> 00:10:35,359
line. This means that Syslog messages will\n
110
00:10:35,360 --> 00:10:41,919
via the console port. By default, all messages,\n
111
00:10:41,919 --> 00:10:47,958
when connected to the CLI via the device’s\n
112
00:10:47,958 --> 00:10:52,438
when you click on a device and go to the CLI\n
113
00:10:52,438 --> 00:10:58,039
via the console port of the device. So, that’s\n
114
00:10:58,039 --> 00:11:05,328
devices in packet tracer via the CLI tab.\n
115
00:11:05,328 --> 00:11:10,088
This means that Syslog messages will be displayed\n
116
00:11:10,089 --> 00:11:17,379
Telnet or SSH. Telnet and SSH will be covered\n
117
00:11:17,379 --> 00:11:22,009
to connect to a device over a network, without\n
118
00:11:22,009 --> 00:11:27,499
console port. Logging to the VTY lines is\n
119
00:11:27,499 --> 00:11:33,939
not be displayed if you’re connecting to\n
120
00:11:33,938 --> 00:11:39,938
an interface, for example, no message will\n
121
00:11:39,938 --> 00:11:44,480
messages is the ‘buffer’ of the device.\n
122
00:11:44,480 --> 00:11:51,420
to RAM. By default, all messages, from level\n
123
00:11:51,419 --> 00:11:55,778
You can view the messages in the buffer with\n
124
00:11:55,778 --> 00:12:01,028
at that command in the lab video. You can\n
125
00:12:01,028 --> 00:12:06,259
to an external server. This is very useful,\n
126
00:12:06,259 --> 00:12:11,789
small networks. Having a central server for\n
127
00:12:11,789 --> 00:12:17,929
easier and makes it easier to compare the\n
128
00:12:17,929 --> 00:12:24,899
servers will listen for Syslog messages on\n
129
00:12:24,899 --> 00:12:31,589
message to a Syslog server, the destination\n
130
00:12:31,589 --> 00:12:36,899
So here are some basic Syslog configurations.\n
131
00:12:36,899 --> 00:12:42,629
the console line. This is enabled by default,\n
132
00:12:42,629 --> 00:12:48,730
is LOGGING CONSOLE, followed by the level.\n
133
00:12:48,730 --> 00:12:54,058
commands, you can specify either the number\n
134
00:12:54,058 --> 00:12:59,988
I specified 6, but I could have used the keyword\n
135
00:12:59,989 --> 00:13:05,028
doesn’t only enable informational messages.\n
136
00:13:05,028 --> 00:13:12,379
and higher, so informational to emergency,\n
137
00:13:12,379 --> 00:13:17,470
0. By default the console logs all messages,\n
138
00:13:17,470 --> 00:13:22,809
level to 6 actually slightly restricts the\n
139
00:13:22,808 --> 00:13:28,528
Okay, next the command to configure logging\n
140
00:13:28,528 --> 00:13:34,389
by the level. Just like above, you can specify\n
141
00:13:34,389 --> 00:13:39,850
the keyword of INFORMATIONAL instead of the\n
142
00:13:39,850 --> 00:13:45,159
buffer the command is LOGGING BUFFERED, followed\n
143
00:13:45,159 --> 00:13:50,039
level. The size is optional, if you don’t\n
144
00:13:50,039 --> 00:13:55,338
size. Just be careful not to set the buffer\n
145
00:13:55,339 --> 00:14:01,709
memory away from other essential operations.\n
146
00:14:01,708 --> 00:14:06,438
you can use either the number or the keyword,\n
147
00:14:06,438 --> 00:14:13,448
6 but also levels 5, 4, 3, 2, 1, and 0. Finally,\n
148
00:14:13,448 --> 00:14:20,628
with LOGGING, followed by the server IP, or\n
149
00:14:20,629 --> 00:14:25,619
commands are the same, you can use whichever.\n
150
00:14:25,619 --> 00:14:30,889
to the external server, you need to use a\n
151
00:14:30,889 --> 00:14:36,110
by the level. This time I specified DEBUGGING,\n
152
00:14:36,110 --> 00:14:43,180
number of 7 instead. This enables logging\n
153
00:14:43,179 --> 00:14:48,818
3, 2, 1, and 0. So, that’s how you enable\n
154
00:14:48,818 --> 00:14:55,068
specify which levels of messages should be\n
155
00:14:55,068 --> 00:14:59,019
specified in the exam topics, you probably\n
156
00:14:59,019 --> 00:15:04,068
the exam. However, I will include flashcards\n
157
00:15:04,068 --> 00:15:08,068
with them in the following lab video.
158
00:15:08,068 --> 00:15:13,729
Let me introduce another command. Even if\n
159
00:15:13,730 --> 00:15:19,420
messages will not be displayed when connected\n
160
00:15:19,419 --> 00:15:24,849
too. For the messages to be displayed, you\n
161
00:15:24,850 --> 00:15:29,759
from privileged exec mode. But not only that,\n
162
00:15:29,759 --> 00:15:35,989
to the device via Telnet or SSH. So, if you\n
163
00:15:35,989 --> 00:15:41,800
command, Syslog messages will be displayed\n
164
00:15:41,799 --> 00:15:46,448
you log out, that ‘session’ is finished\n
165
00:15:46,448 --> 00:15:52,308
effective. To display Syslog messages in the\n
166
00:15:52,308 --> 00:15:58,259
need to use the TERMINAL MONITOR command again.\n
167
00:15:58,259 --> 00:16:03,759
This next command isn’t essential, but very\n
168
00:16:03,759 --> 00:16:07,828
in the CLI while you are in the middle of\n
169
00:16:07,828 --> 00:16:14,178
like this. Notice in the middle of typing\n
170
00:16:14,178 --> 00:16:19,938
I continued typing the command, and the command\n
171
00:16:19,938 --> 00:16:23,828
the color of the command to make it easier\n
172
00:16:23,828 --> 00:16:29,888
the CLI it can be hard to see where the Syslog\n
173
00:16:29,889 --> 00:16:34,789
To prevent this, you should use the logging\n
174
00:16:34,789 --> 00:16:40,000
and I will talk more about ‘line’ configuration\n
175
00:16:40,000 --> 00:16:45,100
to learn this yet, but for example here’s\n
176
00:16:45,100 --> 00:16:50,870
0, and then configure LOGGING SYNCHRONOUS.\n
177
00:16:50,870 --> 00:16:57,519
your typing is interrupted by a message. Here’s\n
178
00:16:57,519 --> 00:17:03,789
was displayed, and then SHOW IP INT was reprinted\n
179
00:17:03,789 --> 00:17:09,149
typing the command. So, this is a nice command\n
180
00:17:09,150 --> 00:17:12,190
labs. It just makes things easier to see.
181
00:17:12,190 --> 00:17:19,490
Okay, the last two commands I want to show\n
182
00:17:19,490 --> 00:17:23,319
This is how you control whether or not the\n
183
00:17:23,319 --> 00:17:30,919
in Syslog messages. To enable timestamps for\n
184
00:17:30,920 --> 00:17:36,670
followed either by DATETIME or UPTIME. If\n
185
00:17:36,670 --> 00:17:42,420
the actual date and time when the event occurred.\n
186
00:17:42,420 --> 00:17:46,759
display the date and time, they will display\n
187
00:17:46,759 --> 00:17:52,829
the event occurred. DATETIME is usually the\n
188
00:17:52,829 --> 00:17:58,279
Then I enabled sequence numbers with the SERVICE\n
189
00:17:58,279 --> 00:18:04,559
config mode, you can see that the Syslog message\n
190
00:18:04,559 --> 00:18:08,669
I think it’s a good idea to always enable\n
191
00:18:08,670 --> 00:18:13,080
find sequence numbers particularly useful,\n
192
00:18:13,079 --> 00:18:17,909
Here’s a summary of the commands I just\n
193
00:18:17,910 --> 00:18:23,080
lab will be very helpful, not just for remembering\n
194
00:18:23,079 --> 00:18:29,189
works. So make sure to watch the next video\n
195
00:18:29,190 --> 00:18:36,880
Finally, here’s a brief comparison of Syslog\n
196
00:18:36,880 --> 00:18:41,850
are both used for monitoring and troubleshooting\n
197
00:18:41,849 --> 00:18:47,829
functionalities are different. Syslog is used\n
198
00:18:47,829 --> 00:18:53,609
the system are categorized based on facility\n
199
00:18:53,609 --> 00:19:00,119
and likely to an external Syslog server. Syslog\n
200
00:19:00,119 --> 00:19:05,649
troubleshooting. Here’s a big difference.\n
201
00:19:05,650 --> 00:19:10,680
server, but the server can’t actively pull\n
202
00:19:10,680 --> 00:19:19,400
Get message, or modify variables on the devices,\n
203
00:19:19,400 --> 00:19:25,050
used to retrieve and organize information\n
204
00:19:25,049 --> 00:19:31,559
IP addresses, current interface status, device\n
205
00:19:31,559 --> 00:19:38,480
variables and organized within the MIB. SNMP\n
206
00:19:38,480 --> 00:19:45,160
Set to modify variables on the clients. Syslog\n
207
00:19:45,160 --> 00:19:51,470
device management, and you need to be familiar\n
208
00:19:51,470 --> 00:19:56,250
Before the quiz, here’s a review of what\n
209
00:19:56,250 --> 00:20:02,019
of Syslog. It’s an industry standard protocol\n
210
00:20:02,019 --> 00:20:08,600
I introduced the Syslog message format, as\n
211
00:20:08,601 --> 00:20:13,040
sure you know all of those severity level\n
212
00:20:13,039 --> 00:20:19,759
the different parts of a Syslog message. Finally,\n
213
00:20:19,759 --> 00:20:24,019
You probably won’t be asked about Syslog\n
214
00:20:24,019 --> 00:20:28,930
hands-on practice in Packet Tracer will be\n
215
00:20:28,930 --> 00:20:34,000
end of the quiz for a bonus practice question\n
216
00:20:34,000 --> 00:20:40,000
exams for the CCNA, and the ones I used to\n
217
00:20:43,160 --> 00:20:48,851
What is the severity level of the following\n
218
00:20:48,851 --> 00:20:56,750
the video now to examine the message and select\n
219
00:20:56,750 --> 00:21:02,869
The answer is C, Notification. This is indicated\n
220
00:21:02,869 --> 00:21:09,009
mnemonic. This severity level is called ‘Notice’\n
221
00:21:09,009 --> 00:21:15,990
as ‘Notification’. In the CLI of Cisco\n
222
00:21:17,799 --> 00:21:23,510
Here’s another one. What is the severity\n
223
00:21:23,510 --> 00:21:32,359
are the options. Pause the video now to examine\n
224
00:21:32,359 --> 00:21:38,740
The answer is B, Error. That is the name of\n
225
00:21:38,740 --> 00:21:43,609
the severity levels and their names. They’re\n
226
00:21:43,609 --> 00:21:49,529
definitely important. Okay, let’s go to\nquestion 3.
227
00:21:49,529 --> 00:21:54,220
Which of the following locations are Syslog\n
228
00:21:54,220 --> 00:22:00,319
Syslog configuration? (select two). Here are\n
229
00:22:00,319 --> 00:22:06,000
about the answers, select two.
230
00:22:06,000 --> 00:22:12,380
The answers are B, the console line and C,\n
231
00:22:12,380 --> 00:22:17,561
messages in realtime when connected to the\n
232
00:22:17,560 --> 00:22:22,019
can also use SHOW LOGGING to view those messages\n
233
00:22:22,019 --> 00:22:27,519
of the device. The device will not send Syslog\n
234
00:22:27,519 --> 00:22:32,730
it to do so, and Syslog messages also won’t\n
235
00:22:32,730 --> 00:22:39,559
the device via the VTY lines using Telnet\n
236
00:22:39,559 --> 00:22:47,000
in another video, don’t worry about them\n
237
00:22:47,000 --> 00:22:52,819
You issue the logging buffered 6 command on\n
238
00:22:52,819 --> 00:22:57,679
will be saved to the logging buffer? Here\n
239
00:23:02,130 --> 00:23:09,180
The answer is C, severity 0 to 6. When you\n
240
00:23:09,180 --> 00:23:13,640
of that level and higher severity, meaning\n
241
00:23:13,640 --> 00:23:19,230
are more severe, will be displayed or saved\n
242
00:23:21,859 --> 00:23:26,979
Which of the following Syslog message fields\n
243
00:23:26,980 --> 00:23:32,299
configuration? (select two). Here are the\n
244
00:23:37,710 --> 00:23:44,809
The answers are A, sequence and D, time stamp.\n
245
00:23:44,809 --> 00:23:50,710
and SERVICE SEQUENCE-NUMBERS command. I highly\n
246
00:23:50,710 --> 00:23:55,029
although I don’t think sequence numbers\n
247
00:23:55,029 --> 00:24:03,269
quiz. Now let’s take a look at a bonus question\n
248
00:24:03,269 --> 00:24:09,210
Okay here's today's Boson ExSim practice question.\n
249
00:24:09,210 --> 00:24:14,651
so I'll click on this button to open it up.\n
250
00:24:14,651 --> 00:24:19,680
logging keywords from the left and drag them\n
251
00:24:19,680 --> 00:24:24,570
right. Okay, so I have said this multiple\n
252
00:24:24,569 --> 00:24:33,619
know all of these levels for the CCNA exam.\n
253
00:24:33,619 --> 00:24:40,469
Okay let's check. So, first level 0. This\n
254
00:24:40,470 --> 00:24:49,019
but the severity level is the highest. And\n
255
00:24:49,019 --> 00:25:00,440
number 1, alerts. And the critical, number\n
256
00:25:00,440 --> 00:25:08,130
that, notifications, or notices. And then\n
257
00:25:08,130 --> 00:25:14,030
So, if it helps you remember that, use the\n
258
00:25:14,029 --> 00:25:19,349
need ice cream daily'. So, I personally don't\n
259
00:25:19,349 --> 00:25:25,189
do, so if that helps you remember these seven\n
260
00:25:25,190 --> 00:25:32,830
so I'll click on done and then let's check.\n
261
00:25:32,829 --> 00:25:39,000
as always Boson has a great explanation down\n
262
00:25:39,000 --> 00:25:49,319
about filtering the levels on the console,\n
263
00:25:49,319 --> 00:25:54,990
There is also a reference here to some Cisco\n
264
00:25:54,990 --> 00:26:00,509
keywords. So, if you google this title here\n
265
00:26:00,509 --> 00:26:07,930
is available for free online from Cisco, and\n
266
00:26:07,930 --> 00:26:12,460
that was a question from Boson Software's\n
267
00:26:12,460 --> 00:26:17,019
the best practice exams for the CCNA and I\n
268
00:26:17,019 --> 00:26:22,769
Boson ExSim, please follow the link in the\nvideo description.
269
00:26:22,769 --> 00:26:27,839
There are supplementary materials for this\n
270
00:26:27,839 --> 00:26:32,839
the software ‘Anki’. There will also be\n
271
00:26:32,839 --> 00:26:38,869
some hands-on practice. That will be in the\n
272
00:26:38,869 --> 00:26:42,649
the link in the description, and I’ll send\n
273
00:26:46,420 --> 00:26:52,000
Before finishing today’s video I want to\n
274
00:26:52,000 --> 00:26:57,519
please click the ‘Join’ button under the\n
275
00:26:57,519 --> 00:27:04,389
Brandon, Samil, Aaron, Tech Alameda, Marcel,\n
276
00:27:04,390 --> 00:27:10,210
Junhong, Benjamin, Tshepiso, Justin, Prakaash,\n
277
00:27:10,210 --> 00:27:16,559
Ed, Value, John, Funnydart, Velvijaykum, Mark,\n
278
00:27:16,559 --> 00:27:21,569
and Vance. Sorry if I pronounced your name\n
279
00:27:21,569 --> 00:27:28,369
support. This is the list of JCNP-level members\n
280
00:27:28,369 --> 00:27:33,799
13th 2021. If you signed up recently and your\n
281
00:27:36,849 --> 00:27:41,719
Thank you for watching. Please subscribe to\n
282
00:27:41,720 --> 00:27:46,730
and share the video with anyone else studying\n
283
00:27:46,730 --> 00:27:52,400
check the links in the description. I'm also\n
284
00:27:52,400 --> 00:27:56,330
or Basic Attention Token, tips via the Brave\n
23233
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.