Any Workarounds for SNMP OIDs starting with "1.3.6.1.4.1.8072.3.2." are prevented from inserting. For more information please see KB0751287?

Naomi5 · ‎06-30-2021

I've been running discovery on a certain IP address without success.

Upon reading the SNMP input payload, I found

<sysObjectID oid="1.3.6.1.2.1.1.2" type="SnmpObjectId">.1.3.6.1.4.1.8072.3.2.10</sysObjectID>

And 1.3.6.1.4.1.8072.3.2.10 was not found in the SNMP OID Classification, so I attempted to create one.

Ended up with the result that stopped be from creating one for this particular OID "SNMP OIDs starting with "1.3.6.1.4.1.8072.3.2." are prevented from inserting. For more information please see KB0751287."

In a big pickle here... since I was able to resolve previous discovery issues with the above method. Is there any workaround for this? How do I proceed forward to successful discover the devices?

Thank you so so so much in advance. Any input will be greatly appreciated!

doug_schulze · ‎06-30-2021

Yes that could be an impact, so I would check the device list they mention to see if any would be impacted by this in your environment. If so, you could create custom classifiers for the devices and using the classification criteria you should be able to work around this as its my current understanding that the classification criteria is the primary check then we look through the snmp sysoids. But as always, test in dev and see how it can work best for you.

View solution in original post

doug_schulze · ‎07-01-2021

If you dont see this, you should open a case with support, something might be amiss..

Community Alums · ‎11-17-2021

Hi Doug,

How can we find out what qualifies as a classification criteria for these particular devices?

Any video's or white papers that can help shed some light?

Thanks

Luigi

doug_schulze · ‎11-17-2021

You can see that in the previous screen shots you can see things like sysdescr and other values you can use. You also have the ability to turn on classification debug to see everything that was caught and attempted to measure in the log files..

MBannis · ‎05-05-2023

Hi Doug,

I have a strange one here.. I'm attempting to discovery Synology NAS Devices which when attempting to discover via ServiceNow will give me SNMP Input results with that exact .8072 SNMP OID, yet, on Synology's website their SNMP MIBs show OIDs with .6574. How do I get around this? Why wouldn't ServiceNow see .6574 vs the very generic .8072

So even if I were to load the MIBs provided by Synology discovery may not work becfause the OIDS being read are different? Am I correct in that statement?

Daniel Needles1 · ‎01-23-2023

The solution for me was to use the sysDescr because though the vendor was too lazy to sign up with IANA.org for their own enterprise OID (https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers) and used the Net-SNMP one out of the box, they did at least populate the sysDescr with a unique description. So instead of adding a SNMP OID and a Classifier, I simply added a SNMP Classifier based on the SysDescr. Specifically, Discovery Definitions => CI Classification => SNMP. There (in this case) I created a reference to a BarracudaDevice with a Classificiation Criteria (tab) with sysdescr contains Barracuda Email Security Gateway. NOTE: I first had to create a Baracude Email Security Gateway child class under Network Gear. A dated but still applicable YouTube video on this is - https://www.youtube.com/watch?v=6ULRbpGOSB4 Also if you want this to show up in Changes and Incidents, not just tasks you need to add it to the Principal Class, which can be done by navigating to cmdb_class_info.LIST, create a new Class, click the drop down arrow on Class and set Principal Class to True.