<?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[Anyway to make Proxy Nodes subnet aware in their zone]]></title><description><![CDATA[<p dir="auto">So it looks like proxy nodes are not subnet aware when added to a zone, what I mean by that is take the following</p>
<p dir="auto">NetXMS Server Public WAN<br />
All agents using agent to server tunnel configuration.</p>
<p dir="auto">Zone A (with proxynodes 1 &amp; 2 set under properties, communications, Proxy nodes)<br />
Subnet 192.168.1.0/24</p>
<ul>
<li>SNMPdevice1 - 192.168.1.2</li>
<li>ProxyNode1 - 192.168.1.3</li>
<li>WindowsAgent1 - 192.168.1.4</li>
</ul>
<p dir="auto">Subnet 172.16.16.0/24</p>
<ul>
<li>SNMPdevice2 - 172.16.16.2</li>
<li>ProxyNode2 - 172.16.16.2</li>
<li>WindowsAgent2 - 172.16.16.2</li>
</ul>
<p dir="auto">Now in the console, I will randomly get device offline in each subnet, as though it appears to not have any defined or exposed method of selecting which ProxyNode is used for the subnet.  If I select SNMPDevice2 I can manually goto it's properties and choose Communications and specify the ProxyNode2 (thus overriding the Zone A defaults) and this clears the communications errors.</p>
<p dir="auto">These Zones can be logical or physical separations, for example, different parts of a DMZ, or separate buildings / offices but still communicate back to say the same set of servers.  For example desktops in subnet 1 &amp; 2 talk to servers in subnet3 but not each other.</p>
<p dir="auto">My Question - <br />
Are the Proxy Nodes subnet aware and if not<br />
Is there a way to set the communication Properties per subnet?  It seams selecting the subnet properties doesn't have that option and it would be a huge benefit (at least to me) to control communication via the subnet layer.</p>
<p dir="auto">Thank You</p>
]]></description><link>https://forum.netxms.org/topic/7651/anyway-to-make-proxy-nodes-subnet-aware-in-their-zone</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 11:48:49 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7651.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 23 Mar 2023 19:15:21 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Anyway to make Proxy Nodes subnet aware in their zone on Thu, 06 Apr 2023 09:55:09 GMT]]></title><description><![CDATA[<p dir="auto">Multiple proxies within one zone intended for load balancing and HA - so all proxy nodes should be able to communicate with all nodes within zone. Server will distribute load between proxy nodes, and yes, this process is not subnet-aware (and is not intended to be).<br />
If two subnets you have are actually in two different locations, you can split them into separate zones and assign correct proxies.<br />
Overriding proxy on subnet level can be implemented relatively easy if load balancing and HA functionality is not required - i.e. only one proxy set on a subnet, it overrides any zone setting, and if this proxy is not functioning, communication with the subnet s lost. Replicating full zone proxy functionality on subnet level will significantly increase complexity of necessary changes, and in my opinion will be unnecessary duplication of functionality that is already exist.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/32354</link><guid isPermaLink="true">https://forum.netxms.org/post/32354</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 06 Apr 2023 09:55:09 GMT</pubDate></item><item><title><![CDATA[Reply to Anyway to make Proxy Nodes subnet aware in their zone on Fri, 31 Mar 2023 09:08:33 GMT]]></title><description><![CDATA[<p dir="auto">Plus one, subnet-level would be a great place to be able to define a proxy.</p>
]]></description><link>https://forum.netxms.org/post/32343</link><guid isPermaLink="true">https://forum.netxms.org/post/32343</guid><dc:creator><![CDATA[troffasky]]></dc:creator><pubDate>Fri, 31 Mar 2023 09:08:33 GMT</pubDate></item></channel></rss>