<![CDATA[Overlapping non routed subnets]]>We use a standard configuration on each of our routers across our network. this configuration has the same natted subnets behind them. NetXMS seems to interpret this as these devices being connected on this subnet. Is there a way to ignore this Nat'd subnet.

similarly, i have some Nat'd subnets that are of the same network but with different sizes.

Sorry if this is a repeat question, i have attempted to search for a response but cannot find one that seems to apply.

Thanks

]]>https://forum.netxms.org/topic/6273/overlapping-non-routed-subnetsRSS for NodeFri, 13 Nov 2026 09:35:21 GMTThu, 14 Nov 2019 21:45:36 GMT60<![CDATA[Reply to Overlapping non routed subnets on Tue, 03 Dec 2019 13:59:15 GMT]]>Latest NXSL manual:
www.netxms.org/documentation/nxsl-3.0/
NXSL manual for version 2.2:
www.netxms.org/documentation/nxsl-2.2/

]]>https://forum.netxms.org/post/27017https://forum.netxms.org/post/27017Tue, 03 Dec 2019 13:59:15 GMT<![CDATA[Reply to Overlapping non routed subnets on Wed, 27 Nov 2019 16:00:43 GMT]]>I have been working on this, and i am very new to Nxsl. it seems that the object definitions on the wiki seem incomplete or perhaps dont have the ability to refernce the Interface Childs like the console scripting does.

i was wondering if there are some better examples or documentation somewhere.

thanks

]]>https://forum.netxms.org/post/27006https://forum.netxms.org/post/27006Wed, 27 Nov 2019 16:00:43 GMT<![CDATA[Reply to Overlapping non routed subnets on Mon, 18 Nov 2019 22:28:10 GMT]]>i think that is more what i want.

Thank you for the suggestion, I have tried this on a few and this seems to work.

]]>https://forum.netxms.org/post/26960https://forum.netxms.org/post/26960Mon, 18 Nov 2019 22:28:10 GMT<![CDATA[Reply to Overlapping non routed subnets on Mon, 18 Nov 2019 21:46:15 GMT]]>You can "Exclude this interface from network topology" (per interface setting, properties of interface -> Polling), which I believe will ignore the attached subnet.
The networks that were already discovered will still be around, so you'll have to clean those up.

I haven't really used this setting and haven't checked if it can be set via NXSL (which you'd probably want to do, so any new devices will have those particular interfaces ignored by default).

]]>https://forum.netxms.org/post/26959https://forum.netxms.org/post/26959Mon, 18 Nov 2019 21:46:15 GMT<![CDATA[Reply to Overlapping non routed subnets on Mon, 18 Nov 2019 16:08:15 GMT]]>I was reading a bit about zones. i dont think it quite solves the problem i am having. I control the lan and Wan side of these routers. i want to manage the wan side of these routers as one ip space and the lan side because it is not being routed should be treated as a different space. If i understand zones, you put an entire node in a zone. this doesnt seem to match my use case.

I would also be content with the idea of ignoring the Lan ip space.

]]>https://forum.netxms.org/post/26956https://forum.netxms.org/post/26956Mon, 18 Nov 2019 16:08:15 GMT<![CDATA[Reply to Overlapping non routed subnets on Fri, 15 Nov 2019 16:03:09 GMT]]>You should set them up as Zones if you dont want them to be considered on the same subnet.
You will need to setup a proxy that is either directly addressable by the NetXMS server or with an agent tunnel to the NetXMS server.

]]>https://forum.netxms.org/post/26947https://forum.netxms.org/post/26947Fri, 15 Nov 2019 16:03:09 GMT