Last updated: 2021-11-08

Source: https://support.freshservice.com/support/solutions/articles/221269-snmp-device-discovery-

The Freshservice Probe lets you discover and manage all SNMP (v1, v2 & v3) devices on your network in the Assets database.

The SNMP Devices supported in Freshservice are:

For all the supported devices, interface information will be automatically fetched and updated under the device properties in Freshservice. For printers, additional information such as Input units, Output units, and Marker units will also be updated in every scan. This information can be accessed from the Components section of each device. For example, the component information for printers will look like this,

All other SNMP devices that are not supported are added to Freshservice under Hardware -> Other Devices -> SNMP. These devices will not be counted as managed assets.

Setting up the SNMP device scan in the Probe:

SNMP devices are automatically scanned when an IP range is scanned using the Freshservice Probe. If you have a dedicated SNMP string in your network, it can be specified while creating a new IP Range scan. If the SNMP string field is not filled out, the probe looks for devices in the default string "public". Learn more about scanning and discovering assets in your network here.

Manually changing the device type of your SNMP device:

In some cases, the SNMP device type may not be identified correctly. In such situations, the device will be listed under Hardware -> Other Devices -> SNMP

These devices can be moved to one of the supported device types by performing any of the following steps:

Changing Device Type Individually:

Changing Device Type in Bulk:

Serial Number Discovery

     The probe uses the merged oid library to discover the serial number from any SNMP device. A single SNMP device can be matched in a model(exact match), series, and vendor. Our priority order is as follows: model, second series, and the third vendor. If none of these are able to fetch the serial number then we have a fallback (commonly used) OIDs to fetch the serial number.

The priority order is:

Example:

In the above configuration, if the scanned SNMP device SystemObjectID is 1.3.6.1.4.1.9.1.339 then the probe will match all the above three entries, and look for the serial number in the SNMP device according to the priority as mentioned above.  So according to that logic, the probe will check the following OIDs in Order:

The Probe will iterate the above Serial number OIDs in order(priority) until a valid serial number is found.

Other Options:

Example:

Model/Product Discovery:

     The probe will fetch the model/Product value from the merged oid\_library and exact matched OID entries model value will be fetched irrespective of the category.  And the same value is matched/created in the products in freshservice application side.

Manufacturer Discovery:

     The probe will fetch the Manufacturer value from the oid\_library in the same way the serial\_number is fetched.

Example:

In the above configuration, if the SystemObjectID is 1.3.6.1.4.1.9.1.339 then the probe will fetch the manufacturer value as "Cisco Systems". In this case, since the manufacturer in the model and series are not configured, the next priority is the vendor.

Other Type Fields:

     To configure the other type fields the customer can specify the type field label as key and the OID needed to be fetched as a value in the type\_fields JSON column.

Note: When Type field label is used as a key, the label should be similar to the label in Freshservice application under the asset type

The process followed by the probe to fetch the type fields is the same as fetching the serial number, as mentioned above.  The priorities and options remain the same.