<?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[Network Discovery finds hundreds of subnets]]></title><description><![CDATA[<p dir="auto">LAN has 2 networks: 192.168.15.0/24 and 192.168.2.0/24.  NetXMS is 5.1.0/Windows.</p>
<p dir="auto">When I run a discovery (active &amp; passive), NetXMS finds over 400 additional subnets.  None of the subnets have devices found in them; netxms only finds the subnets.  See attached image for what I mean.</p>
<p dir="auto">I have my 'Active Discovery Targets' set to 192.168.15.1 to 192.168.15.254.  I understand why it is finding the 192.168.2.0/24 subnet, and the devices, and that's great.</p>
<p dir="auto">But the other subnets are noise or a ghost or something.  How can I hide them?  I tried creating a new zone and was just going to dump them all there, but NetXMS doesn't allow me to move the subnets to the new zone.</p>
<p dir="auto">Things I tried</p>
<ol>
<li>A filter. Not possible, there are just too many.  If NetXMS had the option to ! (negate) a filter, I could just put !(192.168.15.0/24,192.168.2.0/24) and that could work I guess.  But it doesn't have a negation option.</li>
<li>I could use only active scan. I'm trying that now, after having just deleted all the other subnets.  But I do arp monitoring, and I never see addresses for those other subnets, so I don't know why they're appearing in the first place. And honestly I'd rather just leave active + passive on.</li>
<li>Move the unwanted ones into a 'Junk' zone. But NetXMS doesn't let me move them.</li>
</ol>
<p dir="auto">So what can be done?  Are all these subnets a symptom of some other issue, unrelated to NetXMS?  How can I prevent them from appearing, or hide them?</p>
<p dir="auto">TIA!</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000006801-MobaXterm_2024-11-15_10-34-38.png" alt="MobaXterm_2024-11-15_10-34-38.png" class="img-markdown  img-fluid" width="1572" height="857" /></p>
]]></description><link>https://forum.netxms.org/topic/8062/network-discovery-finds-hundreds-of-subnets</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 09:26:11 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/8062.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 14 Nov 2024 23:46:32 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Network Discovery finds hundreds of subnets on Tue, 19 Nov 2024 08:19:12 GMT]]></title><description><![CDATA[<p dir="auto">Subnets are created on node configuration poll. Possible reason could be some node(s), which have interfaces with periodically changing IP address.<br />
Filtering can be done in Hook::CreateSubnet script in script library, but first of all you can add some debug there (before "return true;" line):</p>
<p dir="auto">trace(0, "In Hook::CreateSubnet | Conf poll on " .. $<a href="http://node.name" rel="nofollow ugc">node.name</a> .. " want to create subnet " .. $1.ipAddress);</p>
<p dir="auto">This will add messages to server's log. If you NetXMS version is older then 5.x, line should be a bit different:</p>
<p dir="auto">trace(0, "In Hook::CreateSubnet | Conf poll on " . $<a href="http://node.name" rel="nofollow ugc">node.name</a> . " wants to create subnet " . $1.ipAddr);</p>
]]></description><link>https://forum.netxms.org/post/33975</link><guid isPermaLink="true">https://forum.netxms.org/post/33975</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Tue, 19 Nov 2024 08:19:12 GMT</pubDate></item><item><title><![CDATA[Reply to Network Discovery finds hundreds of subnets on Fri, 15 Nov 2024 20:49:27 GMT]]></title><description><![CDATA[<p dir="auto">Update: Even though I switched to active only discovery, and deleted all the unwanted subnets, more are coming back.</p>
]]></description><link>https://forum.netxms.org/post/33972</link><guid isPermaLink="true">https://forum.netxms.org/post/33972</guid><dc:creator><![CDATA[tfines]]></dc:creator><pubDate>Fri, 15 Nov 2024 20:49:27 GMT</pubDate></item></channel></rss>