discovery status active for a long time

[Ravish Shetty]

I have scheduled some discovery scan in the dev environment in the interval of 1 hour for a window of 4 hours. all of them use 1 mid server. the scans are taking longer than expected compared to when we run them on their own without others being scheduled in the sequence. 

some scans are still in progress after running for a couple of hours. could this be because we are using just 1 MID server? below are the stats from ecc_agent_scalar_metric table.

mid server consumption seems to be the obvious reason but i want to understand if there is something more to it.

[tim_broberg]

Go to one of your long running discovery statuses.

Look at the ecc_queue related list, and filter for status != processed.

Those are the probes that are dragging on.

Once you know what they are, you can start debugging what the issue is there.
    - Tim.

[Ian Mildon]

A lot of things can (and will) affect the time taken to complete a Discovery job. Not least of which is the IP Range you are scanning. Then there is the issue of devices on the IP range being scanned. Some devices such as network gear (with lots of ports and routing tables) will take a long time to process; as too will any kind of NAS device.

As already mentioned, take a look at the Discovery Status for the running job, paying attention to the Discovery Log and ECC Queue tabs. These should give you a better idea as to what is causing the slowdown.