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

Vicente · ‎04-02-2019

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.

Andrew Westerv4 · ‎04-02-2019

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.

View solution in original post

KKrabbenhoft · ‎11-08-2022

I have a similar issue when running a (Quick Discovery) against our MID Server internal IP. The logs indicate the MID Server selected is not suitable MID because it does not have Nmap value. We do not want to use Nmap and are using ip ranges to discover such things as printer, computers.

KKrabbenhoft · ‎12-13-2022

I have a similar issue when running a (Quick Discovery) against our MID Server internal IP. The logs indicate the MID Server selected is not suitable MID because it does not have Nmap value. We do not want to use Nmap and are using ip ranges to discover such things as printer, computers.