NXTI Trap Definitions Missing EXEC Field

[aceplatforms]

As the title states, after processing mibs, the trap definitions that are generated do not have an EXEC field. As a result, every trap is sent to unknown.

[swolf]

Hi @aceplatforms,

I don't think those two issues are related. If your trap definitions are missing EXEC fields, you can add them by editing them in the SNMP Trap Interface.

If your incoming traps are being sent to the unknown traps log, that's a separate issue. Check snmptt.ini to verify that snmptt.conf.nxti is being read, and verify that the snmptt service has been restarted since the last time you processed traps.

EDIT: I felt I should include a little more information about these.
If you click the 'edit' button on any of those post-processing trap definitions, you should see a section for "Passive Service Setup". This adds an EXEC line for snmptraphandling.py, but doesn't list it as an EXEC line in the main trap definition view.

To check snmptt.ini, you'll want to go to the end of the file, where there should be a section like

Code: Select all

[TrapFiles]
# A list of snmptt.conf files (this is NOT the snmptrapd.conf file).  The COMPLETE path
# and filename.  Ex: '/etc/snmp/snmptt.conf'
snmptt_conf_files = <<END
/etc/snmp/snmptt.conf
/etc/snmp/snmptt.conf.nxti
END

If you're only using NXTI to manage trap definitions, the sample shown above will be exactly what you want yours to look like

[aceplatforms]

Hello @swolf! Yep, that's exactly what snmptt.ini looks like. In case you might see something I'm not, here is an example of what shows up in the unknown log for a coldStart:

Code: Select all

Mon Jul  8 11:58:57 2019: Unknown trap (SNMPv2-MIB::coldStart) received from 192.168.252.253 at:
Value 0: 192.168.252.253
Value 1: 192.168.252.253
Value 2: 5:21:40:04.60
Value 3: SNMPv2-MIB::coldStart
Value 4: 192.168.252.253
Value 5:
Value 6:
Value 7:
Value 8:
Value 9:
Value 10:

This is the trap definition I have for coldStart:

Code: Select all

coldStart	.1.3.6.1.6.3.1.1.5.1	Status Events	Normal		A coldStart trap signifies that the SNMPv2 entity, acting in an agent role, is reinitializing itself and that its configuration may have been altered.

I am able to send a custom example trap with this OID and have it show up but when receiving traps from devices, everything still goes to unknown.

[aceplatforms]

I believe I got it working. There must have been an issue with the original snmptt.conf.nxti file. Deleting it and creating a new one with the same permissions seemed to do the trick.

[benjaminsmith]

Hello,

I believe I got it working. There must have been an issue with the original snmptt.conf.nxti file. Deleting it and creating a new one with the same permissions seemed to do the trick.

Excellent. May we close this post or did you need any further assistance. Please let us know.

[aceplatforms]

Traps are working perfectly now. You can go ahead and close the post. Thanks for the help!