Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

All work

Select view

Select search mode

 
11 of 11

enlinkd maps link isssues

Description

We have deployed Open NMS in out site and we have added many switches to the Monitor manually. We have noticed that the network topology map is not able to show the connections even though we have the LLDP Neighbor Populated.
Initially it generated the map for 1 hour and then it stopped
Sample of initial map attached.

 

Environment

Ubuntu 20

Acceptance / Success Criteria

We have deployed Open NMS in out site and we have added many switches to the Monitor manually. We have noticed that the network topology map is not able to show the connections even though we have the LLDP Neighbor Populated.

Attachments

4

Lucidchart Diagrams

Details

Assignee

Reporter

Labels

Due date

HB Grooming Date

HB Backlog Status

Components

Affects versions

Priority

Parent

PagerDuty

Created September 1, 2022 at 7:57 PM
Updated May 10, 2023 at 2:35 PM

Activity

Antonio RussoSeptember 23, 2022 at 5:26 AM
Edited

Could you attach the walk of lldp mib from both devices?

Antonio RussoSeptember 23, 2022 at 5:24 AM

Hi, I'll go forward the attached walks if you attach here the results for both devices.
I explained why we were not able to match the link in the map, both devices need to have Snmp enabled.
In the case of Lldp, we can try to go forward bbut identification of the connected device is problematic because they use mac address or syslogname. 

I'll check the code for better identification in the case where one device has no LLDp MIBb support or is not snmp reachble.

Rohan RajSeptember 17, 2022 at 4:50 PM

I have fixed the SNMP Issues for teh OID 

snmpwalk  -v2c -c public1947 10.16.11.10 1.0.8802.1.1.2.1

snmpwalk  -v2c -c public1947 10.16.11.10 1.0.8802.1.1

and I disabled use-bridge-discovery="false"

But Still no links

Antonio RussoSeptember 2, 2022 at 10:33 AM

The last is an exception from the bridge discovery. Do you need bridge discovery? if not you can set use-bridge-discovery="false" in enlinkd-confoguration.xml.

Also 

snmpwalk  -v2c -c public1947 10.16.11.10 1.0.8802.1.1.2.1
iso.0.8802.1.1.2.1 = No Such Object available on this agent at this OID
vsrsadmin@map01:~$ snmpwalk  -v2c -c public1947 10.16.11.10 1.0.8802.1.1
iso.0.8802.1.1 = No Such Object available on this agent at this OID

means no lldp mib available on devices.

Rohan RajSeptember 1, 2022 at 8:54 PM

I have deleted the switch and added it back and after some time have noticeded the following error

 

2022-09-01 20:52:38,998 ERROR [EnhancedLinkd-Thread-5-of-5] o.o.n.e.DiscoveryBridgeDomains: run: node: [916], getting broadcast domain. Failed at least two domains found
2022-09-01 20:52:39,040 ERROR [EnhancedLinkd-Thread-5-of-5] o.o.n.e.DiscoveryBridgeDomains: run: node: [938], getting broadcast domain. Failed at least two domains found
2022-09-01 20:52:39,041 ERROR [EnhancedLinkd-Thread-5-of-5] o.o.n.e.DiscoveryBridgeDomains: run: node: [940], getting broadcast domain. Failed at least two domains found
2022-09-01 20:52:39,123 ERROR [EnhancedLinkd-Thread-5-of-5] o.o.n.e.DiscoveryBridgeDomains: run: executing task java.util.NoSuchElementException
java.util.concurrent.ExecutionException: java.util.NoSuchElementException
        at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?]
        at java.util.concurrent.FutureTask.get(FutureTask.java:191) ~[?:?]
        at org.opennms.netmgt.enlinkd.DiscoveryBridgeDomains.runDiscovery(DiscoveryBridgeDomains.java:230) ~[org.opennms.features.enlinkd.adapters.collectors.bridge-30.0.1.jar:?]
        at org.opennms.netmgt.enlinkd.common.Discovery.run(Discovery.java:105) ~[org.opennms.features.enlinkd.adapters.common-30.0.1.jar:?]
        at org.opennms.netmgt.scheduler.LegacyScheduler$1.run(LegacyScheduler.java:179) ~[org.opennms.core.daemon-30.0.1.jar:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
        at org.opennms.core.concurrent.LogPreservingThreadFactory$3.run(LogPreservingThreadFactory.java:124) ~[opennms-util-30.0.1.jar:?]
        at java.lang.Thread.run(Thread.java:829) ~[?:?]
Caused by: java.util.NoSuchElementException
        at java.util.Spliterators$1Adapter.next(Spliterators.java:688) ~[?:?]
        at org.opennms.netmgt.enlinkd.service.api.BridgeForwardingTable.getPort(BridgeForwardingTable.java:230) ~[org.opennms.features.enlinkd.service.api-30.0.1.jar:?]
        at org.opennms.netmgt.enlinkd.service.api.BridgeForwardingTable.getRootPort(BridgeForwardingTable.java:225) ~[org.opennms.features.enlinkd.service.api-30.0.1.jar:?]
        at org.opennms.netmgt.enlinkd.service.api.DiscoveryBridgeTopology.down(DiscoveryBridgeTopology.java:505) ~[org.opennms.features.enlinkd.service.api-30.0.1.jar:?]
        at org.opennms.netmgt.enlinkd.service.api.DiscoveryBridgeTopology.root(DiscoveryBridgeTopology.java:179) ~[org.opennms.features.enlinkd.service.api-30.0.1.jar:?]
        at org.opennms.netmgt.enlinkd.service.api.DiscoveryBridgeTopology.calculate(DiscoveryBridgeTopology.java:264) ~[org.opennms.features.enlinkd.service.api-30.0.1.jar:?]
        at org.opennms.netmgt.enlinkd.DiscoveryBridgeDomains.lambda$runDiscovery$0(DiscoveryBridgeDomains.java:189) ~[org.opennms.features.enlinkd.adapters.collectors.bridge-30.0.1.jar:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
        ... 1 more