Why CIs are classified as unclassed hardware?

[MSB]

Hello Everyone,

We are having many devices being classified as unclassed hardware, so looking for the reason for it being unclassed hardware and what would help it to classify them to be their respective class devices. Any information on it would be greatly appreciated.

Thanks,

MSB

[Logan Poynter]

Hello,

What kind of devices are they? Basically, this issue will happen when a CI does not provide a name in the response or is not one that ServiceNow understands to properly classify the CI.

Look at the source IP and check for failed credentials or if you need to build out an additional SNMP classifier. 

Please mark my answer as correct/helpful if it has helped you.

Thanks,
Logan
--
LinkedIn

[Rahul Priyadars]

here is the - what service now docs says

https://docs.servicenow.com/bundle/sandiego-security-management/page/product/vulnerability-config-compliance/concept/cc-cj-discovered-items.html

Regards

RP

[SELECT Username]

Could you please provide some more information as to where the CIs are coming from?  Are they from Discovery?  A Service Graph Connector?  A Custom Integration?  Manually created?  When you say that they're "unclassified hardware", do you mean that they're in the "Hardware" class (cmdb_ci_hardware), or do you have a class called "unclassified hardware"?  If it's the latter, what's the technical name of the class (I'm wondering if it starts with "u_").