[opennms-discuss] OpenNMS Enlinkd does not detect links in Topology

[UdayKumar]

Hi Team,

OpenNMS is unable to show links in topology. OSPF & LLDP are enabled on all
devices. OSPF adjacency is established b/w some of our devices. LLDP
neighborship is also formed among all as per our topology. LLDP and OSPF
mibs are successfully compiled in OpenNMS.

We are using IPInfusion's OcNOS devices and Cisco routers in our topology.
Links of Cisco nodes are detected but not of OcNOS.

We are running OpenNMS 20.0.0 on Kali Linux. EnhanceLinkd is UP and running.
Any inputs will be highly appreciated.

***@kali:~# opennms -v status
OpenNMS.Eventd : running
OpenNMS.Alarmd : running
OpenNMS.Bsmd : running
OpenNMS.Ticketer : running
OpenNMS.Trapd : running
OpenNMS.Queued : running
OpenNMS.Actiond : running
OpenNMS.Notifd : running
OpenNMS.Scriptd : running
OpenNMS.Rtcd : running
OpenNMS.Pollerd : running
OpenNMS.PollerBackEnd : running
*OpenNMS.EnhancedLinkd : running*
OpenNMS.Collectd : running
OpenNMS.Discovery : running
OpenNMS.Vacuumd : running
OpenNMS.EventTranslator: running
OpenNMS.PassiveStatusd : running
OpenNMS.Statsd : running
OpenNMS.Provisiond : running
OpenNMS.Reportd : running
OpenNMS.Ackd : running
OpenNMS.JettyServer : running
opennms is running

But it shows some warning logs in enlinkd.log
***@kali:~# tail -f /var/log/opennms/enlinkd.log
2017-06-21 16:42:25,966 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty
2017-06-21 16:42:25,966 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty
2017-06-21 16:42:25,966 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty
2017-06-26 13:37:12,184 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty
2017-06-26 13:37:12,195 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty
2017-06-26 13:37:12,195 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty
2017-06-26 13:37:12,196 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty
2017-06-26 13:37:12,196 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty
2017-06-26 13:37:12,196 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty
2017-06-26 13:49:44,359 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler:
getReadyRunnable: queue is Empty

***@kali:~# cat /etc/opennms/enlinkd-configuration.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<enlinkd-configuration threads="5"
initial_sleep_time="60000"
rescan_interval="86400000"
use-cdp-discovery="true"
use-bridge-discovery="true"
use-lldp-discovery="true"
use-ospf-discovery="true"
use-isis-discovery="true"
/>

Below are my OpenNMS, Java & PostgreSQL details.

Version: 20.0.0
Server Time: Mon Jun 26 13:57:02 IST 2017
Client Time: Mon Jun 26 2017 13:57:14 GMT+0530 (India Standard Time)
Java Version: 1.8.0_131 (Oracle Corporation)
Java Runtime: OpenJDK Runtime Environment (1.8.0_131-8u131-b11-2-b11)
Java Specification: Java Platform API Specification (Oracle Corporation,
1.8)
Java Virtual Machine: OpenJDK Server VM (Oracle Corporation, 25.131-b11)
Java Virtual Machine Specification: Java Virtual Machine Specification
(Oracle Corporation, 1.8)
Operating System: Linux 4.9.0-kali4-686-pae (i386)
Servlet Container: jetty/9.4.0.v20161208 (Servlet Spec 3.1)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Database Type: PostgreSQL
Database Version: 9.6.3
Time-Series Strategy: RRDTool or JRobin

[Ronny Trommer]

Hi,

Post by UdayKumar
use-cdp-discovery="true"
use-bridge-discovery="true"
use-lldp-discovery="true"
use-ospf-discovery="true"
use-isis-discovery="true"

CDP / Bridge MIB / LLDP give you all the same information about a Layer 2 network but with three different mechanisms. All devices supporting BRIDGE-MIB get a link discovered, if they support CDP they get a link discovered and if they support LLDP as well, it got a link discovered. There is an BRIDGE-MIB, CDP and LLDP overlapping each other. So in worst case on devices which support all three of them, you get 3 x the number of links for this nodes which is not very useful IMHO.

With old Linkd it was possible to group nodes in packages and enable protocol per group of nodes which is currently not possible in Enhanced Linkd [1]. The configuration about protocols is global for all devices in your OpenNMS inventory. Additionally, there is no way how to visual differentiate OSFP from CDP links.

IMHO when you want useful information use

* just OSPF for visualising a OSPF routing network
* just ISIS for visualising a IS-IS routing network
* just use *one* of the three mechanisms for visualising a Layer 2 network

