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?

[Dr Atul G- LNG]

@AJ-TechTrek need inputs here.

[Mukesh5]

Hi Ajay,

what kind of inputs are needed.

[Mukesh5]

Hi Ajay,

What kind of inputs are needed

[AJ-TechTrek]

Hi @Mukesh5 ,

This is the expected behaviour of discovery, When we run the discovery for any CI, Like hardware or Virtual , Associated record with that CI, also created in different classes which not belongs to Hardware class.

Above Screenshot is representing with Virtual Instance discovery, Discovery found the DNS name, Linux Server and Unclassed Hardware.

Unclassed Hardware means , ServiceNow dont have the correct class to popuplate those device for that you need find the pattern which is used to run the discovery and that pattern you need to debug and that particular step you needs to deactivate which is created CI in Unclassed hardware class.

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