In the previous video, we looked at the configuration
on the router for SNMP version 3,
which included views, groups, which have permissions
associate with those views, and then users, which
are associated with the groups.
So in this video, I'd like to look at the back half of that,
which is how do we train our SNMP manager to manage
a device using SNMP version 3?
So without further ado, let's go to our management station
and in this demonstration, I'm using
Observium as a free SNMP manager that's perfect for the task. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Observium as a free SNMP manager that's perfect for the task.
So here on the SNMP manager, I simply
said, OK, we're using version 3.
I specify we're using the default port of UDP port
161 for the SNMP.
And then over here for SNMP version 3 authentication,
because I said SNMP version 3 here, said OK, great,
what type of security are you using?
So there's three options here.
authPriv says we're doing authentication, right?
That's that hashing piece.
And we're also doing encryption, which is the privacy piece.
So authPriv like this means we're doing both. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So authPriv like this means we're doing both.
So what if you want to do authentication
but you don't want to do any encryption for whatever reason.
Maybe your device doesn't support it.
This is the option you'd pick.
So authNoPriv simply says I want to do
the authentication, the hashing, but I'm not
going to use the encryption.
So at the router, I specified that we're using authentication
and we're using encryption, the privacy option.
But if I'd said we're just using authentication
and no privacy, no encryption, I would select authNoPriv here.
Or if you don't want any of the authentication
and you don't want any of the encryption,
you might as well use SNMP version 2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
you might as well use SNMP version 2.
However, there is options for that, too.
So no auth, no Priv, means you're not
doing the authentication, you're not doing the encryption.
But we're still using SNMP version 3, but just not taking
advantage of the benefits.
So if we are using auth and priv,
you need to put in the details for that.
So for the authorization username,
I'll put the username and the password.
Also the hashing algorithm that we're using for authentication.
And then furthermore, because we're using priv,
meaning encryption, I specify the password
that I specified for encryption and I also WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that I specified for encryption and I also
specified the flavor.
Now when I initially set this up,
I don't recall if I used 128 or 256.
I know the user I just set up used 256.
So here, I'm looking at it.
If I was troubleshooting this and it wasn't working,
I might want to go back to the router and set 128.
Or as a test, you might want to do no auth no priv just
to verify basic communications and then come back here and add
those features.
So whatever you do to troubleshoot
to set up a new device, you have the options here.
You could also test with version 2 with just a community string. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
You could also test with version 2 with just a community string.
Set the router up to support it.
If that works, then we could know
that the actual port's available and it's not
being blocked in transit.
So getting a working baseline, finding a piece that does work
and then adding on from there is not a bad idea as well.
All right.
So that that is already configured and done.
And as a result, this has been up for like maybe two hours
now.
So if you get an overview of this device,
it has pulled all the details via SNMP version 3.
That's what it's currently using. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That's what it's currently using.
There's graphs, that's the availability, the uptime,
processor information, memory information, storage,
network statistics.
And again, all of these are based
on this SNMP manager going out periodically,
I think it's every 10 minutes by default, and pulling.
Another important aspect is that if we want an SNMP
agent to send messages to the server it on its own like,
oh, this was just exceeded or this interface went down,
we need to train the SNMP agent or the client to do that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we need to train the SNMP agent or the client to do that.
And that's what the command SNMP dash server space
host, and then the credentials, if it's version 2 the community
string, if it's version 3, the client information, to send
those traps.
So if we're expecting messages out of the blue
to come from an SNMP agent or a client,
we're not going to see them unless we've
trained the SNMP agent or client to know where that SNMP server
is that it should send them to.
So back on this device, if we went to the properties of this
once again and we clicked on MIBs, once again,
I got to tell you, this network management station, Observium, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I got to tell you, this network management station, Observium,
it just made some estimated guesses on what that device was
based on some initial polling and then it
through all these MIBs at it based
on what it thought it was.
And as an administrator, we can go in and say, you know what?
This MIB is not appropriate for that.
I want to take that off, take that off, and remove them.
And the key is, we want our network management station
to have the correct MIBs or the correct enough MIBs
to adequately address and get information
about all the pieces on that device that
are available as object IDs as part of the MIB
or that managed device. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
or that managed device.
So it's amazing stuff.
And although it does take a little more work
to set up SNMP version 3, it is worth
it to have the security involved with the authentication
and the encryption that SNMP version 3 brings to the table.
All right.
In the next video, I'd like to talk
with you about troubleshooting.
Whether it's version 2 or version 3,
if SNMP is not working, I'd like to share with you
the top things to look at that are probably
causing the problem.
And we'll do that in the next video.
So I'll see you there in just a moment.
Meanwhile, I hope this has been informative for you.
And I'd like to thank you for viewing. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I'd like to thank you for viewing.