WEBVTT

1
00:00.000 --> 00:01.640 align:middle line:84%


2
00:01.640 --> 00:04.875 align:middle line:90%
SNMP version 2C is fairly
straightforward because it

3
00:04.875 --> 00:06.500 align:middle line:90%
doesn't have a lot
of details regarding

4
00:06.500 --> 00:09.530 align:middle line:90%
encryption and authentication
because it doesn't do it.

5
00:09.530 --> 00:11.870 align:middle line:90%
However, it does require
doing a little bit

6
00:11.870 --> 00:14.660 align:middle line:90%
of setup at the router and
also a little bit of setup

7
00:14.660 --> 00:16.760 align:middle line:90%
on the NMS, the network
management station.

8
00:16.760 --> 00:19.970 align:middle line:90%
And I'd like to share with you
a demonstration of both of those

9
00:19.970 --> 00:23.630 align:middle line:90%
and how we can verify that
SNMP is indeed working.

10
00:23.630 --> 00:25.550 align:middle line:90%
Here's our topology
for this demonstration.

11
00:25.550 --> 00:27.350 align:middle line:90%
This router right
here, router one,

12
00:27.350 --> 00:38.090 align:middle line:90%
is going to be a literal
router called KB-LSV-RTR-A,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:27.350 --> 00:38.090 align:middle line:90%
is going to be a literal
router called KB-LSV-RTR-A,

13
00:38.090 --> 00:39.470 align:middle line:84%
and that is its hostname.

14
00:39.470 --> 00:43.940 align:middle line:84%
And it's connected to a cloud.

15
00:43.940 --> 00:46.340 align:middle line:90%
And out there we've got
a network management

16
00:46.340 --> 00:50.000 align:middle line:90%
server that is going to
manage this via SNMP.

17
00:50.000 --> 00:53.420 align:middle line:90%
So on this device, we're
going to use SNMP version

18
00:53.420 --> 00:55.560 align:middle line:84%
2C, which is really simple.

19
00:55.560 --> 00:58.340 align:middle line:90%
We're just going to have a
community string for read

20
00:58.340 --> 01:00.290 align:middle line:84%
only or read/write access.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:58.340 --> 01:00.290 align:middle line:84%
only or read/write access.

21
01:00.290 --> 01:02.300 align:middle line:90%
We'll then tell the
network management server

22
01:02.300 --> 01:06.288 align:middle line:90%
about that IP address and
what those things are.

23
01:06.288 --> 01:07.830 align:middle line:90%
And as long as they
have connectivity

24
01:07.830 --> 01:10.330 align:middle line:90%
and they can reach each other,
the network management server

25
01:10.330 --> 01:11.690 align:middle line:84%
can start pulling that device.

26
01:11.690 --> 01:14.065 align:middle line:90%
And assuming we're using the
right management information

27
01:14.065 --> 01:16.670 align:middle line:90%
base, it can then go into
very nitty gritty detail

28
01:16.670 --> 01:19.190 align:middle line:90%
about that device, querying
information and then

29
01:19.190 --> 01:21.440 align:middle line:90%
displaying it in the
network management system

30
01:21.440 --> 01:22.190 align:middle line:84%
so we can use it.

31
01:22.190 --> 01:22.690 align:middle line:84%
All right.

32
01:22.690 --> 01:25.070 align:middle line:90%
So let's take a look at
the router config for SNMP

33
01:25.070 --> 01:27.742 align:middle line:90%
and then we'll take a look
at the management server.

34
01:27.742 --> 01:28.950 align:middle line:84%
So here we are at the router.

35
01:28.950 --> 01:31.430 align:middle line:90%
It's going to be the SNMP
agent for version 2C.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:28.950 --> 01:31.430 align:middle line:90%
It's going to be the SNMP
agent for version 2C.

36
01:31.430 --> 01:34.670 align:middle line:90%
And if we do a show
run, pipe, and I've

37
01:34.670 --> 01:35.670 align:middle line:84%
already got this set up.

38
01:35.670 --> 01:37.070 align:middle line:84%
I'll do a show run pipe.

39
01:37.070 --> 01:39.050 align:middle line:84%
And we'll include SNMP.

