NetXMS Support Forum

I have been reading through forum after forum and I can't find someone trying to do anything near the level that I am trying to do.

I need to be able to manage up to 50-100 different devices with random private IPs potentially coming from different public IPs from the same site. I need to be able to also manage up to 1000 sites. Worst case scenario, this could end up being 50,000 nodes all potentially behind firewalls that cannot be configured.

I was looking at maybe doing SNMP and using proxies, but even still, I would, at the very least need one static internal IP with 4700 or 161 forwarded to that IP (this is also assuming that the public IP is static as well, which it might not be).

On the plus side, all of these nodes should be Windows OS. So, I was wondering. If I set up each device to run a script to poll the server (preferably with a header or some other information) can the server then report on the status of the incoming poll? Additionally, could the server be set to say, look for an incoming connection every 5 minutes and if it doesn't receive that connection from that node then it reports the node as down?

This is the only way I can really see this situation working. Any suggestions or help would be greatly appreciated.

Hi,

starting with 2.1-M3 there is agent-to-server connection option, so you can have site proxies behind firewall connecting to NetXMS server. Server itself should handle 50k nodes without issues, although you will need quite big amount of RAM (I would recommend 8 GB at least). Database will definitely require some tuning (but actual load and size requirements highly dependent on how much data you will collect and how often). Network connections should be fine because you will have connections open to proxies, and everything else will be between proxies and end nodes.

Best regards,
Victor

I appreciate the response. Fortunately, we have the server hosted on a commercial grade server, I think with 16GB RAM. A Dell PowerEdge. The database, I think is hosted on a separate, equally powerful server. Currently, we are sitting at probably about 1000 nodes that we are monitoring. 50,000 is likely a huge stretch, but I wanted to give worst case scenario. That being said, are there any known issues in this latest beta? 2.1-M3? We are reluctant to put our current monitoring at risk by trying a beta. We are currently using the latest stable 2.0.8.
Thanks for your time!

Hi,

there are few issues already found in 2.1-M3, especially with new back-connect functionality. We plan to release RC version in a week or two, which will be followed by stable 2.1 release.

Best regards,
Victor