All Apps and Add-ons

SNMP Modular Input: Why are SNMP traps received showing up as Hex garbage data?

DavidLago
New Member

I have configured several different devices such as Cisco network switches, HP Storages, Citrix NetScaler and some others to send SNMP traps to SPLUNK. However, whatever comes in through the SNMP port is shown as hex garbage data, like:

"0\x82\xC1public\xA7\x82\xB2 \xB7".

A Splunk technician told me that the problem is that my Splunk needs a MIB called RFC1155-SMI, and in order to make it work, I would have to download the python module and insert it into the ta-snmp extension.

I placed the file within the folder in lots of different names and forms within the folder "G:\Splunk\etc\apps\snmp_ta\bin\mibs".

Still, Splunk shows the events in HEX.

The files could be audited reaching the URL below:

https://www.dropbox.com/s/ewgmosmgt9odi7e/MIBs.zip?dl=0 [No malware, obviously].

How do I solve this?

0 Karma

DavidLago
New Member

An update:

After putting the original IP address in the field "TRAP listener host", (in Data inputs » SNMP » "MyEntry"), the hex problem was solved. But the MIB still doesn't show up the info treated as it should be.

Could anyone share the MIB file that is supposed to be placed in the "G:\Splunk\etc\apps\snmp_ta\bin\mibs" folder?

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...