NPM 9.5 Discovery time limit

Question

The max time that can be specified is 300 mins. I am assuming this is the time allowed to scan and discover all the nodes specified via subnet, range or seed-file. This isn't enough time for me to scan everything on my network. What's the best approach? Break-up the scan? change time-out values for snmp and ping?

I occasionally want to run a full-scan and in the earlier releases could just fire it up on a friday night and everything would be done when I came back in on monday. Maybe the timer could be bumped up to say 600 mins?

Thanks All

FormerMember · Answer

The approach we've suggested to the couple other folks who have run into this problem is to split up the range of IP's being scanned across multiple discoveries.  Would this be possible?  We've recently talked about increasing the timeout, but I was curious if folks were willing to split things up or not.

What's a reason for needing a single discovery to run over 5 hours?  What's a realistic maximum for running a discovery?  If discoveries could be scheduled to run every day, would you still want to do the big one?