max number of IPs a discovery schedule can contain?

[Abdul Parveez]

I had a schedule that was running fine until last weekend (SanDiego) but is getting Cancelled after we upgraded to Utah. now the same schedule that was running without issues everyday is throwing an error "schedule can only contain 1048576 Ips but schedule has more"

So what is the maximum limit of IPs by default in SanDiego and what is in Utah.. where do we check this default value? can we change it? or split the schedule?

[SiD2 · Accepted solution]

Hi @Abdul Parveez 

Yes, it's changed starting in Tokyo via PRB1570850, as we observed multiple OOM issues due to an extensive range.

It's always advised to logically break your IP ranges according to your business operations and target multiple schedules. The maximum IPs allowed starting in Tokyo will be the value in the screenshot.

[Abdul Parveez]

Thanks Sid, got tio know they added below part to discovery schedule script include.

==var ipTotalCount = countIPs(this);
if (ipTotalCount 1048576) // This is the size of a /12 network
return 'Schedule can only contain 1,048,576 IPs but has ' + ipTotalCount;

[Abdul Parveez]

Thanks Sid, they added below part to script include

==var ipTotalCount = countIPs(this);
if (ipTotalCount 1048576) // This is the size of a /12 network
return 'Schedule can only contain 1,048,576 IPs but has ' + ipTotalCount;

[Rahul Priyadars]

This is what Service Now Says

Regards

RP