I got similar requests from other users too. I'm currently considering adding "exclude from topology" option for nodes - then all topology functionality will be turned off, but node will be checked in status and conf poll using primary name and data collection will work.

Best regards,
Victor

IP address uniqueness is one of the basic concepts in NetXMS... I am pretty sure internally the code also relies on single IP = single device a lot.
Victor will however have to comment more on this.

Simply put a Raspberry Pi, or similar $30 Linux machine into the network, and use it as a proxy.

I believe so and I agree with you.
But since it is a small network with one router and one local switch, i should not buy another device ($5 or whatever) for this simple local network and basic SNMP monitoring.
This is simple NetXMS software limitation then, and my request/proposal is to change the behavior and single IP = single device. I also understand that this is core of the system possibly.

Simply put a Raspberry Pi, or similar $30 Linux machine into the network, and use it as a proxy.

Enabling simple that IP address must not be unique would resolve the issue.

1. if this is multiple customers/sites separate them into zones.
   You can research how zones work and what they are used for in the documentation.

2. If you dont want to use Zoning, simply place a proxy in the network, and proxy SNMP over that proxy to all local devices.

I like the option to use custom SNMP port, but just like CactiEz I need to just add many nodes with the same IP addresses and networks, separate them in isolated regions and monitor them. In the current implementation I can use this great system only to monitor one site and this is just not enough.