Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,360 --> 00:00:07,840
Welcome to Jeremy’s IT Lab. This is a free,\xa0\n
2
00:00:07,839 --> 00:00:13,519
videos, please subscribe to follow along with the\xa0\n
3
00:00:13,519 --> 00:00:17,359
and share the video to help spread this\xa0\n
4
00:00:18,879 --> 00:00:23,119
In this video we will cover SNMP, the\xa0\n
5
00:00:24,320 --> 00:00:30,960
SNMP is mentioned in exam topic 4.4, which says\xa0\n
6
00:00:30,960 --> 00:00:36,320
in network operations. So, you don’t need\xa0\n
7
00:00:36,320 --> 00:00:40,399
know how to set up an SNMP server,\xa0\n
8
00:00:41,280 --> 00:00:45,200
Basically, you just need to know its\xa0\n
9
00:00:46,960 --> 00:00:52,000
Here’s what we’ll cover in this video.\xa0\n
10
00:00:52,000 --> 00:00:56,480
its purpose, how it works, etc.\n
11
00:00:56,479 --> 00:01:01,359
versions of SNMP. There have actually been many\xa0\n
12
00:01:02,079 --> 00:01:04,239
however you only really need to know 3 of them.\xa0\xa0
13
00:01:05,359 --> 00:01:10,159
I’ll also give an overview of the different\xa0\n
14
00:01:11,519 --> 00:01:17,679
And finally, some very basic SNMP configurations.\xa0\n
15
00:01:17,680 --> 00:01:22,960
configuration as a requirement, I think it’s a\xa0\n
16
00:01:22,959 --> 00:01:28,639
we will then try out in the next lab video.\xa0\n
17
00:01:28,640 --> 00:01:34,640
practice question from Boson Software’s ExSim\xa0\n
18
00:01:36,480 --> 00:01:43,760
So let me give you an overview of SNMP. SNMP is\xa0\n
19
00:01:43,760 --> 00:01:50,800
was originally released in 1988. Most people think\xa0\n
20
00:01:50,799 --> 00:01:56,959
into a larger framework of network management,\xa0\n
21
00:01:56,959 --> 00:02:05,359
RFC was RFC 1065, structure and identification of\xa0\n
22
00:02:06,400 --> 00:02:12,640
I think I mentioned RFCs, Requests For Comments,\xa0\n
23
00:02:12,639 --> 00:02:18,399
how the IETF, Internet Engineering Task\xa0\n
24
00:02:19,599 --> 00:02:27,120
The next RFC for SNMP was RFC 1066, management\xa0\n
25
00:02:27,120 --> 00:02:34,560
TCP/IP-based internets. And one more, RFC\xa0\n
26
00:02:35,680 --> 00:02:42,480
These three RFCs together make up SNMP version\xa0\n
27
00:02:42,479 --> 00:02:47,039
defining other versions of SNMP, a few of\xa0\n
28
00:02:48,479 --> 00:02:52,399
By the way, you don’t have to memorize these\xa0\n
29
00:02:54,000 --> 00:02:59,439
Don’t let the ‘simple’ in the name fool\xa0\n
30
00:02:59,439 --> 00:03:04,719
compared to the later versions, the current\xa0\n
31
00:03:05,439 --> 00:03:11,840
I know I still have a lot to learn about SNMP.\xa0\n
32
00:03:11,840 --> 00:03:16,800
you don’t need to know all the details, but you\xa0\n
33
00:03:16,800 --> 00:03:24,160
SNMP. SNMP can be used to monitor the status\xa0\n
34
00:03:25,360 --> 00:03:32,000
There are two main types of devices in SNMP.\xa0\n
35
00:03:32,000 --> 00:03:38,560
the devices being managed using SNMP. For example,\xa0\n
36
00:03:39,520 --> 00:03:43,760
We can use SNMP to monitor the status of\xa0\n
37
00:03:45,039 --> 00:03:49,919
And the second type is the Network Management\xa0\n
38
00:03:49,919 --> 00:03:55,359
Management System, instead of Station.\xa0\n
39
00:03:55,360 --> 00:04:02,000
or devices, managing the managed devices I\xa0\n
40
00:04:02,000 --> 00:04:05,840
although typically we use the\xa0\n
41
00:04:07,680 --> 00:04:13,760
Let’s look more at how SNMP works. In this\xa0\n
42
00:04:13,759 --> 00:04:22,560
Station or System. We’re using SNMP to manage R1\xa0\n
43
00:04:22,560 --> 00:04:28,720
are three main operations used in SNMP, three main\xa0\n
44
00:04:29,839 --> 00:04:33,679
The first one is that managed\xa0\n
45
00:04:34,720 --> 00:04:41,840
For example, perhaps SW1’s G0/1 interface had a\xa0\n
46
00:04:41,839 --> 00:04:48,159
It can send an SNMP message to the NMS, SRV1,\xa0\n
47
00:04:49,360 --> 00:04:54,720
The actual SNMP software on the server, or\xa0\n
48
00:04:54,720 --> 00:04:57,920
network administrator to inform\xa0\n
49
00:05:00,240 --> 00:05:05,439
Okay, so managed devices can notify the NMS of\xa0\n
50
00:05:06,879 --> 00:05:11,120
The NMS can also ask the managed devices\xa0\n
51
00:05:12,240 --> 00:05:17,439
For example, perhaps the NMS, SRV1,\xa0\n
52
00:05:18,399 --> 00:05:22,159
You want to make sure your network devices\xa0\n
53
00:05:23,759 --> 00:05:29,599
R1 will then reply to the NMS, for example\xa0\n
54
00:05:30,959 --> 00:05:32,959
So, that’s another function of SNMP.
55
00:05:35,279 --> 00:05:41,199
And one more main operation used by SNMP is\xa0\n
56
00:05:41,199 --> 00:05:48,079
aspects of their configuration. For example,\xa0\n
57
00:05:48,079 --> 00:05:57,599
is 203.0.113.1/30. The NMS can tell R1 to\xa0\n
58
00:05:59,199 --> 00:06:03,360
R1 will change the IP address\xa0\n
59
00:06:04,639 --> 00:06:10,159
So, those are the three main operations used\xa0\n
60
00:06:10,160 --> 00:06:15,920
NMS of events, the NMS can ask managed devices\xa0\n
61
00:06:16,800 --> 00:06:20,560
and the NMS can also tell the managed\xa0\n
62
00:06:21,680 --> 00:06:24,160
Now let’s look a little deeper\xa0\ninto how this all works.
63
00:06:26,879 --> 00:06:29,120
These are the main components of SNMP.\xa0\xa0
64
00:06:29,920 --> 00:06:33,199
Up top there is the NMS from the\xa0\n
65
00:06:34,240 --> 00:06:40,480
On the bottom, the two managed devices, SW1 and\xa0\n
66
00:06:42,000 --> 00:06:48,480
First, the components of the NMS. Let this green\xa0\n
67
00:06:49,360 --> 00:06:54,720
The NMS probably isn’t a machine dedicated\xa0\n
68
00:06:54,720 --> 00:07:01,840
PC which is running SNMP software. So, what\xa0\n
69
00:07:02,480 --> 00:07:08,879
First, the SNMP Manager is the SNMP software on\xa0\n
70
00:07:09,759 --> 00:07:15,839
It receives notifications, sends requests for\xa0\n
71
00:07:16,720 --> 00:07:21,680
Next there is an SNMP application, this is\xa0\n
72
00:07:21,680 --> 00:07:25,680
for the network admin to interact\xa0\n
73
00:07:25,680 --> 00:07:32,000
statistics, charts, etc. Here’s what an\xa0\n
74
00:07:32,000 --> 00:07:37,839
plenty of free and commercial SNMP applications\xa0\n
75
00:07:39,680 --> 00:07:46,879
Next, let’s look at the managed devices, SW1\xa0\n
76
00:07:46,879 --> 00:07:52,959
represents the SNMP entity on the managed\xa0\n
77
00:07:52,959 --> 00:07:59,839
so of course SNMP is just a part of what’s running\xa0\n
78
00:07:59,839 --> 00:08:05,679
Agent. This is the SNMP software running on the\xa0\n
79
00:08:05,680 --> 00:08:11,840
Manager on the NMS. It sends notifications\xa0\n
80
00:08:13,040 --> 00:08:17,439
Another important component is the\xa0\n
81
00:08:18,399 --> 00:08:24,639
This is the structure that contains the variables\xa0\n
82
00:08:24,639 --> 00:08:31,199
is identified with an Object ID, OID. Some\xa0\n
83
00:08:31,199 --> 00:08:35,439
are the status of each interface on\xa0\n
84
00:08:35,440 --> 00:08:42,480
CPU usage, device temperature, etc. Each of\xa0\n
85
00:08:43,919 --> 00:08:50,240
So, that’s the basic structure of SNMP. Then,\xa0\n
86
00:08:50,240 --> 00:08:57,519
and manager make SNMP work. Now before moving on\xa0\n
87
00:08:57,519 --> 00:09:03,759
briefly introduce those Object IDs, OIDs, that are\xa0\n
88
00:09:05,679 --> 00:09:12,799
SNMP Object IDs are organized in a hierarchical\xa0\n
89
00:09:12,799 --> 00:09:22,079
how it breaks down. iso, identified-organization,\xa0\n
90
00:09:22,080 --> 00:09:28,879
and sysName. So, this OID is used to identify the\xa0\n
91
00:09:30,159 --> 00:09:35,839
For example, here’s that same network again.\xa0\n
92
00:09:36,399 --> 00:09:44,079
what value do you have for this OID? SW1 then\xa0\n
93
00:09:44,080 --> 00:09:49,520
countless different OIDs. If you want to explore\xa0\n
94
00:09:49,519 --> 00:09:56,399
oid-info.com. That’s how I got the OID information\xa0\n
95
00:09:58,879 --> 00:10:04,879
Now let me give a brief overview of the major\xa0\n
96
00:10:04,879 --> 00:10:09,919
proposed and developed, however only three\xa0\n
97
00:10:11,200 --> 00:10:20,160
The first is SNMPv1, this is the original version\xa0\n
98
00:10:20,159 --> 00:10:28,480
multiple versions of SNMPv2, but v2c is the most\xa0\n
99
00:10:28,480 --> 00:10:33,440
which allows the NMS to retrieve large amounts\xa0\n
100
00:10:33,440 --> 00:10:38,240
single request, making it much more efficient,\xa0\n
101
00:10:39,519 --> 00:10:44,159
The ‘c’ in the name refers to the ‘community\xa0\n
102
00:10:44,159 --> 00:10:50,240
in SNMPv1, removed from SNMPv2, and\xa0\n
103
00:10:50,240 --> 00:10:56,480
SNMPv2c. When we take a look at SNMP\xa0\n
104
00:10:56,480 --> 00:11:01,840
demonstrate, so you’ll see how these community\xa0\n
105
00:11:03,440 --> 00:11:08,000
Okay, the next major version and\xa0\n
106
00:11:08,799 --> 00:11:14,479
It is a much more secure version of SNMP that\xa0\n
107
00:11:15,519 --> 00:11:19,039
I’ll talk more about those terms in\xa0\n
108
00:11:19,679 --> 00:11:24,639
but basically it means that SNMPv3 makes\xa0\n
109
00:11:24,639 --> 00:11:29,039
read the SNMP messages, they can’t be\xa0\n
110
00:11:30,399 --> 00:11:37,360
Now let’s look at the SNMP message types. In this\xa0\n
111
00:11:37,360 --> 00:11:42,720
write, notification, and response. I’ve\xa0\n
112
00:11:42,720 --> 00:11:45,680
and then listed the actual\xa0\n
113
00:11:47,039 --> 00:11:53,039
First let’s take a look at the ‘read’ message\xa0\n
114
00:11:53,039 --> 00:11:59,199
information from the managed devices. I already\xa0\n
115
00:11:59,200 --> 00:12:06,560
asked SW1 what its host name is. There are three\xa0\n
116
00:12:08,320 --> 00:12:13,440
I think this is more depth than necessary for\xa0\n
117
00:12:13,440 --> 00:12:19,920
of those messages. First up is the Get message.\xa0\n
118
00:12:20,480 --> 00:12:25,680
the NMS to the managed device, to\xa0\n
119
00:12:25,679 --> 00:12:31,359
or multiple variables. The agent will send\xa0\n
120
00:12:31,360 --> 00:12:39,279
of each variable. For example, our NMS here might\xa0\n
121
00:12:40,080 --> 00:12:48,400
And SW1 responds with an SNMP ‘response’ message.\xa0\n
122
00:12:48,399 --> 00:12:54,559
is sent from the manager to the agent to discover\xa0\n
123
00:12:54,559 --> 00:13:00,000
it says ‘tell me the next OID’, so it can be\xa0\n
124
00:13:01,039 --> 00:13:07,039
There is also the GetBulk message, which is a more\xa0\n
125
00:13:08,080 --> 00:13:12,000
If you know the purpose of the basic Get\xa0\n
126
00:13:14,159 --> 00:13:19,279
So, those are the ‘read’ messages. Next up, the\xa0\n
127
00:13:19,279 --> 00:13:25,199
kind of message, which is ‘Set’. These are sent\xa0\n
128
00:13:25,200 --> 00:13:30,400
devices, to change the value of a specific\xa0\n
129
00:13:32,240 --> 00:13:37,039
Just like with the Get message, I already\xa0\n
130
00:13:37,039 --> 00:13:41,679
when SRV1 made R1 change the IP\xa0\n
131
00:13:41,679 --> 00:13:48,319
but I’ll demonstrate again. So, the Set message is\xa0\n
132
00:13:48,320 --> 00:13:54,640
the value of one or more variables. Then the agent\xa0\n
133
00:13:55,679 --> 00:14:01,839
For example, SRV1 can send a Set message to SW1,\xa0\n
134
00:14:03,200 --> 00:14:07,520
SW1 will then change its host name, and send\xa0\n
135
00:14:09,519 --> 00:14:12,319
So, that’s the write message\xa0\n
136
00:14:13,200 --> 00:14:18,640
Next the ‘notification’ message class. These\xa0\n
137
00:14:18,639 --> 00:14:23,279
to alert the NMS of a particular event,\xa0\n
138
00:14:24,000 --> 00:14:29,840
There are two different messages,\xa0\n
139
00:14:30,480 --> 00:14:35,840
First up, the Trap message. This is a\xa0\n
140
00:14:35,840 --> 00:14:40,879
so the managed device to the NMS. The\xa0\n
141
00:14:40,879 --> 00:14:44,720
to acknowledge that it received the\xa0\n
142
00:14:45,840 --> 00:14:49,840
Also, SNMP uses UDP, so there\xa0\n
143
00:14:51,120 --> 00:14:55,759
Now, unless there’s some problem in the\xa0\n
144
00:14:55,759 --> 00:15:00,639
but since there is no reliability mechanism\xa0\n
145
00:15:01,679 --> 00:15:07,279
I showed an example before, but here’s\xa0\n
146
00:15:07,279 --> 00:15:13,039
so it sends a Trap message to the NMS,\xa0\n
147
00:15:14,399 --> 00:15:18,799
This Trap will probably appear as an\xa0\n
148
00:15:19,759 --> 00:15:23,919
and perhaps it will send an email notification\xa0\n
149
00:15:25,600 --> 00:15:31,680
Okay, the next kind of notification message is the\xa0\n
150
00:15:31,679 --> 00:15:37,759
is acknowledged with a response message. So, even\xa0\n
151
00:15:38,320 --> 00:15:45,040
there is reliability built into the message\xa0\n
152
00:15:45,039 --> 00:15:50,959
will send a Response to tell SW1 that the Inform\xa0\n
153
00:15:50,960 --> 00:15:55,680
used for communications between managers,\xa0\n
154
00:15:56,399 --> 00:16:01,439
However later updates to the protocol allow\xa0\n
155
00:16:03,039 --> 00:16:09,439
So, those are the SNMP Trap and Inform messages.\xa0\n
156
00:16:09,440 --> 00:16:15,280
one message, Response. These are messages sent\xa0\n
157
00:16:16,000 --> 00:16:22,240
For example, Get messages, Set messages, and\xa0\n
158
00:16:22,240 --> 00:16:28,639
of Response messages, so I think that’s enough for\xa0\n
159
00:16:28,639 --> 00:16:33,919
information I just gave you will be more than\xa0\n
160
00:16:33,919 --> 00:16:42,079
numbers in the Day 30 video on TCP and UDP, but\xa0\n
161
00:16:42,720 --> 00:16:49,840
and SNMP Managers listen for messages on UDP port\xa0\n
162
00:16:50,639 --> 00:16:53,519
Now let me demonstrate some\xa0\n
163
00:16:54,879 --> 00:16:59,200
As I said before, SNMP configuration\xa0\n
164
00:16:59,919 --> 00:17:05,119
but I think getting a bit of hands-on practice\xa0\n
165
00:17:05,119 --> 00:17:10,159
cover setting up the NMS, that’s definitely\xa0\n
166
00:17:10,160 --> 00:17:17,600
to set up the SNMP agent on a Cisco router. In\xa0\n
167
00:17:17,599 --> 00:17:24,480
is the NMS, running an SNMP application. First\xa0\n
168
00:17:24,480 --> 00:17:30,240
giving some contact information and the location\xa0\n
169
00:17:30,240 --> 00:17:36,400
don’t need to configure this. Then I configured\xa0\n
170
00:17:36,400 --> 00:17:42,560
these are basically SNMP passwords. Notice\xa0\n
171
00:17:42,559 --> 00:17:50,000
as RO, this means read only. So, an NMS using\xa0\n
172
00:17:50,000 --> 00:17:57,039
it can’t use Set to make any changes to R1.\xa0\n
173
00:17:57,039 --> 00:18:03,279
read/write. An NMS using this password will be\xa0\n
174
00:18:03,279 --> 00:18:09,759
using Set messages. Note that there are actually\xa0\n
175
00:18:09,759 --> 00:18:16,319
and ‘private’ for RW. So, if you don’t specify\xa0\n
176
00:18:16,319 --> 00:18:20,559
it’s best to configure the community strings and\xa0\n
177
00:18:22,000 --> 00:18:29,599
Then I specified the address of the NMS, PC1 at\xa0\n
178
00:18:29,599 --> 00:18:36,159
version and which community string to use with\xa0\n
179
00:18:36,160 --> 00:18:41,840
be able to read information from R1, but it won’t\xa0\n
180
00:18:43,279 --> 00:18:47,680
So, the read/write community string Jeremy2\xa0\n
181
00:18:49,039 --> 00:18:55,920
Then I configured what kinds of traps to send to\xa0\n
182
00:18:55,920 --> 00:19:01,920
so if an interface goes up or down Traps\xa0\n
183
00:19:02,480 --> 00:19:07,599
so for example if configuration changes\xa0\n
184
00:19:07,599 --> 00:19:14,639
that’s a simple SNMPv2c configuration. Let’s see\xa0\n
185
00:19:16,480 --> 00:19:22,960
Here’s a Wireshark capture of the Trap that was\xa0\n
186
00:19:22,960 --> 00:19:29,680
bottom, you’ll see numerous OIDs included in this\xa0\n
187
00:19:30,319 --> 00:19:35,679
and as you can see it is a linkDown Trap,\xa0\n
188
00:19:37,599 --> 00:19:42,959
Okay, now let’s look at some other fields of\xa0\n
189
00:19:42,960 --> 00:19:49,120
2c that I configured. And here’s the community,\xa0\n
190
00:19:50,160 --> 00:19:57,920
Note that this community string, this password,\xa0\n
191
00:19:57,920 --> 00:20:02,720
there is no encryption. The community and\xa0\n
192
00:20:03,680 --> 00:20:07,360
This is not secure, as the packets\xa0\n
193
00:20:08,240 --> 00:20:14,799
So, as I mentioned before SNMPv3 is\xa0\n
194
00:20:14,799 --> 00:20:20,079
configuration is also more complicated, so for\xa0\n
195
00:20:22,000 --> 00:20:28,480
So, before moving on to the quiz let me summarize\xa0\n
196
00:20:28,480 --> 00:20:34,559
a network. There are two main components of\xa0\n
197
00:20:34,559 --> 00:20:40,159
managed using SNMP, such as network devices,\xa0\n
198
00:20:41,279 --> 00:20:46,399
The network management stations, NMS, are\xa0\n
199
00:20:47,440 --> 00:20:52,400
The NMS receives notifications from managed\xa0\n
200
00:20:52,400 --> 00:20:58,960
devices. It can also check on the status of\xa0\n
201
00:20:58,960 --> 00:21:05,840
status, temperature, traffic load, host name,\xa0\n
202
00:21:05,839 --> 00:21:12,559
and each variable is identified using an object\xa0\n
203
00:21:12,559 --> 00:21:18,639
version 1, version 2c, and version 3. Version 3\xa0\n
204
00:21:18,640 --> 00:21:22,960
previous versions, providing encryption\xa0\n
205
00:21:24,319 --> 00:21:31,599
And these are the SNMP messages we covered: Get,\xa0\n
206
00:21:32,960 --> 00:21:36,640
Okay, that should be more than enough\xa0\n
207
00:21:37,519 --> 00:21:41,839
Remember, the exam topics state you need to\xa0\n
208
00:21:42,720 --> 00:21:46,400
There’s a lot more that can be learned about\xa0\n
209
00:21:47,519 --> 00:21:52,319
As always, make sure to watch until the end of\xa0\n
210
00:21:52,319 --> 00:21:58,480
Software’s ExSim, the best practice exams for the\xa0\n
211
00:21:59,680 --> 00:22:03,039
Which of the following SNMP\xa0\n
212
00:22:03,039 --> 00:22:06,559
to ‘read’ information from the managed\xa0\n
213
00:22:07,200 --> 00:22:11,840
Here are the options. Pause the\xa0\n
214
00:22:14,240 --> 00:22:19,519
The answers are D, Get, and G,\xa0\n
215
00:22:19,519 --> 00:22:24,079
there is also the GetBulk message which is used\xa0\n
216
00:22:25,039 --> 00:22:31,359
By the way, F, SetBulk, is not a real SNMP\xa0\n
217
00:22:32,559 --> 00:22:37,359
Which of the following SNMP\xa0\n
218
00:22:38,000 --> 00:22:43,039
Select all that apply. Here are the options.\xa0\n
219
00:22:47,119 --> 00:22:55,439
The answers are A, Inform, and B, Trap. The\xa0\n
220
00:22:56,160 --> 00:23:02,240
Informs and Traps are both sent from the managed\xa0\n
221
00:23:03,359 --> 00:23:07,279
Set and Get messages are sent from\xa0\n
222
00:23:07,279 --> 00:23:12,799
which listen on port 161, so they are\xa0\n
223
00:23:14,960 --> 00:23:19,360
Which of the following SNMP message\xa0\n
224
00:23:19,359 --> 00:23:22,399
and allows mass-retrieval of\xa0\n
225
00:23:23,279 --> 00:23:26,319
Here are the options. Pause the\xa0\n
226
00:23:30,079 --> 00:23:36,319
The answer is D, GetBulk. GetBulk is like an\xa0\n
227
00:23:36,319 --> 00:23:42,480
NMS to discover the variables in the MIB of the\xa0\n
228
00:23:44,960 --> 00:23:48,640
Which of the following pieces\xa0\n
229
00:23:49,279 --> 00:23:52,480
Here are the options. Pause the\xa0\n
230
00:23:56,960 --> 00:23:59,360
The answer is C, the SNMP Manager.\xa0\xa0
231
00:24:00,240 --> 00:24:05,359
This is the software that interacts with\xa0\n
232
00:24:05,359 --> 00:24:11,679
sends SNMP messages to and receives messages\xa0\n
233
00:24:14,160 --> 00:24:18,240
Which of the following SNMP messages\xa0\n
234
00:24:18,880 --> 00:24:22,320
Here are the options. Pause the\xa0\n
235
00:24:26,799 --> 00:24:34,559
The answer is D, Trap. Traps are messages sent\xa0\n
236
00:24:34,559 --> 00:24:40,399
aren’t acknowledged with a Response, so they are\xa0\n
237
00:24:40,400 --> 00:24:46,240
in transmit for some reason, the managed device\xa0\n
238
00:24:46,240 --> 00:24:52,000
the quiz. Next let’s take a look at a bonus\xa0\n
239
00:24:54,319 --> 00:25:00,879
Okay here's today's Boson ExSim practice question.\xa0\n
240
00:25:00,880 --> 00:25:08,240
NMS to extract information from an SNMP agent?\xa0\n
241
00:25:08,240 --> 00:25:15,279
we have Inform, Trap, GetNext, Set, and Get. So\xa0\n
242
00:25:20,160 --> 00:25:28,320
Okay so let's check. So it's asking us which of\xa0\n
243
00:25:28,319 --> 00:25:35,439
NMS, that's the network management station, the\xa0\n
244
00:25:35,440 --> 00:25:43,440
a managed device? So these first two choices,\xa0\n
245
00:25:43,440 --> 00:25:52,799
messages are sent from the SNMP agent, the managed\xa0\n
246
00:25:52,799 --> 00:26:02,079
D, and E are all sent from the NMS to the\xa0\n
247
00:26:02,079 --> 00:26:09,039
or the object ID, of the next object, the next\xa0\n
248
00:26:09,039 --> 00:26:15,839
to discover what objects, what OIDs, are in the\xa0\n
249
00:26:17,920 --> 00:26:22,640
So I think that is one of the correct\xa0\n
250
00:26:22,640 --> 00:26:30,320
from an SNMP agent. Now, Set is used to\xa0\n
251
00:26:30,319 --> 00:26:36,559
used to extract information, it's used to change\xa0\n
252
00:26:37,200 --> 00:26:44,880
is used to get the value of one of the variables,\xa0\n
253
00:26:44,880 --> 00:26:50,800
I think E is correct also. So the two correct\xa0\n
254
00:26:50,799 --> 00:26:56,559
the answers in Boson ExSim by clicking on 'show\xa0\n
255
00:26:57,440 --> 00:27:02,960
So here is Boson's explanation, including an\xa0\n
256
00:27:02,960 --> 00:27:07,840
I mentioned in this video. You can pause\xa0\n
257
00:27:10,240 --> 00:27:14,160
And there is more down here,\xa0\n
258
00:27:18,319 --> 00:27:21,919
And here. And there's also a\xa0\n
259
00:27:21,920 --> 00:27:24,720
about the SNMP Get message type.\xa0\xa0
260
00:27:27,039 --> 00:27:32,720
Okay so that was a look at Boson Software's ExSim\xa0\n
261
00:27:32,720 --> 00:27:38,480
the best practice exams for the CCNA, and they are\xa0\n
262
00:27:38,480 --> 00:27:44,480
for my CCNA exam. If you want to get Boson ExSim,\xa0\n
263
00:27:47,440 --> 00:27:51,680
There are supplementary materials for\xa0\n
264
00:27:51,680 --> 00:27:56,320
to use with the software ‘Anki’. There\xa0\n
265
00:27:56,319 --> 00:27:59,439
so you can get some hands-on\xa0\n
266
00:27:59,440 --> 00:28:04,559
next video. Sign up for my mailing\xa0\n
267
00:28:04,559 --> 00:28:08,319
and I’ll send you all of the flashcards\xa0\n
268
00:28:10,720 --> 00:28:14,799
Before finishing today’s video I want\xa0\n
269
00:28:15,519 --> 00:28:21,599
To join, please click the ‘Join’ button under\xa0\n
270
00:28:21,599 --> 00:28:28,079
Aaron, Tech Alameda, Marcel, Magrathea, Kone,\xa0\n
271
00:28:28,079 --> 00:28:34,079
Benjamin, Tshepiso, Justin, Prakaash, Nasir,\xa0\n
272
00:28:34,079 --> 00:28:40,159
Value, John, Funnydart, Velvijaykum, Mark, Yousif,\xa0\n
273
00:28:41,279 --> 00:28:45,119
Sorry if I pronounced your name incorrectly,\xa0\n
274
00:28:46,079 --> 00:28:52,720
This is the list of JCNP-level members at the time\xa0\n
275
00:28:52,720 --> 00:28:57,839
you signed up recently and your name isn’t on\xa0\n
276
00:28:59,119 --> 00:29:02,239
Thank you for watching. Please\xa0\n
277
00:29:02,240 --> 00:29:06,960
like the video, leave a comment, and share the\xa0\n
278
00:29:08,000 --> 00:29:13,599
If you want to leave a tip, check the links in the\xa0\n
279
00:29:13,599 --> 00:29:20,240
and accept BAT, or Basic Attention Token, tips\xa0\n
23629
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.