MIB of the SNMP traps changed after master server reboot
Has anyone using SNMP Actions run into the below issue? I'm just curious if anyone else has seen this behavior and if you have any thoughts. I've already worked with support on this and we couldn't come up with a reason why this occured. Their documentation indicates the value should always be .188.8.131.52.4.1.1214. So why were we .2?
Problem: MIB of the traps changed from .184.108.40.206.4.1.1214* to .220.127.116.11.4.1.1214* following the reboot of the TIDAL master. The server was rebooted to apply the monthly patches to Microsoft (KB2621440)
Master version: 18.104.22.1684 OS: Windows Server 2008 R2 Standard
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...