Network Discovery - Not Scanning Private IPs

[Community Alums]

Afternoon all,

So I'm re-running a network discovery, and I've set it up as per the doc: Network Discovery

However, I've noticed when scanning, it's not hitting anything in the 172.16 range, and we have network routers in that area. The docs doesn't mention having to add the "Private IP" range to the discovery range sets. It also seems to state it should just be available: "The default IP networks in this list are available to every Network Discovery you conduct and are sufficient for most discoveries"

I did try adding it just to see what it would do, but then the scan can't complete because it has too many IPs in the ranges.

Is there a sys property or something I'm missing to enable that scanning?

Any help is appreciated, Thank you.

[Harsh Vardhan]

Hi @Community Alums  - You need to include the IP ranges in "Private IP Addresses" [ discovery_range ] , OOTB 172.16.0.0/12 already exist. 

Now in your discovery schedule just use the starting router and core router IP. It will start gathering the IP subnets in IP Network table. 

Let me know if you have any further questions on this. 

Thanks,

Harsh

[Harsh Vardhan]

Just to add, mark "glide.discovery.bgp_router_disable" properties as false . then try it again. 

I am assuming your discovery is pattern based not probe based. 

[Community Alums]

I checked the property and we are already set as False, our discovery implementation is pattern based. 

[Community Alums]

Hi Harshvardhan,

For the moment I am just trying to use the default private IP ranges, as they should fit our use case. I've also added the starting routers.  I see it scanning networks across the starting routers, but nothing in the private ranges. The docs don't state to add the private ip range set to the list, if I do I can't then discover as it now says it has too many IPs to scan.