best practice to discover the only printers of the entire network

[Gaetano De Mitr]

Hello everyone,

I have a question about best practice on discovery schedule to retreive only information on Printer device.

into customer network we are using A ip addresses class (10.0.0.0) to manage the device.

My question is:

What is the best pratice to execute a Discovery on entire network to retreive only printer information, without know ip range address?

Thank you so much!

Regards,

Gaetano

EDIT:

I also have a doubt.
Consider the following scenario.

Step 1:
On January 1, 2017, a discovery is made (using an IP range ranging from 10.0.0.1 to 10.0.0.255) and 100 printers are registered with their IP addresses.

Step 2:
Discovery is blocked ... and starts again after 2 years.
1 January 2019, where about 60 printers have changed their IP address (which is defined in a range of different IPs, for example: 192.168.0.1 to 192.168.0.255).

Using the discovery schedule, configured on 1 January 2017, the 60 printers that changed IPs would not be taken into consideration.
For this I would like to understand the best way to discover all the printers on the network, even if these dynamically change the IP address

I believe that the only way that leads to a correct reconciliation is the MAC Address using the Hardware Rule that starts on Printer type CI

[valarmathi_kann]

Hi Gaetano De Mitri

    You can create a ServiceNow Behavior Discovery by pointing the MID server to discover devices based on the Behavior.

    You can go through the below doc to create a Discovery Behavior.

https://docs.servicenow.com/bundle/london-it-operations-management/page/product/discovery/task/creat...

[Gaetano De Mitr]

Hello,

thanks for your answer.

I have just created a discovery behavior based on snmp only, but I would like execute a discovery for only Printer and not Switch,Router or other device based on snmp protocol.

Question:

Can I execute a Discovery using unique SNMP Community credential?

[Harps1]

If the community string only works for printer devices then you can create a schedule using the SNMP behavior and align that credential to either that MID or the schedule. It will still attempt to connect to any device with your defined SNMP port open but it wont authenticate. Also ensure that the other network devices dont allow you to read with the string of "public" 

[doug_schulze]

You would want to do a combination of things.

1. Set up a SNMP only behavior that you apply to your discovery schedule.

2. Use the discovery configuration console to disable all network devices leaving printers enabled.