Why is this SNMP classify failing?

[yandewulf]

Expecting my NEW classifier (priority 9) for RUBRIK (storage) devices to trigger on finding the value "rubrik" in sysdescr but it does not. Discovery keeps classifying these devices as appliance as I have an SNMP classifier (priority 999) that triggers on the device OID.  How can I TEST my NEW classifier, or what log might show what value the sysdescr has?    

[Patrick DeCarl1]

Is that value coming back in the "SNMP - Classify" probe? if so, can you share a screenshot? Also, is there no sysobjectid? I recommend using a SNMP OID of sysobjectid vs contains in a description. 

[yandewulf]

Hi Patrick, yes the value of "sysDescr" does come back. I shared the return below. Yes there is also a sysobjectid but because it contains an OID that is shared with another manufacturer, model and class of CIs I can not use it otherwise it puts the device in the wrong class.  Thank you Jan 

<results probe_time="281" result_code="0">
<result source="xxx.xxx.xxx.xxx">
<snmp host="xxx.xxx.xxx.xxx" ip="xxx.xxx.xxx.xxx" timed_out="false">
<iso oid="1">
<org oid="1.3">
<dod oid="1.3.6">
<internet oid="1.3.6.1">
<mgmt oid="1.3.6.1.2">
<mib-2 oid="1.3.6.1.2.1">
<host oid="1.3.6.1.2.1.25">...</host>
<system oid="1.3.6.1.2.1.1">
<sysName oid="1.3.6.1.2.1.1.5" type="SnmpOctetString">RVMHM188S014165</sysName>
<sysUpTime oid="1.3.6.1.2.1.1.3" type="SnmpTimeTicks">394278070</sysUpTime>
<sysDescr oid="1.3.6.1.2.1.1.1" type="SnmpOctetString">
Linux RVMHM188S014165 4.13.0-45-rubrik4-generic #50~16.04.1 SMP Thu Jan 10 17:08:19 PST 2019 x86_64
</sysDescr>
<sysObjectID oid="1.3.6.1.2.1.1.2" type="SnmpObjectId">.1.3.6.1.4.1.8072.3.2.10</sysObjectID>
</system>

[Andrew Westerv4]

SNMP Classification prioritizes OID Classification over Criteria. You will need to either remove your OID Classification or re-associate to your new classifier.

[yandewulf]

Hi Andrew, Followed up on your idea, I "in-activated" the OID classification, ran discovery, this time the NEW classifier worked and it reclassified the CI to "Storage Server" class. However I then "re-activated" the OID classification, ran discovery again and it reclassified the CI back to the "Appliance" class 😞   This proves OID classifiers take priority over the classifiers' "order" field. Opening an case with ServiceNow to have this looked into.  Thank you Jan