Last time I kick off all of my available SSH session. The problem was quite large because I set up session in line vty 0 4 as : exec-timeout 0 0. Remember, don't do that:)
Sometimes when I drill new equipment I set up exec-timout like this because I do configuration for two or three days and It's anoying when ssh is kicking me off all the time. So I change config and problem beguins when I forget to change it.
I had to connect via console cable.
MPLS#sh ssh
Connection Version Mode Encryption Hmac State Username
1 2.0 IN aes256-cbc hmac-sha1 Session started user
1 2.0 OUT aes256-cbc hmac-sha1 Session started user
2 2.0 IN aes256-cbc hmac-sha1 Session started user
2 2.0 OUT aes256-cbc hmac-sha1 Session started user
3 2.0 IN aes256-cbc hmac-sha1 Session started user
3 2.0 OUT aes256-cbc hmac-sha1 Session started user
4 2.0 IN aes256-cbc hmac-sha1 Session started user
4 2.0 OUT aes256-cbc hmac-sha1 Session started user
%No SSHv1 server connections running.
In this case all you have to do is clear every single line.
clear line vty
In my router :
MPLS#clear line vty 3
[confirm]
[OK]
MPLS#clear line vty 4
[confirm]
[OK]
MPLS#sho ssh
Connection Version Mode Encryption Hmac State Username
2 2.0 IN aes256-cbc hmac-sha1 Session started user
2 2.0 OUT aes256-cbc hmac-sha1 Session started user
%No SSHv1 server connections running.
Lovely blogg you have