Snmptraps automatic detection

[angurisudhakar]

Hi,
Why does Nagios not automatically detect the description “alarm string” from the MIB that it has imported and display that?

Is there any way for mib file import and automatically detect snmptt.conf file for all the services.?

Please let me know

Thanks,
Anguri sudhakar.

[ssax]

Please attach the MIB file and show us the exact trap in your /etc/snmp/snmptt.conf so that we can look more into it.

The MIBs need to be manually imported (either through the web UI or using the addmib command) which will put all the traps defined in the MIB file into /etc/snmp/snmptt.conf where you can adjust them to what you need. Then you restart the snmptt service.

[angurisudhakar]

Thanks for your input i have used same command for import the MIB file into /etc/snmp/snmptt.conf.

But Traps are allays going to /var/log/snmptt/snmpttunknown.log this file,
Please let me know the solution.

below is the files:
#/var/log/snmptt/snmpttunknown.log
Tue Sep 22 05:50:54 2015: Unknown trap (admin.ms.add) received from 10.213.92.70 at:
Value 0: 10.213.92.70
Value 1: 10.213.92.70
Value 2: .1.3.6.1.4.1.36400.3.0.24
Value 3: admin.ms.add
Value 4: 10.213.92.70
Value 5:
Value 6:
Value 7:
Value 8:
Value 9:
Value 10:


#/etc/snmptt/snmptt.conf

EVENT adminDetailedLoggingEdit .1.3.6.1.4.1.36400.3.0.24 "Status Events" Normal
FORMAT Trap indicates that an user has enabled or disabled detailed logging in the MRB $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "adminMediaServerAdded" "$s" "$@" "$-*" "Trap indicates that an user has enabled or disabled detailed logging in the MRB $*"
SDESC
Trap indicates that an user has enabled or disabled detailed logging in the MRB
Variables:
1: event
2: whoSentTrap
3: otherInformation
EDESC



Thanks,
Sudhakar Anguri.

[Box293]

Did you restart the snmptt service afterwards?

Code: Select all

service snmptt restart

[angurisudhakar]

Yes i have restarted the service snmptt ..many time.

Please let me know the troubleshooting for those traps.

[Box293]

At this point, if you enable debug logging in snmptt.ini you can then see why snmptt is not detecting the trap in snmptt.conf. Be aware that the debug logging is quite detailed, which is actually very helpful.

[angurisudhakar]

Thanks for your input....

[tmcdonald]

Did anything come up in the debug logs?

[angurisudhakar]

No.. we are again cross checking with MIB files.

I will let you know the status.

[lmiltchev]

I will let you know the status.

Sure. We will keep the thread open.