Classification Criteria for SNMP Devices

[Community Alums]

I'm trying to wrap my head around classification criteria and how it works. I mostly use SNMP OIDs to classify devices, but we have many that have the standard unusable OID "1.3.6.1.4.1.8072.3.2". I've used sysDesc as a criteria for one device which makes sense since there is a sysDescr OID pulled during the SNMP - Classify probe, but I'm unable to use that criteria for this device I'm working on.

I'd like to understand where the Name values on the classification criteria come from, and how I can figure out the correct parameter to put there. I tried looking at the 'Routing = true' SNMP criteria to understand, but I cannot find any SNMP fields that deal with routing values, and when I look at discovery logs that use the Network router pattern, specifically the SNMP - Classify input logs from that device, I don't see anywhere where the routing value is collected. So how is it able to classify these devices to the "Standard Network Router" classification, when the SNMP - Classify probe isn't reflecting a "routing = true" value?

Any help or resources are much appreciated!

[Runjay Patel]

Hi @Community Alums ,

Classification criteria are defined in the SNMP Classifications table and are based on the device's attributes, such as sysObjectID and sysDescr.

Key Fields involved in SNMP Classification:

• Name
• sysObjectID
• sysDescr Contains: Optional field to match part of the device description.
• sysName Contains: Optional field to match part of the device name.
• Class: Specifies the target CI class (e.g., cmdb_ci_network, cmdb_ci_storage_device).

See below very common Issues with SNMP Classification

• If a device isn’t classified, check if its sysObjectID is missing in the SNMP Classifications table.
• Use the Discovery Logs to view the sysObjectID and add a new classification.
• Ensure the sysObjectID and sysDescr Contains fields are correctly matched to the device.
• If SNMP classification fails, ensure that valid SNMP credentials are configured and tested in Credentials.
• Vendors may update sysObjectID for newer devices. Update the SNMP Classifications table as needed.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

[Community Alums]

Hi Runjay,

Thanks for the response, I am already currently building SNMP classifiers using SNMP OIDs. What I'm trying to understand is "Classification Criteria" in the SNMP Classifier, those stored on discovery_class_criteria and how the 'name' value for these records are found. For example, if you set in the SNMP classifier that "sysDescr contains Aruba" it would classify any devices as Aruba using that SNMP Classifier. In this case, the Cisco Firepower device using a generic OID that cannot be added, and the description pulled from these devices does not contain any usable key words I can classify based on. So I am hoping to understand Classification Criteria so I can look at using another classify value that isn't the sysdescr. So far I've gathered its from the values in the SNMP - Classify probe and Sensor, but hoping to find a more comprehensive list or information.

Miranda

[Runjay Patel]

Hi @Community Alums ,

It will check first with OID if it didnt matches then it will look for sysDescr/nameDescr Contains.

[Marcio Olivieri]

Hello @Runjay Patel , what is the recommended approach when a certain table (cmdb_ci_crac) is not displayed when creating a new classifier? How to make it visible there?