SNMPv3 info erased from snmp-config.xml when using GUI

Description

While the SNMP editor has an option for "v3" it doesn't have enough options to actually make it work (auto-passphrase, privacy-protocol, etc.) so one needs to add it manually to the snmp-config.xml file:

<definition version="v3" security-name="opennms" auth-passphrase="thong" auth-protocol="SHA" privacy-passphrase="thong" privacy-protocol="DES">
<ip-match>172.17.0.5-7</ip-match>
</definition>

and then OpenNMS needs to be restarted.

However, if the GUI editor is used after this entry has been added, it will be removed. This is very frustrating as unless there is a recent backup the data is lost, and this forces the manual editing of this file always.

Environment

Operating System: All Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger July 11, 2013 at 11:28 AM
Edited

Reducing priority since the issue has been almost completely remedied in 1.13 unstable branch.

Markus von Rüden July 10, 2013 at 7:26 AM

The UI was modified so now it is possible to edit all v3 parameters within the UI.
The algorithm to optimize the snmp-config.xml was also edited and a few bugs were fixed within that algorithm.

However somehow the optimization algorithm does not support the ip-match-Segment and therefore the issue still exists.

Markus Neumann July 9, 2013 at 5:45 PM

Hy Markus,

you have been working on SNMPv3 configs features. Can you add something to this issue?

Thanks

Charles Hopkins March 7, 2013 at 10:23 AM

Is there any chance of this getting addressed?

Martin Lärcher February 8, 2012 at 2:28 PM

The required restart of OpenNMS is not usable after change snmp-config.xml.
Also a reload via uei.opennms.org/internal/configureSNMP does not work.

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created July 26, 2009 at 12:41 PM
Updated July 26, 2023 at 2:20 PM

Flag notifications