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]

 Update on the ticket from ServiceNow. They asked to trace the traffic from the mid-server to the target network. We found that many of the servers or devices not responding to mid-server. I logged the case to the network team for the latency. They are looking into this. 

[AEV]

Are you using Trellix(mcafee) Antivirus? I think it might have something to do with the current patch on the Trellix agent v5.7.9.139.

I disabled AV it scans ok.. My bulk scans were slowly, very slowly working before that patch which I think I just tracked down now after days of looking.

This is a 5 month back and forth I've been having with support on my ticket with very, very slow scans that we still can't resolve.