ssh user not getting logged out even when the exec timeout expiry on Cisco 3850

[Abheesh Kumar]

Hi All,

I am facing an issue in Cisco 3850 switch running version 03.07.02E, ssh users are not getting logged out even when the exec timeout expiry. Exec time out is set as 5 min.

I just console into switch and checked but after that console is also on hang state unable to enter any commands. If any one face this kind of issues or any help will be much appreciated.

XXX#sh users
Line User Host(s) Idle Location
* 0 con 0 XXX idle 00:00:00
2 vty 0 ciscoprime idle 2d06h 172.20.16.22
3 vty 1 ciscoprime idle 2d06h 172.20.16.22
4 vty 2 ciscoprime idle 1d12h 172.20.16.22
5 vty 3 ciscoprime idle 1d12h 172.20.16.22
6 vty 4 ciscoprime idle 1d12h 172.20.16.22
7 vty 5 ciscoprime idle 1d12h 172.20.16.22
8 vty 6 ciscoprime idle 1d12h 172.20.16.22
9 vty 7 ciscoprime idle 1d12h 172.20.16.22
10 vty 8 ciscoprime idle 1d12h 172.20.16.22
11 vty 9 ciscoprime idle 1d12h 172.20.16.22
12 vty 10 ciscoprime idle 1d12h 172.20.16.22
13 vty 11 ciscoprime idle 1d12h 172.20.16.22
14 vty 12 ciscoprime idle 1d12h 172.20.16.22
15 vty 13 ciscoprime idle 1d12h 172.20.16.22
16 vty 14 ciscoprime idle 1d12h 172.20.16.22
17 vty 15 ciscoprime idle 1d12h 172.20.16.22

Interface User Mode Idle Peer Address

XXX#

HTH

Abheesh

[Seb Rupik · Accepted solution]

Hi there,

Ah Prime doing what it does best!! I saw something similar on a N7K.

Looks like this bug covers it:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuv84149

...since this release has been deferred try upgrading to a recommended release, eg: 3.6.8 or 16.3.6

cheers,

Seb.

[Georg Pauwen · Accepted solution]

Hello,

you might be hitting the bug below. Try and upgrade to 3.7.5.

Cat3850: All VTY lines hung by SSH sessions initiated by Prime Infra
CSCuv84149
Description
Symptom:
In Catalyst 3850 switch/stack, all VTY sessions are hung by SSH sessions initiated by Cisco Prime.

513E.B.07-3800-14#sh users
Line User Host(s) Idle Location
* 0 con 0 idle 00:00:00
4 vty 2 cisco2 idle 00:09:47 10.201.255.176
5 vty 3 cisco3 idle 00:09:25 10.201.255.176
6 vty 4 cisco4 idle 00:09:14 10.201.255.176
7 vty 5 cisco4 idle 00:08:50 10.201.255.176
8 vty 6 cisco5 idle 00:08:19 10.201.255.176
9 vty 7 cisco6 idle 00:08:02 10.201.255.176
10 vty 8 cisco6 idle 00:07:44 10.201.255.176
11 vty 9 cisco6 idle 00:07:30 10.201.255.176
12 vty 10 cisco7 idle 00:06:57 10.201.255.176
13 vty 11 cisco7 idle 00:06:42 10.201.255.176
14 vty 12 cisco8 idle 00:06:24 10.201.255.176
15 vty 13 cisco8 idle 00:06:02 10.201.255.176
16 vty 14 cisco3 idle 00:05:46 10.201.255.176
17 vty 15 cisco5 idle 00:05:32 10.201.255.176

"clear line vty " and "clear tcp tcb" commands do not clear the hung sessions.

Conditions:
Issue is seen in Catalyst 3850 running 3.7.1 release.

Workaround:
Reloading the switch/stack is a temporary solution and issue may reoccur.

Issue has not reoccurred after upgrading C3850 to 3.7.2.