<?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[Help with SNMP Traps to Alarm Browser]]></title><description><![CDATA[<p dir="auto">Hello everyone. I am in need of some help placing SNMP Traps onto the Alarm Browser. I've browsed through the documentation and the forums and am still struggling.</p>
<p dir="auto">I have configured an external NMS system to send traps to NetXMS. The traps are being received: they appear in the SNMP Trap Log and the SNMP Trap Monitor.</p>
<p dir="auto">I've followed the instructions at another post - <a href="https://www.netxms.org/forum/configuration/snmp-trap-configuration/msg13657/#msg13657" rel="nofollow ugc">https://www.netxms.org/forum/configuration/snmp-trap-configuration/msg13657/#msg13657</a> - but haven't had any luck with it. I have created five Event Configuration items:</p>
<p dir="auto">TRAP_RAW<br />
TRAP_INFO<br />
TRAP_EMERGENCY<br />
TRAP_CRITICAL<br />
TRAP_CLOSE</p>
<p dir="auto">The trap OID is .1.3.6.1.4.1.27207.2.2.1.0.1. I've configured the SNMP Trap Configuration to use event "TRAP_RAW" upon receiving an trap with this OID.</p>
<p dir="auto">I have an Event Processing Policy which calls this script when a TRAP_RAW trap is received:</p>
<p dir="auto">if ($event-&gt;parameters[3] == alert)<br />
{<br />
    switch($event-&gt;parameters[2])<br />
    {<br />
        case 1:<br />
            evt = "TRAP_CRITICAL";<br />
            break;<br />
        case 2:<br />
            evt = "TRAP_EMERGENCY";<br />
            break;<br />
        case 3:<br />
            evt = "TRAP_EMERGENCY";<br />
            break;<br />
        case 4:<br />
            evt = "TRAP_EMERGENCY";<br />
            break;<br />
        case 5:<br />
            evt = "TRAP_EMERGENCY";<br />
            break;<br />
        case 6:<br />
            evt = "TRAP_INFO";<br />
            break;<br />
        case 7:<br />
            evt = "TRAP_INFO";<br />
            break;<br />
        case 8:<br />
            evt = "TRAP_INFO";<br />
            break;<br />
    }</p>
<p dir="auto">    PostEvent($node,evt,null,$event-&gt;parameters[7]);<br />
}<br />
else<br />
{<br />
    PostEvent($node, "TRAP_CLOSE");<br />
}</p>
<p dir="auto">I also have two additional Event Processing Policies for creating the alarm and clearing it. However, no alarms are ever created in the Alarm Browser.</p>
<p dir="auto">In summary:</p>
<p dir="auto">I see the traps coming in via tcpdump.<br />
The traps appear in the SNMP Trap Log<br />
The traps appear in the SNMP Trap Monitor<br />
Nothing appears in the Event Monitor<br />
Nothing appears in the Event Log<br />
Alarms are not generated</p>
<p dir="auto">I'm at a loss as to how to troubleshoot at this point. Would anyone be able to lend a hand?</p>
<p dir="auto">Just to cover as many bases as I can think of, here is a copy of the incoming trap from tcpdump</p>
<p dir="auto">09:44:53.154160 IP itbox.49128 &gt; event.snmp-trap:  C= V2Trap(1134)  system.sysUpTime.0=3322126 S:1.1.4.1.0=E:27207.2.2.1.0.1 E:27207.2.1.1.1.1.2=0 E:27207.2.1.1.1.1.3="alert" E:27207.2.1.1.1.1.4=0 E:27207.2.1.1.1.1.5=1400852702 E:27207.2.1.1.1.1.6="" E:27207.2.1.1.1.1.7="Threshold triggered -- switch0.fl2-closet0.wilm's Gi2/0/1's Availability: 0.00 Percent &lt; 100 Percent averaged over 10.00 minutes" E:27207.2.1.1.1.1.8="ITBOX" E:27207.2.1.1.1.1.9=1 E:27207.2.1.1.1.1.10=192.168.10.40 E:27207.2.1.1.1.1.11="switch0.fl2-closet0.wilm" E:27207.2.1.1.1.1.12=1453 E:27207.2.1.1.1.1.13=192.168.10.18 E:27207.2.1.1.2.1.1="Critical Uplinks Availability - switch0.fl2-closet0.wilm - Gi2/0/1" E:27207.2.1.1.2.1.2="" E:27207.2.1.1.2.1.3=0 E:27207.2.1.1.2.1.4="" E:27207.2.1.1.2.1.5=23 E:27207.2.1.1.2.1.6="Uplink ports" E:27207.2.1.1.2.1.7="" E:27207.2.1.1.1.1.14="SNMP" E:27207.2.1.1.1.1.15=1 E:27207.2.1.1.1.1.16="SNMP Poller" E:27207.2.1.1.1.1.17="Gi2/0/1" E:27207.2.1.1.1.1.18=17716 E:27207.2.1.1.1.1.19="core0.wilm gi6/1" E:27207.2.1.1.1.1.20="s1_interfaceavailability" E:27207.2.1.1.1.1.21=120537 E:27207.2.1.1.1.1.22="Availability" E:27207.2.1.1.2.1.8=213743 E:27207.2.1.1.2.1.9=0 E:27207.2.1.1.2.1.10="0.00" E:27207.2.1.1.2.1.11="100" E:27207.2.1.1.2.1.12="Percent" E:27207.2.1.1.2.1.13=2 E:27207.2.1.1.2.1.14="10.00"</p>
]]></description><link>https://forum.netxms.org/topic/3171/help-with-snmp-traps-to-alarm-browser</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 16:05:12 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/3171.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 23 May 2014 13:56:00 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Help with SNMP Traps to Alarm Browser on Tue, 27 May 2014 19:46:22 GMT]]></title><description><![CDATA[<p dir="auto">And I think I just found my own answer with the UnmanageObject function.</p>
<p dir="auto">Thanks for the help Victor! Great product.</p>
]]></description><link>https://forum.netxms.org/post/14009</link><guid isPermaLink="true">https://forum.netxms.org/post/14009</guid><dc:creator><![CDATA[wwwiebe]]></dc:creator><pubDate>Tue, 27 May 2014 19:46:22 GMT</pubDate></item><item><title><![CDATA[Reply to Help with SNMP Traps to Alarm Browser on Tue, 27 May 2014 19:44:05 GMT]]></title><description><![CDATA[<p dir="auto">Booya! That did it. I now have a series of auto-created node's based on trap. Sweet!</p>
<p dir="auto">After creating the node using CreateNode, is there a way to programatically disable polling? I won't have direct access from my netxms platform to the devices sending traps.</p>
<p dir="auto">Thanks again! My event browser is looking awesome.</p>
]]></description><link>https://forum.netxms.org/post/14008</link><guid isPermaLink="true">https://forum.netxms.org/post/14008</guid><dc:creator><![CDATA[wwwiebe]]></dc:creator><pubDate>Tue, 27 May 2014 19:44:05 GMT</pubDate></item><item><title><![CDATA[Reply to Help with SNMP Traps to Alarm Browser on Sat, 24 May 2014 17:18:17 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">Proposed workflow looks correct. I've added description for CreateNode function to our wiki <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/13979</link><guid isPermaLink="true">https://forum.netxms.org/post/13979</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Sat, 24 May 2014 17:18:17 GMT</pubDate></item><item><title><![CDATA[Reply to Help with SNMP Traps to Alarm Browser on Fri, 23 May 2014 17:26:35 GMT]]></title><description><![CDATA[<p dir="auto">Hi Victor!</p>
<p dir="auto">Yes, that fixed my immediate issue. The traps are certainly creating alarms now.</p>
<p dir="auto">My trap sender is an NMS that will send traps on behalf of other devices; ultimately, it is the 'remote device' that I'd like to have referenced as "$node". I've been digging through the documentation and what I think I need to do is create a node on the fly upon trap reception based on one of the OID value's. I think the workflow would work like this:</p>
<ol>
<li>Receive Trap</li>
<li>Identify Remote Node from MIB</li>
<li>Use FindNodeObject to see if the proper node exists</li>
<li>If yes, script a finagling and use PostEvent</li>
<li>If no, create a new object using CreateNode, and then modify the new alarm</li>
</ol>
<p dir="auto">Does this sound feasible to you? Would you be able to provide me with a one-liner as to how CreateNode works and the parameters it needs?</p>
<p dir="auto">Thanks again!</p>
<p dir="auto">Victor W</p>
]]></description><link>https://forum.netxms.org/post/13967</link><guid isPermaLink="true">https://forum.netxms.org/post/13967</guid><dc:creator><![CDATA[wwwiebe]]></dc:creator><pubDate>Fri, 23 May 2014 17:26:35 GMT</pubDate></item><item><title><![CDATA[Reply to Help with SNMP Traps to Alarm Browser on Fri, 23 May 2014 15:49:45 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">Is trap sender added as a node object in NetXMS?</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/13965</link><guid isPermaLink="true">https://forum.netxms.org/post/13965</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Fri, 23 May 2014 15:49:45 GMT</pubDate></item></channel></rss>