Nagios Support Forum

The way Traps work is that the snmptrapd daemon receives a trap and sends it on to the snmptt daemon (SNMP Trap Translator).
In the /etc/snmp/snmptt.conf file, are all of the OIDs that it should process and if there is a match, it will send it to the XI process.
If it doesn't match, it goes in to the unknown log.

The snmptt.conf file is populated by the XI GUI if the Process Traps button is selected and that the MIB file has TRAP OID's in them.
You can try and add the MIB's again from the command line by running the following. Every time you run this or edit the snmptt.conf file, you will have to restart the Trap Translater by running Try that and see if it works, if not, can you post this file? Here is a link to a SNMP Trap tutorial that describes the process, read through it and let us know if you have any questions.
https://support.nagios.com/kb/article.php?id=77

I have two queries.

I am running purl script in plugin.

While using check_cisco_cpu.pl, in command I was able to use macro $HOSTADDRESS$ and it was correctly selecting IP against it.

whereas using plugin from https://exchange.nagios.org/directory/P ... st/details, if I use macro $HOSTADDRESS$ in command, prompt asking for IP address pop up, so i have to enter address and then command will execute. Why it cant pick up hostaddress based on macro input like first plugin.

2. I am having trouble to run eigrp plugin, below error is killing me. i have all MIB installed if I am correct. How should i resolve it




[root@localhost libexec]# ./check_eigrp.pl
Bad operator (Unsigned32): At line 148 in /usr/share/snmp/mibs//ctc.my
Did not find 'Unsigned64' in module CISCO-TC (/usr/share/snmp/mibs//CISCO-CONFIG-MAN-MIB.my)

ERROR "Timeout" querying 0.



[root@localhost mibs]# grep -R 'CISCO-TC'
ctc.my:-- CISCO-TC.my: Cisco MIB Textual Conventions
ctc.my:CISCO-TC DEFINITIONS ::= BEGIN
CISCO-CONFIG-COPY-MIB.my: CISCO-TC"
CISCO-CONFIG-MAN-MIB.my: FROM CISCO-TC
[root@localhost mibs]#

1. The nagios process expands the $HOSTADDRESS$ macro when it runs the check, the command prompt cannot do that.
2. You may want to check those 2 MIB files and they look to be corrupt. ctc.my and CISCO-CONFIG-MAN-MIB.my have something wrong with them.