Bug 1129274 - SNMPv3 trap notifications don't work if AES192 and AES256 privacy protocols used
Summary: SNMPv3 trap notifications don't work if AES192 and AES256 privacy protocols used
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: No Component
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-12 13:05 UTC by Yulia
Modified: 2022-03-31 04:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Yulia 2014-08-12 13:05:15 UTC 
Description of problem:
SNMPv3 trap notifications don't work if AES192 and AES256 privacy protocols used

Version-Release number of selected component (if applicable):


How reproducible:always


Steps to Reproduce:
1. Go to Administration - Server plugins.
2. Click on the Alert:SNMP plugin name.
3. Configure values for parameter "Privacy Protocol" equal to AES192 or AES256 from the "SNMP version 3 properties" section and save.
4. Trigger the alert conditions and validate trap attributes in trap receiver.

Actual results:
New setting has been saved and applied.The SNMP Trap notification hasn't been sent and in alert history message "Error while trying to send request:Message processing model 3 returned error:1405" is displayed

Expected results:
The SNMP Trap notification has been sent to configured target host.


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