CMDB CI field is just "empty" after running discovery schedule. Has anyone know how to fix this issue?

[Vicente]

In our organization, we have just turned on Discovery against printers. I have been able to find most of the printers running discoveries schedules except a few of them. For some reason, the CMDB CI field is getting: (empty) and the Current activity field, its status, is getting stuck in: Updating CI for a specific IP address, in this case, a printer device.

I had tried adding SNMP Object ID, just to test, without success.

Attach is the Discovery Log information for the printer device.

Has anyone knows how to fix this little issue?

I will appreciate your help.

[Ian Mildon]

It looks like it is your Identifier that is having issues. For whatever reason the printer you scanned does not match the criteria; or there is something that is hanging.

To compare, I did a quick scan against a printer and the log entries for Source were (in order):

Discovery, Identifier, Identifier, SNMP Identity, SNMP-Printing, SNMP, SNMP, Discovery

And the CI was named at the SNMP Identity multiprobe

[Andrew Westerv4 · Accepted solution]

Your Discovery Logs indicate that it matched on serial number, so your there isn't a problem with the Identification rules. Either you have a CI in the printer table that doesn't have a name (hence empty) or you have something deleting your CI during the Discovery run.

[Vicente]

Thanks, Andrew. CI's were being created but I wasn't aware that some of our printers don't have a name.

[ShivamSingh]

Hi Andrew,

Can you please tell me what could be the reasons that names in CMDB table are empty even after discovery?

P.S - this is an independent question.