Pandora FMS 2.1: SNMP Traps
Whether we liked it or not, one of the most things we didn’t pay attention to was the SNMP Trap Console in PandoraFMS WebConsole (what a mix up!). We have worked really hard to improve and add some new features to this one. Though it’s not finished yet, these are one of the most importants breakthroughs I’m going to talk about in here.
What did the SNMP Console do?
So far and before this improvements the console was able to recieve traps (from v1), and show the OID of the trap. It was possible to assign alerts as well depending on the Agent (IP) or the OID shown in the Trap Console.
Truth be told, it was ok, but it wasn’t that good.
What does the SNMP Console do?
With the new 2.1 PandoraFMS version it will be possible to play a wee bit more with Traps, Agents and alerts, let me explain what we’ve achieved.
First of all, let me say that all the new SNMP stuff will be only available in our Enterprise Version.
Said that, let’s go to know the new features a little bit deeper.
Now using trap2agent feature it is possible to map certain traps to certain agents (using the IP as a match for this mapping) so, everytime we get a new SNMP Trap with an IP that matchs an existing agent, a new module will be automatically created in the agent containing the OID sent (we now support v1, v2 and v2c. Take a look at the screenshot as follows:
This is pretty useful if you keep in mind you can treat this module as a normal one, so it means you can assign simple or combined alerts to it, so you will have total flexibility with Traps and alerts.
You may tell us that you just don’t want to go and create alerts to each agent, it’s much more useful for you just to create alerts based on an IP or a certain OID or custom value or value sent in the TRAP. Let’s see this with an example
This is a typical trap sent to PandoraFMS:
2008-10-20[**]09:13:58[**]192.168.50.250[**].220.127.116.11.2.1.17[**]6[**]Enterprise Specific[**].2[**].18.104.22.168.22.214.171.124.126.96.36.199.188.8.131.52 = INTEGER: 1 .184.108.40.206.220.127.116.11.18.104.22.168 = STRING: Fa0/2
Let’s tear this Trap into pieces to figure out which fields are interesting for us to define alerts:
Custom value: Up
So in this case, this trap will be mapped to an agent with IP 192.168.50.250 (if it exists).
Once with that information we can define alerts using:
- Custom Value
This gives PandoraFMS an enormous flexibly to play with SNMP alerts, along with agent alerts.
This is an example of a SNMP Console with some alerts in it:
Lastly, it is worth to say that if an agent has a SNMP alert defined, it will appear in its “personal” events fields in its general view. Making the task of reviewing the general SNMP health much easier.
These are new features we’ve been working on lately, the SNMP Console appearance will be changed sooner we want to give it a new look, we’ll get back to you all soon with new articles about it.
El equipo de redacción de Pandora FMS está formado por un conjunto de escritores y profesionales de las TI con una cosa en común: su pasión por la monitorización de sistemas informáticos.
Pandora FMS’s editorial team is made up of a group of writers and IT professionals with one thing in common: their passion for computer system monitoring.