<?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[Multiple Node Status]]></title><description><![CDATA[<p dir="auto">Hi Victor,</p>
<p dir="auto">I have created a node (Ex: NODE-A) of my device having IP address (192.168.200.130). My device is connected with another device by means of optical fibre. That device does not have any physical IP interface. But still I have created another node (Ex: NODE-B) with the same IP address of NODE-A. Both the devices are having their own set of SNMP traps which NODE-A sends to the server. SNMP traps of both the node's are always being sent by NODE-A.</p>
<p dir="auto">My aim is to configure NetXMS server in such a fashion that when NODE-B specific trap comes I should be able to change the status of NODE-B only (although the trap source is NODE-A).</p>
<p dir="auto">I have configured the specific traps and events accordingly. I have also configured the Event policies for all the traps but unfortunately I could only be able to change the status of NODE-A not NODE-B. I am not able to distinguish the traps specific for NODE-A and NODE-B.</p>
<p dir="auto">Please help.</p>
<p dir="auto">Regards,<br />
tamal_g</p>
]]></description><link>https://forum.netxms.org/topic/2755/multiple-node-status</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 13:26:26 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/2755.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 28 Nov 2013 10:05:31 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Multiple Node Status on Fri, 29 Nov 2013 15:26:21 GMT]]></title><description><![CDATA[<p dir="auto">Once again thanks for your help.</p>
<p dir="auto">Exactly the same logic what I implemented and it worked.</p>
<p dir="auto">Thanks once again</p>
<p dir="auto">Chz!!!</p>
<p dir="auto">Regards,<br />
tamal_g</p>
]]></description><link>https://forum.netxms.org/post/12049</link><guid isPermaLink="true">https://forum.netxms.org/post/12049</guid><dc:creator><![CDATA[tamal_g]]></dc:creator><pubDate>Fri, 29 Nov 2013 15:26:21 GMT</pubDate></item><item><title><![CDATA[Reply to Multiple Node Status on Fri, 29 Nov 2013 13:25:01 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">Global variable $node always points to source node of event being processed, node A in your case. You have to find node object for node B using FindNodeObject (<a href="http://wiki.netxms.org/wiki/NXSL:FindNodeObject" rel="nofollow ugc">http://wiki.netxms.org/wiki/NXSL:FindNodeObject</a>) function, like this:</p>
<p dir="auto">nodeB = FindNodeObject($node, "NodeB");<br />
PostEvent(nodeB, "MY_EVENT", null, ...); // add parameters as required</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/12048</link><guid isPermaLink="true">https://forum.netxms.org/post/12048</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Fri, 29 Nov 2013 13:25:01 GMT</pubDate></item><item><title><![CDATA[Reply to Multiple Node Status on Fri, 29 Nov 2013 10:01:42 GMT]]></title><description><![CDATA[<p dir="auto">Thanks Victor.</p>
<p dir="auto">I Have tried to implement as suggested by you. But the problem is all the event's source node is NODE-A and whenever I have passed the $node object, the $node-&gt;name is always having the name of NODE-A. I am not able to change the status of NODE-B with their specific traps.</p>
<p dir="auto">Can you please give me some more details on how to implement PostEvent() function on this particular configuration?</p>
<p dir="auto">Regards,<br />
tamal_g</p>
]]></description><link>https://forum.netxms.org/post/12044</link><guid isPermaLink="true">https://forum.netxms.org/post/12044</guid><dc:creator><![CDATA[tamal_g]]></dc:creator><pubDate>Fri, 29 Nov 2013 10:01:42 GMT</pubDate></item><item><title><![CDATA[Reply to Multiple Node Status on Thu, 28 Nov 2013 11:31:02 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">Currently there are no simple solution. What you possibly can do is to catch events from node A which are in fact related to node B, use NXSL script as action for them, and use PostEvent function (<a href="http://wiki.netxms.org/wiki/NXSL:PostEvent" rel="nofollow ugc">http://wiki.netxms.org/wiki/NXSL:PostEvent</a>) to re-send same (or different) event on behalf of node B.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/12039</link><guid isPermaLink="true">https://forum.netxms.org/post/12039</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 28 Nov 2013 11:31:02 GMT</pubDate></item></channel></rss>