What link discovery protocols are support on your IPInfusion's OcNOS devices? In the documentation[2] you find the OIDs are used to build the links for each of the protocols. Check your devices if they support them.

[1] https://issues.opennms.org/browse/NMS-8818 <https://issues.opennms.org/browse/NMS-8818>
[2] http://docs.opennms.org/opennms/releases/20.0.0/guide-admin/guide-admin.html#ga-enlinkd-daemon <http://docs.opennms.org/opennms/releases/20.0.0/guide-admin/guide-admin.html#ga-enlinkd-daemon>

Post by UdayKumar
Hi Team,
OpenNMS is unable to show links in topology. OSPF & LLDP are enabled on all devices. OSPF adjacency is established b/w some of our devices. LLDP neighborship is also formed among all as per our topology. LLDP and OSPF mibs are successfully compiled in OpenNMS.
We are using IPInfusion's OcNOS devices and Cisco routers in our topology.
Links of Cisco nodes are detected but not of OcNOS.
We are running OpenNMS 20.0.0 on Kali Linux. EnhanceLinkd is UP and running.
Any inputs will be highly appreciated.
OpenNMS.Eventd : running
OpenNMS.Alarmd : running
OpenNMS.Bsmd : running
OpenNMS.Ticketer : running
OpenNMS.Trapd : running
OpenNMS.Queued : running
OpenNMS.Actiond : running
OpenNMS.Notifd : running
OpenNMS.Scriptd : running
OpenNMS.Rtcd : running
OpenNMS.Pollerd : running
OpenNMS.PollerBackEnd : running
OpenNMS.EnhancedLinkd : running
OpenNMS.Collectd : running
OpenNMS.Discovery : running
OpenNMS.Vacuumd : running
OpenNMS.EventTranslator: running
OpenNMS.PassiveStatusd : running
OpenNMS.Statsd : running
OpenNMS.Provisiond : running
OpenNMS.Reportd : running
OpenNMS.Ackd : running
OpenNMS.JettyServer : running
opennms is running
But it shows some warning logs in enlinkd.log
2017-06-21 16:42:25,966 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
2017-06-21 16:42:25,966 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
2017-06-21 16:42:25,966 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
2017-06-26 13:37:12,184 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
2017-06-26 13:37:12,195 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
2017-06-26 13:37:12,195 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
2017-06-26 13:37:12,196 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
2017-06-26 13:37:12,196 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
2017-06-26 13:37:12,196 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
2017-06-26 13:49:44,359 WARN [enlinkd-Thread] o.o.n.e.s.Scheduler: getReadyRunnable: queue is Empty
<?xml version="1.0" encoding="ISO-8859-1"?>
<enlinkd-configuration threads="5"
initial_sleep_time="60000"
rescan_interval="86400000"
use-cdp-discovery="true"
use-bridge-discovery="true"
use-lldp-discovery="true"
use-ospf-discovery="true"
use-isis-discovery="true"
/>
Below are my OpenNMS, Java & PostgreSQL details.
Version: 20.0.0
Server Time: Mon Jun 26 13:57:02 IST 2017
Client Time: Mon Jun 26 2017 13:57:14 GMT+0530 (India Standard Time)
Java Version: 1.8.0_131 (Oracle Corporation)
Java Runtime: OpenJDK Runtime Environment (1.8.0_131-8u131-b11-2-b11)
Java Specification: Java Platform API Specification (Oracle Corporation, 1.8)
Java Virtual Machine: OpenJDK Server VM (Oracle Corporation, 25.131-b11)
Java Virtual Machine Specification: Java Virtual Machine Specification (Oracle Corporation, 1.8)
Operating System: Linux 4.9.0-kali4-686-pae (i386)
Servlet Container: jetty/9.4.0.v20161208 (Servlet Spec 3.1)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Database Type: PostgreSQL
Database Version: 9.6.3
Time-Series Strategy: RRDTool or JRobin
--
Thanks & Regards,
Udaykumar
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-discuss mailing list
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

[UdayKumar]

Hi Ronny,

Thanks for your reply. I am sorry for my late response.

We found that IPInfusion's OCNOS devices does not support
LLDP OIDs used by Enlinkd for link detection.

Regards,
Udaykumar

