printer devices are not discovering using patterns even after probes to pattern migration

Anthony78
Kilo Sage

I have done the Migration from Probes to patterns but still the printer devices are using probes to discover .

 

Is anyone facing the same issue and found any solution , printer devices are not creating any relationships as well and because of this it's showing under CMDB Orphan health dashboard.

1 ACCEPTED SOLUTION

I don't think any pattern is used to identify the printers. I have only seen the windows printer pattern so far. If you see SNMP they are mostly for network devices. Like switches and router. I hope it helps.  I have done a quick discovery to verify this. We have also done migration in past. And can confirm no pattern got triggered. 

View solution in original post

5 REPLIES 5

Pratiksha
Mega Sage
Mega Sage

1) Check the SNMP credentials are present.

2) Check port 161 open. 

3) Try quick discovery

4) if does not work then see if mid server is allowed to talk to the device. 

 

Regards, 

Pratiksha

@Pratiksha  ,

 

Thanks for the response, Basically i can able to discover the printer devices but still it's using Probes to discover not Pattern even after migration from Probes to pattern .

 

may i know , printers on your instance are using probes or patterns to discover and if it's using pattern then what pattern it is using ?

I don't think any pattern is used to identify the printers. I have only seen the windows printer pattern so far. If you see SNMP they are mostly for network devices. Like switches and router. I hope it helps.  I have done a quick discovery to verify this. We have also done migration in past. And can confirm no pattern got triggered. 

Printer is also connected to a network right , anyway

I have created a case with servicenow and got to know that still few devices are using probes and printers are one of them even after migration.

 

I would like to confirm the same behavior for others too because Probes based discovery not creating any relationship and we have to create the relationship manually in order to retire the dependent CIs when main Ci retires.

 

Thanks for your input.