
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2019 11:40 AM
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.
Solved! Go to Solution.
- Labels:
-
Discovery
-
Orchestration (ITOM)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2019 03:06 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2019 12:03 PM
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

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2019 03:06 PM
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.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2019 08:13 AM
Thanks, Andrew. CI's were being created but I wasn't aware that some of our printers don't have a name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2024 04:16 AM
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.