While I can not explain the details of the messages, it is very clear that there is some type of error (probably a software issue more likely than a hardware issue). This relates to the part that says "Unexpected internal error" and to the presence of traceback information. In my experience traceback is always related to a software issue.
Is this perhaps a transient (temporary) problem and after a while SSH worked again? Or is the problem continuing?
As a workaround it might help to reload the router. That might restore normal function for SSH. I believe that a longer term solution will involve upgrading to different code. If the router is covered by a maintenance contract it would be good to open a TAC case on this and get a more authoritative explanation than I am able to give.
Yes, that was the solution, you check with the command (show process blocked) if you find (devc-vty) for various time, they can be ssh or telnet sessiones who remained hung. So you apply the (process restart devc-vty) command to unlock the process.
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...