13 Posts
0
6890
SSH timeout on PowerConnect 5548
Starting with firmware version 4.1.0.21 and continuing to the newest version released this week, v4.1.0.22, I am logged out of the SSH session to my PowerConnect 5548 after one hour of inactivity.
% ssh switch; date switch# show bootvar Unit Image Filename Version Date Status ---- ----- --------- --------- --------------------- ----------- 1 1 image-1 4.1.0.21 06-Dec-2017 16:17:06 Not active 1 2 image-2 4.1.0.22 17-May-2018 19:17:44 Active* "*" designates that the image was selected for the next boot switch# show version Unit SW version Boot version HW version ------------------- ------------------- ------------------- ------------------- 1 4.1.0.22 1.0.0.14 00.00.02 switch# show line ssh SSH configuration: Interactive timeout: Disabled History: 10 switch# show clock 12:14:34 EDT(UTC-4) Jun 19 2018 Time source is sntp switch# packet_write_wait: Connection to 192.168.2.X: Broken pipe Tue Jun 19 13:14:35 EDT 2018 # date/time printed by the shell after ssh ends
Notice that an hour after I typed the show clock command, I am disconnected. Is there a configuration change I can make so I stay logged in, or is this a bug? If it's a bug, how can I get a bug report submitted so it can be addressed in the next release?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
1
July 19th, 2018 12:00
I had good luck with simply setting the terminal software to send keepalive every 30 seconds.
1 Attachment
putty keepalive.png
vt1012
212 Posts
1
June 20th, 2018 09:00
Hi Joel,
You should be able to use the following for SSH, telnet, and console:
console(config)# line console
console(config-line)# exec-timeout 0
Specify either the number of minutes (up to 65535, equivalent to 45 days), or use zero (0) for no timeout.
It seems counter-intuitive, but using the "no" command below will timeout with the default timing.
console(config-line)# no exec-timeout
If the "zero" command doesn't work, try setting it to the maximum minutes or anything beyond a couple of hours and see if that also times out too soon.
Hope this helps.
Joel_McClung
13 Posts
0
June 21st, 2018 19:00
Joel_McClung
13 Posts
0
June 26th, 2018 17:00
I also set the exec-timeout to 65535 to see if that had any effect.
It did not have any effect; I was still logged out of the switch after 1 hour. As an experiment, I changed it to 2 minutes and I was indeed logged out after 2 minutes, but the connection was closed in a different manner. See the close statement at the bottom? It is different from the one above.
versus the other close message: And, just to make sure, I set my SSH session to have the KeepAlive value to "yes", but was still logged out after an hour.Joel_McClung
13 Posts
0
June 27th, 2018 14:00
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 28th, 2018 12:00
Thanks for bringing this to our attention. I found a 5500 in our lab and currently have an SSH connection to it. I will do some further testing to see if I can reproduce these results. I will chime back in with my findings.
Joel_McClung
13 Posts
0
July 20th, 2018 15:00
Thank you for the information. Based on your feedback I did more research and found that I did not set the KeepAlive parameter properly in my SSH config file. I changed ~/.ssh/config (Linux host) to:
and that worked. I am no longer logged out of the switch unless I explicitly close the connection. Thank you again for your help.