Bug 1268133

Summary:	[RFE] RHEV Manager support for SNMPv3 traps
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Sarvesh Pandit <sapandit>
Component:	ovirt-engine	Assignee:	Ravi Nori <rnori>
Status:	CLOSED ERRATA	QA Contact:	Jiri Belka <jbelka>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.5.4	CC:	fdeutsch, gklein, iheim, ivan.makfinsky, juwu, lbopf, lsurette, lsvaty, mgoldboi, michal.skrivanek, mperina, oourfali, pstehlik, rbalakri, Rhev-m-bugs, rnori, sbonazzo, srevivo, ykaul
Target Milestone:	ovirt-4.0.1	Keywords:	FutureFeature, ZStream
Target Release:	4.0.1	Flags:	jbelka: testing_plan_complete+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	With this enhancement, support for SNMP v3 traps was added. RHV-M is now able to provide SNMP v2c and v3 traps. New SNMP related options which can be set along with the default values can be found at: /usr/share/ovirt-engine/services/ovirt-engine-notifier/ovirt-engine-notifier.conf.	Story Points:	---
Clone Of:
Clones:	1348933 (view as bug list)		Environment:
Last Closed:	2016-08-23 20:29:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1348933

Description Sarvesh Pandit 2015-10-01 21:35:30 UTC

Description of problem:
Currently, SNMPv2 is the only trap type RHEV-M will send. Request for Enhancement. Add a new feature to RHEV-M. Ability to send SNMPv3 traps in addition to SNMPv2 traps.

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

- What is the nature and description of the request?

Request for Enhancement. Add a new feature to RHEV-M. Ability to send SNMPv3 traps in addition to SNMPv2 traps.

- Why do you need this? (List the business requirements here)

Customer has security requirements that all SNMP traffic be SNMPv3. At the moment, the RHEV-M system only sends traps via SNMPv2. This is a government contract and this requirement was passed on to us Engineers.

- How would you like to achieve this? (List the functional requirements here)

In a similar way as to how SNMP traps are configured now in RHEV-M, v3.5.4. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Administration_Guide/Configuring_the_Red_Hat_Enterprise_Virtualization_Manager_to_Send_SNMP_Traps.html

- Do you have any specific time-line dependencies?

Our timeline need is asap. This program will go live within the next 6 months and the sooner this feature is available, the sooner we can navigate the paperwork for the upgrade approval.

- List any affected packages or components.

According to the documentation, this appears to be a change to the ovirt-engine-notifier component of RHEV.

- Would you be able to assist in testing this functionality if implemented?

Yes.

- For each functional requirement listed in the previous question, can test to confirm the requirement is successfully implemented.

Not sure I understand this sentence. There is only one functionality requested here and yes, we will test it.

Comment 9 Martin Perina 2016-06-22 10:50:26 UTC

Fixing milestone and flags after cloning

Comment 10 Jiri Belka 2016-07-11 15:57:55 UTC

ok, ovirt-engine-tools-4.0.2-0.2.rc1.el7ev.noarch

tested all SNMPv3 security levels against iReasoning mibbrowser's trap receiver.

Comment 12 errata-xmlrpc 2016-08-23 20:29:40 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-1743.html