Bug 1129274

Summary: SNMPv3 trap notifications don't work if AES192 and AES256 privacy protocols used
Product: [Other] RHQ Project Reporter: Yulia <prudius>
Component: No ComponentAssignee: RHQ Project Maintainer <rhq-maint>
Status: NEW --- QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.9CC: gerhard.dreschler, hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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: