Most recent Discovery - Empty

[sreejith93]

Hello All,

Its being observed that some of the CIs are having most recent discovery as "Empty". We did a complete scan & quick scan, both the ways the CI is getting updated but still the Most Recent Discovery field shows up as "Empty" for some devices.

What can be the root cause of this & what's the solution for this if someone has faced the same?

We are using Istanbul release.

Thanks,

SJ

[Dave Ainsworth]

Hi Sreejith,

Do have any reconcilation definitions defined?

Go to Configuration->Reconciliation Definitions and check. By default, there will be definitions for ServiceWatch and ServiceNow (depending on the version you are on). If there are any others that have been defined or the definitions have been updated, ensure there are no definitions which could be blocking discovery from updating this field. If there are definitions created for other datasources and you are in a dev environment, try disabling them and rediscovering

The only other thing I can think of is some kind of data policy or Business Rule which for some reason is stopping the updates.

Regards,

Dave

[sreejith93]

Hi David,

Thanks for your suggestion. But the issue is just with 4 switches that we are facing in our Test & PROD envs.

So I dont think policy or business rule would be the culprit over here.

SJ

[Dave Ainsworth]

Hi Sreejith,

I would still check the reconciliation rules if you haven't already. If rules have been created, this sort of behaviour can happen if some devices have been updated by other sources before discovery updates them. Devices that are created by discovery first and then only updated by discovery will probably update the most recent discovery without an issue.

Regards,

Dave

[Phil32]

How do you get class "DNS Name" to populate Most Recent Discovery?

[vinothkumar]

Most recent discovery is getting empty and the same time CI is getting updated means, it might be through other means like SCCM Import, etc. If it is running through discovery, this field will be updated.

Check whether you have any SCCM import scheduled import is active