Most recent Discovery - Empty

sreejith93
Kilo Contributor

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

13 REPLIES 13

Dave Ainsworth
ServiceNow Employee
ServiceNow Employee

Hi Sreejith,



With which CI class or classes are you seeing this? Not all CI classes have this populated.



As an example, when a server is discovered, the server has Most Recent Discovery set but the related CIs such as network adapter do not have this populated.



Regards,



Dave


Hi David,




We are seeing this case for Network Switches. The discovery happens fine , the classification also happens. But still the most recent discovery turns up as "EMPTY" despite getting it discovered.



Wondering what can be the cause.



Please help me out if you have any idea how this can be tackled.



Thanks,


SJ


Hi Sreejith,



Just to check. You say that the classification happens but is the identification also successful?



Regards,



Dave


Hi David,



Yes the identification & classification both the phase are successful because I can see that the device is getting updated as well.



find_real_file.png



But when I look into the CMDB report it says it was last updated on January & the most recent discovery field as "Empty".




Thanks,


SJ