discovery stuck and ECC queue output in error

[Arnaud9]

Hi everybody,

I'm doing a huge discovery about 6000 CI and it's stuck at 3500 discovered CI and after all the ECC queue in output are in error state instead of processed and the other CI have failed to be discovered. 

Someone has already had this kind of problem ? 

I looked for in lot of KB but I don't find something to help me and maybe me knowledge is limited on certain point 

Other thing when my discovery schedule is small for example less of 1000 CI everything is ok so i thought it's maybe a size problem but where and how can I fix that ? 

[MD AQUIB KHAN]

Hi,

I think you are correct. It may be about the capacity of the mid server. We can try one last thing divide the discovery schedule in two parts. May be split the IP ranges and try. Use two mid servers for the discovery schedule. Also, we can filter based on the Mid Server capabilities (WMI, SNMP & SSH). If you are aware of the Device, you are discovering. This is just to stop the delay. 

Nice to have discussion with you. 

[Arnaud9]

Thank you for your answer Aquib Khan. You're right i've already did that too by dividing the discovery schedule and using custom behavior I did myself and out of the box behavior to use only certain protocols that you quoted above. 

So yes it's working but i would like if it's possible to increase the mid server capacity without to split my schedule. 

Unfortunately I can't make a cluster because I don't have the ressource for that. 

Nice to have this conversation with you too.

Have a nice day.