[opennms-discuss] OpenNMS shows Cisco links but not OcNOS in Topology

UdayKumar

2017-06-28 16:00:59 UTC

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

--
*Thanks & Regards,Udaykumar*