Closed

Closed due to inactivity. Received 55 votes with last vote on 01 Oct 2019.

Device Discovery Schedule Improvement

We need a more flexible Discovery scheduler. Our network is too large to discover Daily, and Custom only allows discovery on an interval. In order to periodically discover our network without schedule conflicts, we need Weekly and possibly Monthly intervals, not just Daily. Due to the size and nature of our network, it would be useful to scan certain subnets on day 1 at 3am, other subnets on day 2 at 2am, etc. in addition to just Once, Daily or on a periodic interval.

  • I am also breaking down to multiple sub-nets for discovery, but I would love to have frequency templates or schedule templates to plug in to different network discovery. So I will have daily schedule temple K for sub-net N, O and W. Or I will have monthly schedule template J for sub-net A, C and K. I can create multiple daily, monthly time rotation templates and just pick one to apply to a sub-net location to run discover.


    Able to duplicate from a discovery will help to speed up when creating new ones. I will just have to change IP range or sub-net setting.

    For discovery settings, there could have resource selections such as interface/vlan/CPU/memory/topology/routing....for us to either monitor them or ignore them. Because when I add new device nodes, I do not add interfaces. Or interface description key word can be added so for some one who want to have interface included when a new device is discovered.

    Discovered result can be cleared so I will have fresh new ones every week.

    Ignored results can be eliminated since I already ignored them in the discovery settings?? Or excluded this IP range from the settings??

  • This should have been a must when they created scheduled discoveries, think of as windows task scheduler,

    even in a network that spans 2 countries with 2 different timezones, and over 20 locations, doing everything in one night is just crazy.


  • A network comprised of 150 global locations drives a requirement to schedule discovery per sub-net to a per-determined maintenance window. Ability to scan once upon the scheduled time is another requirement. We can't have sub-net scans traversing sensitive LAN/WAN links outside of specific times of day or days of the week.

  • Agreed my network is too large to discovery everything in one night.  It has to be spread out over multiple intervals.