Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Trap OID mismatch between send/receive - why?

I am using a trapgen tool with the following command to send a trap to TEO:

trapgen -f input.txt

input.txt file contains the sender's OID specified with a -o option. Now on to my question:

Regardless of the what the sender's OID is, the OID received by SNMP adaptor in TEO is different as seen in the log file. In my case, I am sending the following OID 1.3.6.1.4.1.1824 but am seeing the following OID in SNMP adaptor log file: 1.3.6.1.6.3.1.1.5.6.

Question: Would like to understand why this OID mismatch between what is sent Vs what is received by TEO?

thanks,

Jamal

1 REPLY
Cisco Employee

Trap OID mismatch between send/receive - why?

Same post from the email I sent and posted otherplace.

Here is the email info as well...

My assumption is because of some other parameter in that tool. It is *forcing* it to be that. Maybe it’s the version or something in the variable bindings. I do not know SNMP deep enough or that tool deep enough to give a complete answer. I found some sites by googling that tool, so that’s a start:

http://mango.serotoninsoftware.com/forum/posts/list/217.page

http://docstore.mik.ua/orelly/networking_2ndEd/snmp/ch10_03.htm

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094aa5.shtml

Again, my understanding and knowledge of SNMP is limited, so if you need a SNMP expert, better to look to the networking TAC I’d guess.

I was able to send in a different OID by running the command like this:

Trapgen –d 172.18.173.116 –o .1.3.1.4.1.2654 –v .1.3.1.4.1.2854.1.2 INTEGER 20

This was picked up in TEO like this…

04/25 15:49:01:075[TrapListener.0]: (mem=45222712/375521280) TrapReceiveHandler: Incoming trap from 172.18.173.7 to local port 162

04/25 15:49:01:075[TrapListener.0]: (mem=45222712/375521280) TrapReceiveHandler: Incoming trap version: V1 and community string: public

04/25 15:49:01:075[TrapListener.0]: (mem=45222712/375521280) TrapReceiveHandler: Incoming trap has no Trap OID

04/25 15:49:01:075[TrapListener.0]: (mem=45222712/375521280) TrapReceiveHandler: Convert incoming V1 trap's trap OID to: 1.3.1.4.1.2654.0.1

04/25 15:49:01:075[TrapListener.0]: (mem=45222712/375521280) TrapReceiveHandler: Trap source FQDN :IA-TAC-AUTO-TLS.CISCO.COM

04/25 15:49:01:075[TrapListener.0]: (mem=45222712/375521280) TrapReceiveHandler: Trap source from computer:IA-TAC-AUTO-TLS

And I verified that in the GUI.

Furthermore I found that I could trigger off of “*” for Trap OID in the trigger. So you can put a star to trigger off of any OID, and then just put some criteria for the variable bindings. This might work better.

Remember in the process we wrote and gave you, that the trigger does a search into the variable binding for *ERROR* so if you were monitoring "*" OID but still using that conditional it should be fine.

--Shaun Roberts shaurobe@cisco.com CIAC Adoption Pilot Engineering Lead
483
Views
0
Helpful
1
Replies