40
01:39.050 --> 01:42.540 align:middle line:90%
And then I'm going to have to
blur out a few of the details,

41
01:42.540 --> 01:44.660 align:middle line:90%
including the community
string that I don't

42
01:44.660 --> 01:46.130 align:middle line:84%
want to disclose to the world.

43
01:46.130 --> 01:48.720 align:middle line:84%
All right, so let's press Enter.

44
01:48.720 --> 01:49.220 align:middle line:84%
All right.

45
01:49.220 --> 01:51.440 align:middle line:90%
So with a little bit
of blur on this output

46
01:51.440 --> 01:54.380 align:middle line:90%
to protect the innocent, if
we want to set up an SNMP

47
01:54.380 --> 01:57.670 align:middle line:90%
agent out for version
2C on the router,

48
01:57.670 --> 02:06.530 align:middle line:90%
it would simply be SNMP server,
space, the keyword community,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
01:57.670 --> 02:06.530 align:middle line:90%
it would simply be SNMP server,
space, the keyword community,

49
02:06.530 --> 02:09.020 align:middle line:90%
space, and then the
name of the community

50
02:09.020 --> 02:10.020 align:middle line:84%
string we want to use.

51
02:10.020 --> 02:16.220 align:middle line:90%
And so it would be Cisco!23, or
whatever you want that string

52
02:16.220 --> 02:16.730 align:middle line:84%
to be.

53
02:16.730 --> 02:19.160 align:middle line:90%
Something a little more secure
this would be a great idea.

54
02:19.160 --> 02:20.990 align:middle line:90%
Space, and then we're
going to specify

55
02:20.990 --> 02:24.800 align:middle line:90%
whether it's a read only
unity string with RO,

56
02:24.800 --> 02:27.330 align:middle line:84%
or is it read/write.

57
02:27.330 --> 02:27.990 align:middle line:84%
Ta da.

58
02:27.990 --> 02:29.370 align:middle line:84%
We now have a community string.

59
02:29.370 --> 02:32.640 align:middle line:90%
And the other details
about location or contact
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
02:29.370 --> 02:32.640 align:middle line:90%
And the other details
about location or contact

60
02:32.640 --> 02:34.530 align:middle line:90%
is above and beyond
what's needed

61
02:34.530 --> 02:37.740 align:middle line:90%
for the basic requirements
for an SNMP manager

62
02:37.740 --> 02:41.315 align:middle line:90%
to go ahead and connect
to this SNMP agent.

63
02:41.315 --> 02:42.690 align:middle line:90%
Now in addition
to this, and what

64
02:42.690 --> 02:43.920 align:middle line:90%
we should do in a
production environment,

65
02:43.920 --> 02:45.420 align:middle line:90%
is we can throw in
an access control

66
02:45.420 --> 02:47.970 align:middle line:90%
list at the end of
this SNMP statement

67
02:47.970 --> 02:51.390 align:middle line:90%
for the community specifying
where the source addresses are

68
02:51.390 --> 02:52.330 align:middle line:84%
allowed to come from.

69
02:52.330 --> 02:55.440 align:middle line:90%
So if we know we have
two or three SNMP servers

70
02:55.440 --> 02:58.050 align:middle line:90%
or management servers and we
know what IP addresses they are

71
02:58.050 --> 03:01.470 align:middle line:90%
or the subnet they're in,
we'd want to explicitly permit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
02:58.050 --> 03:01.470 align:middle line:90%
or the subnet they're in,
we'd want to explicitly permit

72
03:01.470 --> 03:04.200 align:middle line:90%
those, and that way
just not anybody

73
03:04.200 --> 03:08.040 align:middle line:90%
can try to attempt to
access this with SNMP.

74
03:08.040 --> 03:11.010 align:middle line:90%
So an attacker, if
they can't get access

75
03:11.010 --> 03:13.615 align:middle line:90%
based on an ACL logically
applied for SNMP,

76
03:13.615 --> 03:15.240 align:middle line:90%
they're not even
going to have a chance

77
03:15.240 --> 03:17.930 align:middle line:90%
to do a brute force attack with
lots of different passwords.

