Plan and Monitoring with SolarWinds NPM in 2025

charly_DF

Hello,

I have some questions regarding a new project for SolarWinds monitoring.

• We need to monitor approximately 32,000 IP addresses (some only by ping, others via SNMP with full statistics).
• The IP addresses will be in independent networks (multiple clients, possibly with overlapping IP spaces), so we need separate tenants.
• We require a local poller at each site (around 400 remote locations).
• A NOC must be able to see all alarms from all different clients (tenants).
• We need a self-hosted solution.
• Access to every site via hub-spoke VPN.

I need assistance in designing a solution that meets these requirements, including hardware, software, licensing, and products.

Any suggestions would be greatly appreciated.

Thanks!

bourlis

Someone please correct me if I'm wrong...

Hi Charly_DF,

It sounds like a prime candidate for SolarWinds EOC.  Based solely on the info you supplied and my understanding of SolarWinds Observability Self Host this is what i would do:

• We need to monitor approximately 32,000 IP addresses (some only by ping, others via SNMP with full statistics). 
  • Nothing but a licensing thing, each instance of SolarWinds would have its own mode licensing model. Just know what with the correct licensing model, there's an unlimited number of ICMP managed nodes.  So all you would have to worry about are agent based, SNMP and WMI/RDP managed nodes.
• The IP addresses will be in independent networks (multiple clients, possibly with overlapping IP spaces), so we need separate tenants.
  • Separate SolarWinds instances that would segregate the multiple clients and overlapping IP space.
• We require a local poller at each site (around 400 remote locations).
  • Additional Pollers or remote pollers within the instances to achieve the local poller requirement.
• A NOC must be able to see all alarms from all different clients (tenants).
  • Implement SolarWinds EOC that will collect data from each instance of SolarWinds and display it in a NOC view.
• We need a self-hosted solution.
  • This solution would be on-prem and leverage the heck out of user rights.
• Access to every site via hub-spoke VPN.
  • This is outside of SolarWinds proper, but its achievable. 

This is basically the direction we're going right now, minus the VPN part.  We have a department that's needs to segregate itself from ours due to a number of security reasons.  However, some level of visibility is still needed between teams.  Our solution is SW EOC, which I'm designing right now.  We're giving them X number of our license count and there going to have their own SW support contact.  They'll also have their own SW environment that they'll manage but if they need my assistance then I can jump in and help. 

All in all, what we're doing is pretty much what you're looking at, but in a much smaller compacity.