Syslog and SNMP

Version 2 by Bren Eckles
on Oct 29, 2012 13:50.

compared with
Current by Bren Eckles
on May 19, 2014 14:04.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (3)

View Page History
GroundWork Monitor incorporates the full Net-SNMP software package, including the {{snmptrapd}} daemon that monitors for incoming trap messages on UDP port 162. {{snmptrapd}} is enabled by default, and will be automatically started after installation.

{Note}GroundWork Monitor does not provide a dedicated startup script for {{snmptrapd}}, but instead starts the daemon as part of the {{/etc/init.d/snmptt startup}} script {{service groundwork restart snmptt}} command that is used to initialize the SNMPTT service. If you ever need to restart the {{snmptrapd}} daemon, you should use that control script.{Note}

Only one SNMP listener can be active on the default port for a network interface, so if you are already using another trap listener for some other purpose you will need to either configure the listeners to use separate network interfaces or port numbers, or integrate the configuration files together (if you are already using {{snmptrapd}} from another source, then you may be able to simply merge the configuration files).
# Once the desired configuration file has been created, it must be added to the {{/usr/local/groundwork/common/etc/snmp/snmptt.ini}} control file before it will be used to interpret matching traps. To add the new configuration file to the control file, open {{snmptt.ini}} in a text editor, locate the "TrapFiles" section towards the bottom of the file, and then add the full path and filename of the new configuration file somewhere before the "END" directive. To simplify management, it is suggested that the new configuration file be copied to the {{/usr/local/groundwork/common/etc/snmp/}} directory beforehand.
# After the {{snmptt.ini}} file has been updated, restart the {{snmptt}} daemon with the following command:
{code}$ /etc/init.d/snmptt restart{code}
{code}service groundwork restart snmptt{code}
Once the above steps have been completed, the SNMP trap translator will begin processing the newly-defined SNMP traps, and will begin generating the correct text strings and severity levels to GroundWork Foundation and Nagios. However, in those cases where the MIB file could not be converted, some amount of manual intervention will be required.