Quick Discovery Vs Scheduled Discovery

Nilanjan1
Mega Sage

Hello All, 

Hope everyone is safe and keeping well....

I have seen a strange issue. The IP's that were failing in the scheduled discovery is working in the Quick Discovery, Why is that, however every IP within the scheduled discovery subnet is being scanned...I need a quick response...can someone please help urgently! I came across this article but I am not sure whether there is any restrictions to it.

https://community.servicenow.com/community?id=community_question&sys_id=c2494725db5cdbc01dcaf3231f961989 

 

 

1 ACCEPTED SOLUTION

Ashutosh Munot1
Kilo Patron
Kilo Patron

Hi,

This is strange. There is no restrictions went it comes to discover the IP either ways.


So what i propose is just to compare what happens.

1) Create a Test schedule.

2) Add Quick Ranges to this schedule which has the IP which was discovered using quick discovery and not using discovery scheduled.

3) Make sure you have SNMP Support as all if this is SNMP device.

 

Let me know the results


Thanks,
Ashutosh

View solution in original post

4 REPLIES 4

Ashutosh Munot1
Kilo Patron
Kilo Patron

Hi,

This is strange. There is no restrictions went it comes to discover the IP either ways.


So what i propose is just to compare what happens.

1) Create a Test schedule.

2) Add Quick Ranges to this schedule which has the IP which was discovered using quick discovery and not using discovery scheduled.

3) Make sure you have SNMP Support as all if this is SNMP device.

 

Let me know the results


Thanks,
Ashutosh

Hello Ashutosh, 

Thank you for your time and patience...I was able to resolve it, The issue was with the duplicate entry in the schedule which was preventing the completion of the discovery. Also I created a test schedule & it worked completely without failure. 

Regards

Nilanjan

Nice.

mark the answer correct and close thread. you know that you can mark your answer as correct as well.

Thanks,
Ashutosh

Fausto Lozano
Tera Contributor

Hello, i have realized that this behavior is happening to me as well. Subnet scan in the schedules does not scan ip's that are actually accessible, i have seen this behavior as well if i scan a list of ip's.

Apparently discovery have some problems when is doing scan in batches...

i don't know if any one have ran into the same problem, what i have done to reduce this problem is to make smaller the batch size, but i don't know if this actually helps, i do see some improvement but i still get failed access for ip's i know i discover trough quick scan...

Regards!