Monitoring SNMP Traps from ESX hosts in Opsview (Part 2)

This was done on an Ubuntu 10.04 LTS server. The steps are probably the same on Debian systems.

1. Make sure you have snmpd installed. If you don’t, install it! Easy as pie.

aptitude install snmpd

2. Edit /etc/snmp/snmpd.conf and uncomment “master agentx”. 3. Edit /etc/default/snmpd (or /etc/snmp/snmptrapd.conf on newer systems):

TRAPDOPTS='-t -m ALL -M /usr/share/snmp/mibs:/usr/local/nagios/snmp/load -p /var/run/'
SNMPDOPTS='-u nagios -Lsd -Lf /dev/null -p/var/run/'

4. Edit /etc/snmp/snmptrapd.conf and add the following lines:

traphandle default /usr/local/nagios/bin/snmptrap2nagios
disableAuthorization yes

Please note that this will make the server listen to and handle any SNMP traps it receives, regardless of source. 5. Restart snmpd and snmptrapd:

/etc/init.d/snmpd restart

6. Edit the /etc/sudoers file to allow Opsview to restart snmpd and snmptrapd:

nagios ALL=NOPASSWD:/usr/local/nagios/bin/snmpd reload

7. Test the permissions:

su - nagios
sudo /usr/local/nagios/bin/snmpd reload

8. Exit back to the root user and restart opsview-web:

/etc/init.d/opsview-web restart

That’s all. Opsview should now be able to handle traps sent to it.

About the Author

Marcus Vejneke holds a bachelor’s degree in computer science and engineering and has worked in IT for almost 14 years. Marcus lives in Sweden and works as Sysadmin. Visit Marcus's blog.

Legal Disclaimer

This blog post is contributed by a member of the Opsview community. Opsview accept no responsibility for the accuracy of its content and are not liable for any direct or indirect damages caused by its use.



niels's picture
5 December 2011 - 12:05pm

Any ETA on when to expect information regarding how to write a couple of service check handlers in Opsview to make sense of the traps? (As you mentioned at the beginning of this post).

Keep up the good work!


Call us for a quote


International numbers