Organizing Discovery Schedule

[MonzaniWill]

What is the best way to organize discovery schedules for a global organization? Any tips on creating an IP range set or application that helps manage existing IPs and Subnets?

[Adrian Ubeda]

Hello,

While there's no specific manual for this task, I would recommend separating IP addresses into smaller ranges, always keeping them under /20. This will expedite the discovery process, especially when scheduling the job during periods of low task performance for the midServer or environment. It's important to ensure that credentials and access are properly configured. Additionally, if there are too many Configuration Items (CIs) within the same IP range, consider splitting it into a lower number of CIs to facilitate the process.

I let you also a link to best practices to configure midServer: https://www.servicenow.com/community/itom-articles/mid-server-best-practices/ta-p/2326878

[MonzaniWill]

Hi Adrian,

I understand, but this starts to become complex when we have datacentres spread across the world and we have to determine mid servers for each IP range. And so when you receive a server name and IP that needs to be updated you have to scan several tables to find information and determine the correct server that will see that IP and have the necessary credentials to run Discovery.

Furthermore, when new subnets are added simultaneously in several parts of the world this can become confusing as well. 😅

[Pratiksha · Accepted solution]

Their are few ways to do it.

• You can run the network discovery to get the IP ranges.
• You can integrate with the IPAM tools. (we have done it with a client and it works fine)
• avoid using class B ranges. It will put load on the mid servers.