Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Overlapping IP Space

k_fern2002

I need to manage two customer networks with overlapping IP space on the same orion box. Any recommendations of products/solutions available that will handle this.

Thanks,

KF

Find more posts tagged with

Accepted answers

All comments

iunderwo

You're going to need to a lot of funky NAT stuff to get that to work. Overlapping space is the least fun to deal with.

// Ian Underwood - Service Management
// Level 3 Communications

Network_Guru

In addition to NAT, you could assign secondary loopback addresses to manage the devices in each network. Of course they will need to be routable in the customer's network for you to use them for management, which may present another challenge.

-=Cheers=-
NG

clisser

We do exactly what you are describing using NATed IPs. In our case we tranlate the first octet of the customer IP using the PIX firewall at our NOC.

DonYonce

The NPM polling engines are designed to handle exactly this kind of issue. SolarWinds has many installations that monitor end-user networks with overlapping 10.x.x.x networks. The largest installation has over 60 overlapping private networks.

Here's one way of doing it without NAT-ing the end-user networks and assuming two networks with overlapping 10.x.x.x address space.

Use two NPM polling engines on two machines. (The SQL database could be on either machine, or on a third machine).
Configure the routes on each machine to point to each of the two 10.x.x.x networks... the first polling engine routes to the first end-user network, the second machine routes to the second end-user network. Monitor the first end-user network with the first polling engine and the second network with the second polling engine. All Nodes from both networks will show up just fine on the Web and in the SQL database. Reports, Charts , Views, etc work fine.

You can still use each of the two polling engines to monitor other networks also.
This particular model can be used for any number of overlapping networks without having to NAT each.