So now that we've configured our Linux host for monitoring,
let's go into the monitoring system and add our main file server.
Now that we've allowed ICMP,
it should be a lot easier to actually start monitoring on this guy.
So we don't see it here in the list.
The system has not actually gone and done another network discovery,
so we have to go manually add the device.
So we will go up here under Windows, Servers, click Add Device.
We're going to name the device name something more accurate than device,
GLOBO-SRV-1, it's connecting it using IPv4.
The IPv4 address is 192.168 .150 .4.
In this particular system, we can add tags to the system if we wanted to.
And we'll give it a nice device icon, something like that.
And now we're asked for the device type.
We can just add it manually and then go in and manually
add all of the sensors if we want to.
I'm going to choose the second option, Automatic Device Identification,
detailed may create many sensors and we're going to discover it once.
We could say do a rediscovery on this guy every hour, day, or week.
If you have a device that say has lots of disks that come in and out,
you could rediscover it every so often.
So now it wants the credentials for Windows system.
We didn't specify that whenever we did the root level
configurations so I'll uncheck this to not inherit.
It will say domain or computer name.
I did not go to the trouble of setting up an AD domain since
I only have the two Windows servers so we will assign the
computer name as GLOBO-SRV-1, the user will be my user and my password.
So now that that's done, we can scroll down,
and in theory, we could uncheck the inheritance for SNMP configuration,
but we configured that up at the root.
So we'll leave the rest of this the same, and we will hit OK.
So now it's running an auto-discovery on GLOBO-SRV-1.
We'll go into the Device page,
and we'll just wait until the auto-discovery is complete and
that took much longer than I was expecting.
I guess maybe I should have picked the first option
to just do the initial light scan, but it took 23 minutes and we have 2 sensors,
ping and RDP, because again, this server is not really doing much of anything.
So what we're going to do is we're going to manually add a sensor now.
So we'll hit Add Sensor, and we want to say Disk Usage on a Windows system,
and we want to use SNMP to do it.
If that's the case, we have SNMP Disk Free,
so we'll hit plus to add to our server,
and we see that we have two disks on our server that it discovered via SNMP,
so we're going to monitor all of them.
We're going to inherit the scanning interval,
which is every 60 seconds, and we'll hit Create.
While we're at it,
let's add a CPU sensor as well so we're going to say CPU
Usage on Windows via SNMP and SNMP CPU Load.
Hit plus and there are really no settings for this
since you're just monitoring the CPU.
You don't choose to monitor or not monitor I suppose.
But now we see the disk free on CND in the SNMP CPU load and it has
to pull this data so we'll wait just a few more minutes and let it
pull a bit of data for all of these sensors and we'll have a look
at what it actually does.
And now that we've gotten a little data under our belt,
we can actually click on say the Disk Free and it will show us that
our disk right now is 91% free because again,
there is nothing on this particular server.
But what this allows you to do is base your management
and monitoring off of disk free space, for example,
in this example,
and if you have a drive that runs say an Exchange database that you really,
really don't want it to run out of disk space,
you can set an alert to say when this gets down to 90% used,
10% free space, send me some kind of alert,
and to tie all that back into the subject of the course,
most of this data is gathered via SNMP.
Again, on Windows platforms,
you can use WMI and even some PowerShell here and there,
but for Linux and Cisco routers and other infrastructure devices,
you're firmly in the world of SNMP and really the whole reason why
you configure SNMP and go to all the trouble of setting up a network
monitoring system is for exactly this,
you want to know before your users tell you if a device goes
down and if a server runs out of disk space.
It makes IT, in general,
look a lot better whenever users call up and say hey my phone just went dead.
Yeah, we know.
One of our switches went down.
We'll have it back up here in a few minutes.
Or even better, send a proactive alert to the affected users saying hey,
there are telephony problems because the power went out or whatever.
Here I am waxing eloquent about network monitoring and IT governance,
in general.
I'm sure you just want to know about SNMP.
So that shows us all of the monitors that are on this server.
We're checking it for ping and remote desktop disk
free on C and D and the CPU load.
We can actually click on the CPU load and it'll tell us that the server is
kind of bored because again it's not really doing anything.
So in the last section of this module, we are going to configure SNMP on a Cisco iOS device.