Issues
- Cannot process SNMPv3 Informs due to random Engine ID associated with usersNMS-12473Resolved issue: NMS-12473Chandra Gorantla
- Update examples/opennms.conf to be JDK11-compatibleNMS-12468Resolved issue: NMS-12468Ronny Trommer
- MIB Compiler fails with Null Pointer ExceptionNMS-12459Resolved issue: NMS-12459Christian Pape
- Improve alarmd Drools engine performance by using STREAM modeNMS-12455Resolved issue: NMS-12455Jesse White
- Inefficient locking in the TopologyUpdater classNMS-12443Resolved issue: NMS-12443Markus von Rüden
- Ticket-creating automations are incorrectly enabled by defaultNMS-12439Resolved issue: NMS-12439Christian Pape
- Use Router Id (and maybe AS) to associate node with exporting router's dataNMS-12436Resolved issue: NMS-12436Christian Pape
- Associate exporter node using Observation Domain IdNMS-12435Resolved issue: NMS-12435Christian Pape
- Add system test for IpfixTcpParserNMS-12434Resolved issue: NMS-12434fooker
- Classification Engine: The end of the range is excluded, which is not intuitiveNMS-12433Resolved issue: NMS-12433Markus von Rüden
- Classification UI: Error responses are not shown properlyNMS-12432Resolved issue: NMS-12432Markus von Rüden
- Cannot define a specific layer in topology app URLNMS-12431Resolved issue: NMS-12431Markus von Rüden
12 of 12
Cannot process SNMPv3 Informs due to random Engine ID associated with users
Fixed
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Details
Assignee
Chandra GorantlaChandra GorantlaReporter
Alejandro GalueAlejandro GalueComponents
Sprint
NoneFix versions
Affects versions
Priority
Major
Details
Details
Assignee
Chandra Gorantla
Chandra Gorantla
Reporter
Alejandro Galue
Alejandro Galue
Components
Sprint
None
Fix versions
Affects versions
Priority
MajorPagerDuty
PagerDuty
PagerDuty
Created January 13, 2020 at 7:38 PM
Updated March 20, 2020 at 11:06 PM
Resolved February 21, 2020 at 3:23 PM
Activity
Show:
Jeff GehlbachFebruary 4, 2020 at 8:52 PM
Poking at this in a Vagrant lab now.
Jesse WhiteJanuary 16, 2020 at 9:24 PM
Alejandro GalueJanuary 13, 2020 at 7:57 PM
The problem could affect all Meridian versions as the UsmUser handling dates from 2011, but for now, I've added M2018 and M2019 to the list.
A customer has reported a problem on Trapd when receiving SNMPv3 Informs. Upon restarting OpenNMS, Trap stops processing Informs, and the following error appears on the log:
On the source code, a random Engine ID is associated with each USM User defined in trapd-configuration.xml, which is the behavior when an explicit ID is not passed when creating the UsmUser object, and I believe this is the source of the problem.