Hi,
Just what I saw in your configuration, the default configuration is not
use-cdp-discovery="true"
use-bridge-discovery="true"
use-lldp-discovery="true"
use-ospf-discovery="true"
use-isis-discovery="true"
CDP / Bridge MIB / LLDP give you all the same information about a Layer 2
network but with three different mechanisms. All devices supporting
BRIDGE-MIB get a link discovered, if they support CDP they get a link
discovered and if they support LLDP as well, it got a link discovered.
There is an BRIDGE-MIB, CDP and LLDP overlapping each other. So in worst
case on devices which support all three of them, you get 3 x the number of
links for this nodes which is not very useful IMHO.
With old Linkd it was possible to group nodes in packages and enable
protocol per group of nodes which is currently not possible in Enhanced
Linkd [1]. The configuration about protocols is global for all devices in
your OpenNMS inventory. Additionally, there is no way how to visual
differentiate OSFP from CDP links.
IMHO when you want useful information use
* just OSPF for visualising a OSPF routing network
* just ISIS for visualising a IS-IS routing network
* just use *one* of the three mechanisms for visualising a Layer 2 network
What link discovery protocols are support on your IPInfusion's OcNOS
devices? In the documentation[2] you find the OIDs are used to build the
links for each of the protocols. Check your devices if they support them.
[1] https://issues.opennms.org/browse/NMS-8818
[2] http://docs.opennms.org/opennms/releases/20.0.0/guide-
admin/guide-admin.html#ga-enlinkd-daemon
Hi Team,
OpenNMS is unable to show links in topology. OSPF & LLDP are enabled on
all devices. OSPF adjacency is established b/w some of our devices. LLDP
neighborship is also formed among all as per our topology. LLDP and OSPF
mibs are successfully compiled in OpenNMS.
We are using IPInfusion's OcNOS devices and Cisco routers in our topology.
Links of Cisco nodes are detected but not of OcNOS.
We are running OpenNMS 20.0.0 on Kali Linux. EnhanceLinkd is UP and running.
Any inputs will be highly appreciated.
OpenNMS.Eventd : running
OpenNMS.Alarmd : running
OpenNMS.Bsmd : running
OpenNMS.Ticketer : running
OpenNMS.Trapd : running
OpenNMS.Queued : running
OpenNMS.Actiond : running
OpenNMS.Notifd : running
OpenNMS.Scriptd : running
OpenNMS.Rtcd : running
OpenNMS.Pollerd : running
OpenNMS.PollerBackEnd : running
*OpenNMS.EnhancedLinkd : running*
OpenNMS.Collectd : running
OpenNMS.Discovery : running
OpenNMS.Vacuumd : running
OpenNMS.EventTranslator: running
OpenNMS.PassiveStatusd : running
OpenNMS.Statsd : running
OpenNMS.Provisiond : running
OpenNMS.Reportd : running
OpenNMS.Ackd : running
OpenNMS.JettyServer : running
opennms is running
But it shows some warning logs in enlinkd.log
getReadyRunnable: queue is Empty
getReadyRunnable: queue is Empty
getReadyRunnable: queue is Empty
getReadyRunnable: queue is Empty
getReadyRunnable: queue is Empty
getReadyRunnable: queue is Empty
getReadyRunnable: queue is Empty
getReadyRunnable: queue is Empty
getReadyRunnable: queue is Empty
getReadyRunnable: queue is Empty
<?xml version="1.0" encoding="ISO-8859-1"?>
<enlinkd-configuration threads="5"
initial_sleep_time="60000"
rescan_interval="86400000"
use-cdp-discovery="true"
use-bridge-discovery="true"
use-lldp-discovery="true"
use-ospf-discovery="true"
use-isis-discovery="true"
/>
Below are my OpenNMS, Java & PostgreSQL details.
Version: 20.0.0
Server Time: Mon Jun 26 13:57:02 IST 2017
Client Time: Mon Jun 26 2017 13:57:14 GMT+0530 (India Standard Time)
Java Version: 1.8.0_131 (Oracle Corporation)
Java Runtime: OpenJDK Runtime Environment (1.8.0_131-8u131-b11-2-b11)
Java Specification: Java Platform API Specification (Oracle Corporation,
1.8)
Java Virtual Machine: OpenJDK Server VM (Oracle Corporation, 25.131-b11)
Java Virtual Machine Specification: Java Virtual Machine Specification
(Oracle Corporation, 1.8)
Operating System: Linux 4.9.0-kali4-686-pae (i386)
Servlet Container: jetty/9.4.0.v20161208 (Servlet Spec 3.1)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Database Type: PostgreSQL
Database Version: 9.6.3
Time-Series Strategy: RRDTool or JRobin
--
*Thanks & Regards,Udaykumar*
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
_________________________________________
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-discuss mailing list
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-discuss mailing list
https://lists.sourceforge.net/lists/listinfo/opennms-discuss