Why Discovery Schedules are hanging when multiple CI IPs addresses are associated with a single device?

[Vicente]

Hello Community.

While running discovery schedules some IPs addresses are hanging and discovery never finishes.
I noticed that the IPs addresses that are hanging in the scanning phase are associated with particular devices.
These devices have multiple IPs addresses configured in its LAN nic.

For example; we have a server with 5 IPs addresses configured in its LAN nic.
Discovery updates the CI record using just one of the IP addresses and it hangs trying to scan the 4 remaining IPs addresses till the configured max run timer in the discovery schedule runs out of time.

I did a test scanning one by one the 5 IPs and the CI record was being successfully updated each time I scanned the IP.
The issue happens when Discovery is scanning all of the IPs together. I could exclude 4 of the IPs addresses so those wouldn't be scanned; however, I don't know what those IPs are used for.

Your comments/suggestions are welcome.

Thanks.

[tim_broberg]

So, if you go to the discovery status, look at the ecc_queue related list, and filter for the relevant IPs, what probes do you see?

Are there inputs for all the outputs?

Are there errors in the input records?

[Vicente]

Yes, there are input and outputs. (See attachment) I'm just able to see the WMI probe. And in the payloads XML, there are no errors at all.

[tim_broberg]

Sorry, I see no ecc_queue in the attachments. Without being able to see the ecc_queue, I have no idea what probes have been run, whether the response came back, whether the mid picked it up, etc. I'm looking for the created, updated, processed, state, topic, name, and queue fields of the ecc_queue.

WMI, so it's Windows. Ok.

[Vicente]

Here is the full ecc_Queue for the IP address that Discovery is taking to properly update this CI record.