78
03:17.930 --> 03:20.430 align:middle line:90%
That's a good security measure,
especially with SNMP version

79
03:20.430 --> 03:23.280 align:middle line:90%
2C, where we don't have
a whole bunch of security

80
03:23.280 --> 03:26.370 align:middle line:90%
outside of that ACL and
the community string

81
03:26.370 --> 03:29.460 align:middle line:90%
that we specified as the
password for that access.

82
03:29.460 --> 03:32.490 align:middle line:90%
So next, let's take a
look at an SNMP manager
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
03:29.460 --> 03:32.490 align:middle line:90%
So next, let's take a
look at an SNMP manager

83
03:32.490 --> 03:35.490 align:middle line:90%
that has the ability using this
community string for read/write

84
03:35.490 --> 03:40.307 align:middle line:90%
to connect to this box and make
requests and also set elements

85
03:40.307 --> 03:42.390 align:middle line:90%
based on having the correct
management information

86
03:42.390 --> 03:44.560 align:middle line:84%
base for this router.

87
03:44.560 --> 03:47.508 align:middle line:90%
So this is an example
of a free SNMP manager.

88
03:47.508 --> 03:49.050 align:middle line:90%
It also does a few
other cool things.

89
03:49.050 --> 03:51.360 align:middle line:90%
But for this purpose,
SNMP management.

90
03:51.360 --> 03:53.160 align:middle line:84%
And it's called Observium.

91
03:53.160 --> 03:55.020 align:middle line:84%
Oh my gosh, it is so amazing.

92
03:55.020 --> 03:57.180 align:middle line:90%
So what we're looking
at here is the details

93
03:57.180 --> 04:00.120 align:middle line:90%
for that specific Cisco
router that we just looked
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
03:57.180 --> 04:00.120 align:middle line:90%
for that specific Cisco
router that we just looked

94
04:00.120 --> 04:01.830 align:middle line:84%
at its SNMP configuration for.

95
04:01.830 --> 04:05.550 align:middle line:90%
So to configure the manager
to talk to that router,

96
04:05.550 --> 04:06.930 align:middle line:84%
we would go to the settings.

97
04:06.930 --> 04:08.880 align:middle line:90%
And the interface might look
slightly different based

98
04:08.880 --> 04:10.047 align:middle line:84%
on the manager you're using.

99
04:10.047 --> 04:12.770 align:middle line:90%
But we specify the
protocol version.

100
04:12.770 --> 04:14.083 align:middle line:84%
Version 2C is what we're using.

101
04:14.083 --> 04:15.750 align:middle line:90%
And in the next video,
we'll take a look

102
04:15.750 --> 04:19.170 align:middle line:90%
at SNMP version 3 including the
configuration to make it work.

103
04:19.170 --> 04:21.690 align:middle line:84%
So this one's SNMP version 2C.

104
04:21.690 --> 04:25.660 align:middle line:90%
Transport protocol is using
the default of UDP port 161.

105
04:25.660 --> 04:28.840 align:middle line:90%
And then I simply supplied
the SNMP community,

106
04:28.840 --> 04:31.178 align:middle line:90%
which I grayed out on
the previous screen.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
04:28.840 --> 04:31.178 align:middle line:90%
which I grayed out on
the previous screen.

107
04:31.178 --> 04:33.720 align:middle line:90%
So I don't think I want to click
and show that password here.

108
04:33.720 --> 04:36.720 align:middle line:90%
So with SNMP version 2, the
only option we have for security

109
04:36.720 --> 04:39.340 align:middle line:90%
is this community string,
which I'm using right here.

110
04:39.340 --> 04:41.370 align:middle line:90%
And if we also want to
tack on an access list

111
04:41.370 --> 04:43.590 align:middle line:90%
at the end of that
configuration on the router,

112
04:43.590 --> 04:46.680 align:middle line:90%
that would also protect based
on the addresses where the SNMP

113
04:46.680 --> 04:48.300 align:middle line:84%
manager could come in from.

114
04:48.300 --> 04:51.500 align:middle line:90%
And I got to tell
you that SNMP is so--

115
04:51.500 --> 04:53.620 align:middle line:90%
it's amazing about
what it can collect.

