Most Recent Discovery Not Getting updated even though the device shows it is being discovered recenlty

[Nilanjan1]

Hello. 

This is a very strange issue I am getting. While I am running a weekly scans and can see all the IP subnets getting scanned, however when I check the table (Network Gear & Server) the most recent discovery date is not getting updated even though in the discovery status the CI has been discovered very recently. Can someone check asap and let me know. it is very uirgent

Regards

Nilanjan

[bernyalvarado]

Hi @Nilanjan , try doing a Quick discovery of a specific network or server CI with its IP and check if it's most recent discovery gets updated. From what I recall, out of the box, discovery doesn't update that field for all CI types.  

Thanks,

Berny

[sachin_namjoshi]

Its likely the appropriate probe-sensor, or pattern (depending on your situation) that is collecting the network gear and server info isn't setting the Most Recent Discovery date. 

 I've noticed some of the 'deeper' class types don't get these value set.  So you'd have to tweak the probe/sensor/pattern to ensure the fields are updated.

Regards,

Sachin

[SiD2]

Hi @Nilanjan

This is real strange, hope you are checking the "Updated" field only and no errors in the discovery log.

[bernyalvarado]

The reality is that it's not strange. In fact, it's quite common. It all depends on the CI type. 

Even within the community is pretty common. Here goes a short list of others that faced the same issue: 

https://community.servicenow.com/community?id=community_question&sys_id=a185ee9adb14105014d6fb243996...

https://community.servicenow.com/community?id=community_question&sys_id=1066bf531b99b300ada243f6fe4b...

https://community.servicenow.com/community?id=community_question&sys_id=ddcc4074db332b80a39a0b55ca96...

Thanks,

Berny