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

Limiting subnet discovery

morrack2000

I'm running an evaluation copy of IPAM, and right out the gate I'm smacking into a wall. It's great that we can specify a list of routers to run discovery on. However, am I missing something or is there really no ability to limit the discovery to just connected routes on those routers? My full routing tables include summarized routes, loopbacks for our MPLS providers gear, as well as hundreds of routes to our "sister organizations" that we share address space with. I don't want to import all that, or spend hours checking and unchecking things - and still have an incomplete list of subnets due to summarization.

I can probably sort out a way to get all the subnets added, but I'd be looking at several days of manual effort (I have hundreds of sites). It would be SO much easier to provide a list of core routers at each site, then run a discover for connected routes only, and BAM! Not possible?

Find more posts tagged with

Accepted answers

All comments

dgsmith80

I thought when you specify a seed router for discovery it lets you set how many hops you can make as part of the discovery? Couldn’t you use that to restrict it?

morrack2000

Afraid not, that was the first thing I tried. It grabs the entire routing table from that router, not just the connected routes. Given that, i'm actually not sure what the point of specifying the number of hops is for the IPAM module.