116
04:53.620 --> 04:56.370 align:middle line:90%
For example, if we click
on MIBs right here,

117
04:56.370 --> 05:00.680 align:middle line:90%
the management information
base, I didn't actually
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
04:56.370 --> 05:00.680 align:middle line:90%
the management information
base, I didn't actually

118
05:00.680 --> 05:05.300 align:middle line:90%
tell this management system that
it was a specific Cisco router

119
05:05.300 --> 05:07.550 align:middle line:90%
and you could use
this specific MIB.

120
05:07.550 --> 05:10.880 align:middle line:90%
What it did was, it did a couple
of fairly generic queries,

121
05:10.880 --> 05:12.810 align:middle line:90%
found out what the
device was, and then made

122
05:12.810 --> 05:15.980 align:middle line:90%
a bunch of estimated guesses
on the MIBs associated

123
05:15.980 --> 05:17.900 align:middle line:84%
with that device.

124
05:17.900 --> 05:18.890 align:middle line:84%
It's amazing.

125
05:18.890 --> 05:21.070 align:middle line:90%
So here all the
device MIBs that it

126
05:21.070 --> 05:22.970 align:middle line:90%
is using to communicate
with that device.

127
05:22.970 --> 05:24.470 align:middle line:90%
And so what it can
do is it can have

128
05:24.470 --> 05:26.390 align:middle line:84%
all these MIBs and then test.

129
05:26.390 --> 05:28.700 align:middle line:90%
So each MIB, think of
it like a dictionary

130
05:28.700 --> 05:31.220 align:middle line:90%
of how to get to the
individual components.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
05:28.700 --> 05:31.220 align:middle line:90%
of how to get to the
individual components.

131
05:31.220 --> 05:34.220 align:middle line:90%
And so it enable a
MIB, tried it, and then

132
05:34.220 --> 05:35.600 align:middle line:90%
if a whole bunch
of stuff failed,

133
05:35.600 --> 05:37.200 align:middle line:90%
it could say nothing
matches here.

134
05:37.200 --> 05:38.450 align:middle line:84%
I'm not going to use that MIB.

135
05:38.450 --> 05:41.450 align:middle line:90%
And based on its trial
and error here, look--

136
05:41.450 --> 05:44.250 align:middle line:90%
and also educated guess on
based on the type of device,

137
05:44.250 --> 05:46.530 align:middle line:90%
look at all these
MIBs that it's using.

138
05:46.530 --> 05:48.900 align:middle line:90%
And as an administrator, if
you thought, you know what?

139
05:48.900 --> 05:50.660 align:middle line:90%
There's a few MIBs
in here that are not

140
05:50.660 --> 05:52.890 align:middle line:90%
appropriate for that device that
aren't going to be effective,

141
05:52.890 --> 05:54.557 align:middle line:90%
we could go ahead and
just disable them.

142
05:54.557 --> 05:55.440 align:middle line:84%
Not use them.

143
05:55.440 --> 05:57.720 align:middle line:90%
So an intelligent network
management system,

144
05:57.720 --> 05:59.700 align:middle line:90%
including Observium,
which is free,

145
05:59.700 --> 06:03.230 align:middle line:90%
it does an amazing job
of going in, identifying
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
05:59.700 --> 06:03.230 align:middle line:90%
it does an amazing job
of going in, identifying

146
06:03.230 --> 06:05.930 align:middle line:90%
which MIBs are correct,
and then actually using

147
06:05.930 --> 06:07.340 align:middle line:84%
those to query the device.

148
06:07.340 --> 06:09.080 align:middle line:90%
So based on that, I
mean, check this out.

149
06:09.080 --> 06:10.850 align:middle line:84%
Here's the overview page.

150
06:10.850 --> 06:12.650 align:middle line:84%
So all this information--

151
06:12.650 --> 06:14.840 align:middle line:90%
this is a 2801 router
that I literally

152
06:14.840 --> 06:19.500 align:middle line:90%
had I think in a closet
for more than a year.

153
06:19.500 --> 06:22.430 align:middle line:90%
And I dusted it off, brought
it up, put it online.

154
06:22.430 --> 06:23.080 align:middle line:84%
It's so fun.

