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 don't need to add to the list.

Try this way : - 

When you define the "Network" type discovery schedule, just add the starting router in "Discovery Range Sets" related list, and for testing purpose, add another range in same related list 172.27.0.0/16.

Screenshot attached.

Documentation is very confusing, when I implemented I had the same challenge.  

Hope it will help you.

Thanks,

Harsh

[arielgritti]

Hi @Harsh Vardhan 

Can this configuration help me in my challenge to discover private networks (same addresses) in several physical locations?

Thanks,

Ariel

[cragland]

Hi, Kilo. DId you fine you answer?