Quick Discovery completed after 8.5 hours for a Windows Server

[Suvetha S]

Hi All,

I ran quick discovery for a windows server and it took more than 8 hours to complete. From the ECC queue i could see that the Windows OS - Server pattern is running for 6 hours. I went through the pattern log and nothing seems to be abnormal. What might be the issue? Any help will be appreciated. Thanks

[Harsh Vardhan]

Hi @Suvetha S  : What happen if you open "Windows OS - Server" pattern on debug mode and test that destination IP , are you getting the result quickly ? this way you can also validate if any command taking time to response on ecc_queue. 

Also have you checked any PowerShell command taking time to execute ? validate the mid server log file.

Can you also confirm if your mid server did not down between the discovery execution ? i think you can get it from mid server log file.

Adding one KB article : Troubleshoot Discovery Performance, Cancellation, and Timeout 

Thanks,

Harsh

[Suvetha S]

Hi @Harsh Vardhan  Thank you for the response. I tried debugging Windows OS - Server and its getting session time out each time i clicked on any of the steps. Also in the performance metrics i could Windows OS probe is the one which took longer time to complete. 

[Harsh Vardhan]

@Suvetha S  How about if you add mid.log.level parameter on mid server then running quick discovery , now you can validate mid server log file to check which command taking time to response or which is failing ? 

How to add MID Server to debug mode 

Thanks,

Harsh

[Rahul Priyadars]

I have One Question here . 

Your Mid Server and the Given HOST is in same DC/Geography ? What are their Locations ..I asked just to kill the LATENCY Angle from Mid Server to HOST.

Regards

RP