MIB of the SNMP traps changed after master server reboot

Unanswered Question
Apr 12th, 2012

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 .1.3.6.1.4.1.1214.  So why were we .2?

Problem: MIB of the traps changed from .2.3.6.1.4.1.1214* to .1.3.6.1.4.1.1214* following the reboot of the TIDAL master.  The server was rebooted to apply the monthly patches to Microsoft (KB2621440)

Master version: 5.3.1.354
OS: Windows Server 2008 R2 Standard

Thanks.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)

Actions

Login or Register to take actions

This Discussion

Posted April 12, 2012 at 9:14 AM
Stats:
Replies:0 Overall Rating:
Views:458 Votes:0
Shares:0
Tags: snmp
+
Categories: Master
+

Related Content

 

Discussions Leaderboard

Rank Username Points
1
Marc Clasby
84
2
Tracy Donmoyer
65
3
Derrick Au
63
4
rami_rgare
25
5
Joe Fletcher
23
Rank Username Points
Derrick Au
5