Discovery schedule is not discovering all the Servers

[Ankith K U]

When we run discovery schedule for IPs/IP subnet we are getting below error

Terminated the probe because the max timeout was exceeded: 600 seconds.

Only 20% of servers from the schedule will get updated rest all will be terminated with the error

But if we pick those IPs which we get these errors and run a quick discovery, the Server associated with that IP will get updated.
We have tried to increase the probe time to 1200 seconds that also didn't help.

Also we see HIGH CPU usage (100%) while running the schedule

[pratiksha5]

I am having an open ticket with ServiceNow for this. If I give the IP ranges let's say for 100 IP it is not working. Same IP if I give in the IP address list it works. Previously they asked to add more memory to the mid server. we did that and it did not work. Now they are saying it is because of network latency and asked me to provide the traffic details. I have denied the solution as it works with the IP list at the same time but the range is not working. I will keep you posted on the solution they provide. 

You can also look in to the MID Server threads parameters 

[Daniel Borkowi1]

Hi @pratiksha5, would be great if you can share the root cause afterwards. Sometimes you need to be more patient with the support, it takes some time until you get an expert. I don't think it has something to do with the MID parameters. Even with default settings there should be no issues with 100 IPs.  Challenge the support again and again until you get a discovery expert who can investigate deeper.

[pratiksha5]

It's been more than a month now. But I am optimistic. I will surely keep you posted. 

[pratiksha5]

We could finally fix it. 

- source: mid-server IP
- destination: destination ip range
- ports: allow all
- IPS: turned off all intrusion prevention checks
- App Control turned off
- limits: allow to exceed global session limits (this was causing most of the issue)

[AEV]

I would like to know what the solution was to this if you found it. Since last week I'm starting to get this exact error.

scan 10 servers, errors... scan one, it works but takes 15 minutes to finish. On Tokyo with latest patches.