A guide on how to monitor Juniper EX switches using SNMP and Opsview.
You are here
How to do an SNMP walk
This guide shows you how to run an SNMP walk in Opsview. An SNMP walk is a simple way to set up the collection of information from your routers, switches or other SNMP enabled devices. The SNMP walk will allow you to see all of the OID parameters available on your SNMP device and then set rules against the values. This will give you exactly what you need to actually start monitoring a device.
Loading a MIB file
MIB files link the OIDs to human readable parameter definitions, these files are normally provided by the device vendor. This step is optional, MIB files are not required for the SNMP walk, but they do make the parameters easier to identify when running an SNMP walk.
OIDs are the codes used to identify each parameter available via SNMP on the device, they look something like:
Loading MIB files into Opsview is a simple process, instructions on how to do it can be found here:
Adding the host
You will need to add the host before running the SNMP Walk. Just add the host in the normal way setting the IP and Host title and any of the other parameters you require.
Figure 1 - Adding the host
When adding the host, if you have added a MIB file, make sure you load the "SNMP – MIB-II" host template, this allows the host to use the MIB file.
Figure 2 - MIB template
Once you have finished configuring the Host tab select “Next” and then go to the “SNMP” tab. Configure the SNMP settings for the host, in Opsview version 4.6 the SNMP community string will be encrypted for added security:
Figure 3 - SNMP Settings
Submit the changes, and that is your host set up, we will run the SNMP walk in the next step.
Running the SNMP walk
To run the SNMP walk first, add a new service check. Select “SNMP Polling” for the “Type of Check” and then fill in the “Example Host” with the host identifier of the new host you just added.
Then select the “SNMP Walk” link next to the host name.
Figure 4 - SNMP walk results
Once the walk has completed you will see all of the OIDs available on the device. Next just select the relevant OID and define any rules you would like against it:
Figure 5 - OID selection and rules
You can do this a few times to create multiple service checks against your host, you can even put all of these rules into a host template in order to apply them to multiple hosts. For example if a server is getting too full, or if a service is up and running or not.
And that is it, this simple method will get you monitoring your SNMP devices in no time.
Opsview also supports SNMP traps, allowing you to configure your devices to report into your Opsview system rather than Opsview reading the devices, you can find information on setting this up on our documentation pages here:
More like this
In this guide, I will show you a quick and easy way to get open source syslog monitoring using Opsview that can also be applied to Nagios.
Monitoring software does not serve the purpose of replacing technical talent. Instead, it is there to make the lives of technical resources easier...