Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 16.0.3, 16.0.4, 17.0.0
-
Fix Version/s: 18.0.0, Meridian-2016.1.0
-
Component/s: Enhanced Linkd / Linkd
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Environment:OpenNMS runs an three dedicated server, one for the Database, one for the GUI and one for the monitoring. The server have more than enough memory and CPU power so this couldn't be the problem.
-
Epic Link:
-
Sprint:November Releases Sprint
Description
The BridgeBridgeTopologie discovery in a big installation of an customer ( over 7000 nodes and 12000 links) is very slow and need sometimes hours for a single node.
Picture 1 shows the amount of time that enlinkd needs for the BridgeBridgeTopologie the have 34 active layer2 interfaces. The other Protocols (cdp and lldp) are as fast as usual.
In a test run with only one Node enlinkd needs only seconds for the discovery (Picture 2).
I add the logfiles of enlinkd, eventd and the output.log.
The JDBC-Errors in eventd.log seems to be caused by reimport form a big amount of Nodes with the REST-API.
