ServiceNow Discovery individual IP addresses v Subnet Range?

[Keith Revis]

Hi,

I am new to ServiceNow and looking at the Discovery jobs that were implemented by someone else a few years ago. We are about to go to Vancouver release. I am surprised to see the jobs contain quite specific IP adresses and a very small IP range. We have over 500 retail outlets and the Discovery  job for each one is quite specific by device rather than containing some subnet ranges 0-255 which I would have expected. The risk is if we add devices they wont be picked up by Discovery without action.

Is specifying subnets 0-255, even though there may be only a few IP addresses used, not recommended? 

[AJ-TechTrek]

Hi @Keith Revis ,

The best practice is used the IP Subnet for discovery schedules as IP subnet will help add those Ip as well which was used in future or assign to some device after they used,

Individual IP's which we used only for that case, if we are sure more IP will not be added in that particular Ip Range, you must use the comma separated IP or IP subnet range always in Discovery Schedule.

https://www.servicenow.com/community/itom-blog/best-practices-for-setting-up-discovery-schedules/ba-...

you should use the subnet like 1.1.1.0/24 , for 256 IP , 1.1.1.0/23 - is for 512 IP, where 2 IP always reserved.

Refer below for IP Subnets.

https://www.calculator.net/ip-subnet-calculator.html

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[Keith Revis]

Thanks AJ, I will read those.