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 · ‎06-30-2021

You can disable the 'Generic OID Prevention' business rule and it wont do that check for you.

Naomi5 · ‎06-30-2021

Thank you, Doug.

Just want to say ... I am a big fan! Your videos helped me tremendously!!

doug_schulze · ‎06-30-2021

Oh, so you're the ONE that watched them... 😉 lol...

Glad they could be of service and welcome to the community! Lots of great voices here that have done tremendous things with Discovery.

jrmckins · ‎08-25-2021

Oh man, you're running with scissors!!!