<![CDATA[SNMP_UNMATCHED_TRAP issue]]>Hi,

After adding a new MIB using nxmibc  -d "c:\Program Files\NetXMS\var\mibs" -z
 I moved netxms.mib to the mibs folder and restarted the core service.
I proceeded to add a new trap mapping .1.3.6.1.4.1.5597.50.1 (I could select it with the MIB browser which I guess proves the above steps succeeded)
Finally a went on and added an event template and Event Processing Policy.

When I trigger the SNMP trap I receive the following (error) in the Event Browser:
SNMP_UNMATCHED_TRAP SNMP trap received: .4.11.93.0.99 (parameters: 1.3.6.1.4.1.5597.50.1.99 == ...)
I get the same message even when I map to 1.3.6.1.4.1.5597.50.1.99
So apparently the trap Is perceived as a parameter, what am I doing wrong?

Dan

]]>https://forum.netxms.org/topic/1453/snmp_unmatched_trap-issueRSS for NodeFri, 13 Nov 2026 15:41:08 GMTWed, 23 Nov 2011 14:24:08 GMT60<![CDATA[Reply to SNMP_UNMATCHED_TRAP issue on Thu, 24 Nov 2011 09:41:26 GMT]]>Hi lindeamon,

Thanks for the tips. The trap OID’s returned by following your advice were identical to those shown in the Event Browser.
Digging further on the net for the .4.11.93.0.99 trap I've discovered "Time Server Monitor" from Meinberg is probably the culprit as someone else using a different monitoring software was getting the same wrong OID’s. I guess 'Time Server Monitors" emits different traps than their own MIB file states.
 Since NetXMS seems to accept the wrong OID and triggers on it I’ll get used to live with it 

Regards,

Dan

]]>https://forum.netxms.org/post/6336https://forum.netxms.org/post/6336Thu, 24 Nov 2011 09:41:26 GMT<![CDATA[Reply to SNMP_UNMATCHED_TRAP issue on Wed, 23 Nov 2011 15:05:48 GMT]]>hi DanG,

you can use the snmp trap log in the old console and in the column "Trap OID" you will find the OID you should enter in the trap mapping.
the var binds in the trap mapping configuration are according to the trap sent (ex. in netapp when volume is offline varbind 1 in position 1 will give the trap data).
in the event configuration in case the event is relating to snmp trap you should write the varbinds from %2 meaning trap varbind #1 will be event %2 due to the fact that in case of snmp traps %1 is always the trap OID.

maybe this will help you solve ypur problem
Lindeamon

]]>https://forum.netxms.org/post/6332https://forum.netxms.org/post/6332Wed, 23 Nov 2011 15:05:48 GMT