NetXMS Support Forum

Victor - sorry for wasting your time.  I had looked at those OID's over and over again yesterday and could not spot the typo. Of course now i have corrected it, everything works fine.

I have been looking at a bunch of software in this area and NetXMS has been head and shoulders above everything else I have tried. I am looking forward to what you have planned for future releases. Thanks.

Hi Victor,

Thanks for getting back to me. Here are the screen grabs you requested. The event at 15:33:09 is the one I am interested in.

Event & Traps Logs:



Trap Configuration:



Event Configuration:



For reference, the complete 'Varbinds' field from the Traps logs reads:

.1.3.6.1.4.1.674.10982.1.5000.10.1.0=='netxms_test'; .1.3.6.1.4.1.674.10892.1.5000.10.2.0=='.1.3.6.1.4.1.674.10892.1.600.12.1.2.1.2'; .1.3.6.1.4.1.674.10982.1.5000.10.3.0=='Power supply detected a failure Sensor location: Power Supply 2 Chassis locati


Cheers Stoo.

Server OS = Redhat (RHEL4 / Update 6)
NetXMS = 0.2.19

Console = 0.2.19 running on Windows XP.

I am trying to match SNMP Traps to NetXMS events. I managed to get this to work once, but now all traps show up in the Event logs as 'SNMP_UNMATCHED_TRAP'.

Steps followed (using http://tinyurl.com/25249y as a reference):

• Copied the mib file into the NetXMS mibs directory and run nxmibc sucessfully
• Set LogAllSNMPTraps = 1
• Confirmed that I can see traps arriving from a test host in SNMP Trap Log
• Created a new NetXMS event, providing a 'Name', checked the 'Write to event log' checkbox, set 'Message template' to %2 (to match the contents of a returned parameter with the trap)
• Created a new Trap Configuration, providing a 'Description', pasting the 'Trap OID' as taken from the SNMP Trap Log (and confirmed in the MIB Browser), selecting the previously created event, not entering anything in 'Tag', and finally adding one 'Parameter Binding' using the contents of one of the variables returned by the trap

At this point I was expecting any matching traps arriving at the box to be matched to the corresponding event, but instead they still show up as 'SNMP_UNMATCHED_TRAP' in the event log.

I have gone on to provide a matching rule in the 'Event Processing Policy' and restarted all components, but this has no effect. I can see nothing in the netxms log file (last entry refers to the server starting).

I did get the first trap working as expected. I could see no difference in the subsequent traps that I set up that did not work. I finally deleted all configs, to start again, and now none work.

Please can anybody point me in the direction of what I am missing?

Cheers Stooo.