Is there any hint how to unlock this deadlock in Device Discovering. Every Time I want to start a Device Discover Job manually (immediately) I get:
" An instance of discovery is running already. Please try to start once it gets completed. "
If I want to debug the problem, the ngdiscovery.log keeps empty.
If I order the Jobs after job-type in the Job-browser, I will see the only Jobs devices has been discovered was "Peridic Jobs" and all immediatly Jobs found 0 devices or crashed with " An instance of discovery is running already ...". Knowing that during the whoole history of Job-browser we did many reboots, I can imagine that a new reboot will not improve the situation.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...