This could be a bug with a loop or deadlock in the ConfigMgmtServer process. There is at least one outstanding bug, CSCsm50949, which affects RME 4.0.6 and 4.1.1. It can occur if there are any 1900 or 2820 series switches in the network which are not running Enterprise code.
Troubleshooting these problems can be tricky. One might get lucky, and see obvious errors either in the dcmaservice.log or the ConfigMgmtServer.log (Windows) or daemons.log (Solaris) which point to the problem. But often times, the true cause of the problem is not seen without a full thread dump from ConfigMgmtServer when the problem is occurring. This is easy to do on Solaris (just run kill -QUIT against the PID of ConfigMgmtServer). However, on Windows it requires one to run ConfigMgmtServer manually outside of dmgtd. Therefore, it's advisable to open a TAC services request and have them step through the procedure.
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...