For example . Two remote sites have same IP 10.0.0.0/24 networks. Is NPM capable of separating the two sites even though they are in same IP subnet?
Yes type for seach range.
Now you can to monitor the sites external link.
I'll be interested in seeing how someone recommends accomplishing this.
If there were something unique about each network, such that you could write static routes to send your NPM polling to unique 32-bit addresses, or sub-ranges of the original 24-bit range, I could imaging how to do it.
But suppose the two different 10.0.0.0/24 subnets have a device at 10.0.0.10/24 that you want to monitor with NPM. You'd need to be able to ping each one separately, and your routing won't know how to do it. Without a separate routing solution for each one, I don't see how it could be accomplished with a single instance of NPM.
Can you ping each one separately from the same NPM instance? I don't see how, and without that, NPM won't be able to poll / monitor / discover two devices on different subnets with the same address.
`With the same ip it will not do.
I had not paid attention to it.
You can use NAT on each end of the link so that the NPM appears with a local IP on each remote site and have each remote site appear with a local IP on the NPM network.
True. But ugly. Still, an accurate answer if you can get it to route the way it's needed. Good thinking.
Could try dropping a poller into each subnet - but I don't know how npm would handle it. Route NPM discovery into one subnet, then after the discovery re-route to the other subnet. Seems like a simpler solution would be just to re-subnet one of the 10.0.0.0/24s into 10.1.0.0/24.
Thanks everyone. Yes, NAT is the obvious solution but won't be wont scale well if you start talking a large amount of IP's to NAT. I was hoping someone had some trick with IP+SNMP STRING or IP+Customer property, or something else. But yes, it does come down to polling the IP which you can't have duplicates.
Yea, NAT would do it - but it just seems so superfluous to me. It's only 254 max hosts, seems like it would be easier to re-ip, but either way it'll work.
Spend money on EOC license?
Enterprise Operations Console | EOC | SolarWinds
...
Allows enterprises and Managed Service Providers (MSPs) to monitor overlapping IP addresses
You can monitor up/down status with icmp through a NAT but that's about it and maintaining it is a nightmare. Also the worst thing is snmp will NOT work through NAT! snmp uses IP's that are part of the OID's. Unless you have some magic snmp proxy (it's been tried before but never really worked) Having so much information deep in the packet with IP information trying to proxy this is just next to impossible.
A seperate poller and EOC is really the way things are going... especially now that EOC is being completely rewritten now!
One other option depending on what you are monitoring would be to have the new SAM agent do polling inside individual DMZ perhaps???
I did the EOC thing for a few years because I had four regional NPM instances as the result of mergers & acquisitions. It's really not the way to go for that small a solution--it takes a long time to update status from the pollers. I talked with SW about it, they said they built it for much larger implementations.
I dropped EOC and changed my stand alone NPM's to simple pollers reporting to one NPM instance, and saved the EOC license/support costs and the hardware space. And ended up with a better corporate environment because now all regions show up as if they were in my home region. That lets my team treat all outages equally, rather than focusing on what's local and what's remote. It was a big improvement for our needs.
You can see more about the SAM solution here:
Server & Application Monitor - What we're working on beyond SAM 6.2