155
06:23.080 --> 06:25.160 align:middle line:90%
I also have a couple
more advanced routers

156
06:25.160 --> 06:28.190 align:middle line:90%
which I'll be using in the
next video with SNMP version 3.

157
06:28.190 --> 06:30.590 align:middle line:90%
So it shows the hardware
vendor, the version
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
06:28.190 --> 06:30.590 align:middle line:90%
So it shows the hardware
vendor, the version

158
06:30.590 --> 06:32.330 align:middle line:84%
of software running on it.

159
06:32.330 --> 06:35.150 align:middle line:90%
And all of these
details here, it got,

160
06:35.150 --> 06:38.540 align:middle line:90%
I should say the network
management system got, via SNMP

161
06:38.540 --> 06:40.908 align:middle line:90%
and pulling that device
and asking, please

162
06:40.908 --> 06:42.950 align:middle line:90%
tell me about this and
please tell me about that.

163
06:42.950 --> 06:47.188 align:middle line:90%
And all this information is
fed back via SNMP with SNMP

164
06:47.188 --> 06:48.980 align:middle line:90%
version 2 that we just
configured or looked

165
06:48.980 --> 06:50.990 align:middle line:84%
at on the router itself.

166
06:50.990 --> 06:53.810 align:middle line:90%
It really is amazing,
the amount of information

167
06:53.810 --> 06:56.380 align:middle line:84%
that can be gleaned via SNMP.

168
06:56.380 --> 06:59.660 align:middle line:90%
It's showing us the
interface going up and down.

169
06:59.660 --> 07:02.340 align:middle line:90%
I've got some BGP
status on that device.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

169
06:59.660 --> 07:02.340 align:middle line:90%
I've got some BGP
status on that device.

170
07:02.340 --> 07:04.070 align:middle line:84%
Am I running BGP on that device?

171
07:04.070 --> 07:06.740 align:middle line:90%
I must be, because
the SNMP is reporting

172
07:06.740 --> 07:07.835 align:middle line:84%
what's going on with it.

173
07:07.835 --> 07:09.710 align:middle line:90%
So if we go back to that
router and just show

174
07:09.710 --> 07:16.840 align:middle line:90%
IP BGP S2 summary, yeah, sure
enough, I've got 67 prefixes.

175
07:16.840 --> 07:18.100 align:middle line:84%
And there they go.

176
07:18.100 --> 07:23.810 align:middle line:84%
Or show BGP and IPV for Unicast.

177
07:23.810 --> 07:24.530 align:middle line:84%
Enter.

178
07:24.530 --> 07:25.830 align:middle line:84%
Yet another way to look at it.

179
07:25.830 --> 07:27.860 align:middle line:90%
So that command
is the newer way.

180
07:27.860 --> 07:31.410 align:middle line:90%
But the show IP BGP
also still works.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

180
07:27.860 --> 07:31.410 align:middle line:90%
But the show IP BGP
also still works.

181
07:31.410 --> 07:34.160 align:middle line:90%
So in any event,
that SNMP manager

182
07:34.160 --> 07:36.860 align:middle line:90%
is collecting information
on issues and problems

183
07:36.860 --> 07:37.610 align:middle line:84%
from this device.

184
07:37.610 --> 07:41.450 align:middle line:90%
And I haven't even yet
specified where to send traps

185
07:41.450 --> 07:43.340 align:middle line:84%
or informs to from this device.

186
07:43.340 --> 07:45.440 align:middle line:90%
So all that information
on the network manager

187
07:45.440 --> 07:49.400 align:middle line:90%
is being seen from pulling
this device periodically.

188
07:49.400 --> 07:51.170 align:middle line:90%
And a few minutes
ago, I modified

189
07:51.170 --> 07:52.760 align:middle line:90%
the contact
information regarding

190
07:52.760 --> 07:54.470 align:middle line:84%
the SNMP config on the router.

191
07:54.470 --> 07:57.570 align:middle line:90%
And it just pulled again and
now it's updated as well.

192
07:57.570 --> 07:59.450 align:middle line:90%
So I mean, it's
just really amazing

193
07:59.450 --> 08:01.490 align:middle line:90%
all the detail
that can be gleaned
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

