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 .220.127.116.11.4.1.1214. So why were we .2?
Problem: MIB of the traps changed from .18.104.22.168.4.1.1214* to .22.214.171.124.4.1.1214* following the reboot of the TIDAL master. The server was rebooted to apply the monthly patches to Microsoft (KB2621440)
Master version: 126.96.36.1994
OS: Windows Server 2008 R2 Standard