All Apps and Add-ons

SNMP Defaul TCP-MIB not recognized

marcoscala
Builder

Hi All,
I'm trying to implement "snmp_ta" modular input. We got several snmp trap collected but I'm afraid there's something I'm missing about SNMP trap interpretation.

I have lots of error like this one:

02-03-2014 10:40:56.242 +0100 ERROR ExecProcessor - message from "python /opt/splunkforwarder/etc/apps/snmp_ta/bin/snmp.py" Exception resolving OID to MIB Name: NoSuchObjectError({'str': 'No MIB registered that defines 1.3.6.1.2.1.6.13.1.1.10.245.193.90.22.10.7.100.14.56603 object, closest known parent is 1.3.6.1.2.1 (SNMPv2-SMI::mib-2)'})

But "1.3.6.1.2.1.6.13" is the default TCP-MIB that's included in smnp_ta default mibs in the "pysnmp__mibs-0.1.4-py2.7.egg"

So, why this trap is not recognized?

Thanks for help,

Marco Scala

Tags (2)
0 Karma

Damien_Dallimor
Ultra Champion

Have you declared the MIB in your stanza ?

alt text

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)

Hello Splunkers,   So you searched, “what is the name of the usb key inserted by bob smith?”  Not gonna lie… ...

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...