193
07:59.450 --> 08:01.490 align:middle line:90%
all the detail
that can be gleaned

194
08:01.490 --> 08:07.730 align:middle line:90%
via SNMP, processor
information, memory, storage,

195
08:07.730 --> 08:09.940 align:middle line:84%
networks statistics.

196
08:09.940 --> 08:11.330 align:middle line:84%
Also if we go to configuration.

197
08:11.330 --> 08:13.893 align:middle line:90%
Again, the actual
interface for the manager

198
08:13.893 --> 08:16.060 align:middle line:90%
isn't as important as what
some of the functionality

199
08:16.060 --> 08:17.430 align:middle line:84%
is that it provides.

200
08:17.430 --> 08:20.660 align:middle line:90%
We go to properties here
for this specific router,

201
08:20.660 --> 08:22.690 align:middle line:90%
it will once again have
the SNMP configuration

202
08:22.690 --> 08:23.523 align:middle line:84%
if we made a change.

203
08:23.523 --> 08:26.920 align:middle line:90%
So for troubleshooting, and we
think the password is wrong,

204
08:26.920 --> 08:30.280 align:middle line:90%
we could verify, or we even
set the password on the router
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

204
08:26.920 --> 08:30.280 align:middle line:90%
we could verify, or we even
set the password on the router

205
08:30.280 --> 08:31.840 align:middle line:90%
and set the password
in the manager

206
08:31.840 --> 08:34.110 align:middle line:90%
just to verify
that it's working.

207
08:34.110 --> 08:36.159 align:middle line:90%
And then for MIBs,
we could also verify

208
08:36.159 --> 08:39.380 align:middle line:90%
that we have the right MIB
for that model of device.

209
08:39.380 --> 08:41.320 align:middle line:90%
There's a MIB lookup
tool at Cisco.

210
08:41.320 --> 08:44.500 align:middle line:90%
So if I was running iOS
version x on a platform y,

211
08:44.500 --> 08:45.430 align:middle line:84%
I could look that up.

212
08:45.430 --> 08:48.040 align:middle line:90%
Make sure I have the exact
correct MIB for the network

213
08:48.040 --> 08:50.560 align:middle line:90%
management system to
interface and connect and work

214
08:50.560 --> 08:52.360 align:middle line:84%
with that managed device.

215
08:52.360 --> 08:55.600 align:middle line:90%
Now as fun as SNMP version
2 is, it's not very secure.

216
08:55.600 --> 08:57.400 align:middle line:90%
Because the only thing
that's protecting us

217
08:57.400 --> 09:00.755 align:middle line:90%
against an attacker is an access
list displaying the source
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

217
08:57.400 --> 09:00.755 align:middle line:90%
against an attacker is an access
list displaying the source

218
09:00.755 --> 09:03.190 align:middle line:90%
address of who can
connect, which an attacker

219
09:03.190 --> 09:04.870 align:middle line:90%
could spoof and make
it look like it's

220
09:04.870 --> 09:07.300 align:middle line:90%
coming from someone else, and
then do a denial of service

221
09:07.300 --> 09:10.360 align:middle line:90%
attack, as well as the password,
the community string that we're

222
09:10.360 --> 09:11.562 align:middle line:84%
using to manage that device.

223
09:11.562 --> 09:13.520 align:middle line:90%
So in the next video,
we'll kick it up a notch.

224
09:13.520 --> 09:16.240 align:middle line:90%
And like to walk you through the
configuration and verification

225
09:16.240 --> 09:18.040 align:middle line:90%
of both the client
and the server

226
09:18.040 --> 09:22.240 align:middle line:90%
in working with SNMP version 3,
which provides authentication

227
09:22.240 --> 09:23.470 align:middle line:84%
and encryption.

228
09:23.470 --> 09:25.660 align:middle line:90%
So I'll see you in that
next video in just a moment.

229
09:25.660 --> 09:28.060 align:middle line:90%
Meanwhile, I hope this has
been informative for you.

230
09:28.060 --> 09:31.290 align:middle line:90%
And I'd like to thank
you for viewing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

230
09:28.060 --> 09:31.290 align:middle line:90%
And I'd like to thank
you for viewing.