Bug 614300 - SNMP MIB does not define a notification-type
SNMP MIB does not define a notification-type
Product: RHQ Project
Classification: Other
Component: Alerts (Show other bugs)
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: Heiko W. Rupp
Corey Welton
Depends On:
Blocks: jon30-bugs 648779
  Show dependency treegraph
Reported: 2010-07-13 23:54 EDT by James Livingston
Modified: 2016-02-21 19:54 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 648779 (view as bug list)
Last Closed: 2011-05-23 21:10:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
modified MIB (3.11 KB, text/plain)
2010-07-13 23:54 EDT, James Livingston
no flags Details

  None (edit)
Description James Livingston 2010-07-13 23:54:47 EDT
Created attachment 431665 [details]
modified MIB

The MIB that JON ships with defines the contents of the SNMP alert notifications it sends. However, it doesn't define a NOTIFICATION-TYPE for the trap itself.

Attached is a modified version of the MIB which does define that. I don't know a whole lot about MIBs, but the customer said it worked for them with SNMPv2c - no idea if this version breaks v1 or v3.
Comment 2 Corey Welton 2010-09-28 08:38:31 EDT
heiko, how does this patch look?
Comment 3 Heiko W. Rupp 2010-10-18 09:35:16 EDT
Seems to be ok to me. Needs a new release date though :)
Comment 4 Heiko W. Rupp 2010-10-18 11:52:57 EDT
rev 414c79341bef50565825f85fc9201b205fb972b9 in master 
rev b57b9bf1f93bbd2d0059b2fd3f04ae4755d28ac9 in release-3.0.0
Comment 5 Corey Welton 2011-01-03 09:50:45 EST
QA Verified, RHQ-mib.txt now contains 'NOTIFICATION-TYPE' reference:

Comment 6 Corey Welton 2011-05-23 21:10:30 EDT
Bookkeeping - closing bug - fixed in recent release.
Comment 7 Corey Welton 2011-05-23 21:10:45 EDT
Bookkeeping - closing bug - fixed in recent release.

Note You need to log in before you can comment on or make changes to this bug.