CI mismatch

[Mukesh5]

Hi, 
I need some help in this below scenario.

We have been recently reviewing records in the CMDB and have identified that the VR.System is creating thousands of CI's in Unmatched Ci's and Unclassed hardware classes.

As per my understanding Generally system will search using QID in the Discovered Item table, if no record is found, it will invoke the CI Look up rule and then if it also doesn't find the CI in the CMDB based on the ci look up rule, Then it will create a record in the CMDB table as unclassified hardware and also create a record in the discovered item table with the state as unmatched.

Question 1) Why this Ci's are storing in different classes rather than original class and is there any way to resolve this ?
Question 2) Can we reduce unclassed hardware and unmatched ci classes records?

[Mukesh5]

HI @AJ-TechTrek ,

Could you please guide me what pattern means and how to find that.

[AJ-TechTrek]

Hi @Mukesh5 ,

to find the pattern using which these record are created, Please re-run the discovery and refer the discovery logs to identify the Pattern using which this CI is created, Also it will be good if you can delete this CI from CMDB if its not a prod instance for testing purpose.

After that Once you got to know the Pattern , Open the pattern and start debugging using the IP Address.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024