<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Sending SNMP Trap from NetXMS to another NMS]]></title><description><![CDATA[<p dir="auto">I've an SNMP Agent which supports only SNMPQuery. We would like to send notification when value of OID reached to high-water-mark. These notification meaning SNMP-Trap to another NMS, SMS and Email notification.<br />
Hence I'm looking for some kind of Event Generation support into "Transformation Script". Event Processing should also facilitate me for defining multiple actions for an event, like Generate a TRAP, Send SMS, email, etc</p>
<p dir="auto">Above functionality could be boon for software which doesnot support SNMP but can provide information in file. NetXMS can read file and generate an alert (TRAP/SMS/Email) when particular content is found.</p>
<p dir="auto">NetXMS can be though of being SNMP Trap proxy and can enrich some compatibility related information.</p>
]]></description><link>https://forum.netxms.org/topic/1278/sending-snmp-trap-from-netxms-to-another-nms</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 09:26:57 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/1278.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 07 Jul 2011 08:19:27 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Sending SNMP Trap from NetXMS to another NMS on Thu, 07 Jul 2011 15:04:10 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">I don't think that transformation script is a right place for SNMP trap generation. Normally you should create threshold, and generate traps, send emails, etc. from event processing policy via actions. Currently you don't have built-in option for SNMP trap sending, but you can use any command line tool capable of sending SNMP traps and call it via "execute command" action. I agree that having built-in SNMP trap sending action is a good feature, but until it is not implemented, there is workaround.</p>
<p dir="auto">As for multiple actions for event - you already can do that - in one rule in event processing policy you can specify multiple actions.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/5671</link><guid isPermaLink="true">https://forum.netxms.org/post/5671</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 07 Jul 2011 15:04:10 GMT</pubDate></item></channel></rss>