If this is the same with the Console, then most likely the router is overwhelmed, maybe due to debugs left running on it or traffic is over capacity.
If you were to yank a connection (outside) for e.g. and try to telnet / console back in, and if it allows you to do so, then its probably due to overcapacity traffic (DoS??) OR if you don't want the excersize to be intrusive, have a sniffer on the outside and then on the inside connections and see if the traffic is unduly high or inappropriate.
Reboot would be the last resort. But at least doing the above would give us a clue as to whats going on.
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...