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 184.108.40.206.4.1.1824 but am seeing the following OID in SNMP adaptor log file: 220.127.116.11.18.104.22.168.5.6.
Question: Would like to understand why this OID mismatch between what is sent Vs what is received by TEO?
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:
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.
CIAC Adoption Pilot Engineering Lead
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...