SSH timeout on PowerConnect 5548

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.

The console line was set to 10 minutes for the timeout, but I changed it just in case. It didn't work. I still got logged out one hour later.

switch# show line
Console configuration:
Interactive timeout:  10 minute(s)
History:  10
Baudrate:  9600
Databits: 8 
Parity: none 
Stopbits: 1 

Telnet configuration:
Telnet is disabled.
Interactive timeout:  10 minute(s) 
History:  10

SSH configuration:
Interactive timeout:  Disabled
History:  10
switch# conf t

switch(config)# line console
switch(config-line)# exec-timeout 0
switch(config-line)# exit
switch(config)# exit
switch# show line
Console configuration:
Interactive timeout:  Disabled
History:  10
Baudrate:  9600
Databits: 8 
Parity: none 
Stopbits: 1 

Telnet configuration:
Telnet is disabled.
Interactive timeout:  10 minute(s) 
History:  10

SSH configuration:
Interactive timeout:  Disabled
History:  10
switch# show clock 
 21:31:39 EDT(UTC-4)  Jun 21 2018
Time source is sntp
switch# packet_write_wait: Connection to 192.168.2.x: Broken pipe
Thu Jun 21 22:31:40 EDT 2018

I still think this is a bug.

I also set the exec-timeout to 65535 to see if that had any effect.

switch(config)# line ssh
switch(config-line)# exec-timeout 65535
switch(config-line)# exit
switch(config)# exit
switch# show clock
 18:32:47 EDT(UTC-4)  Jun 26 2018
Time source is sntp
switch# packet_write_wait: Connection to 192.168.2.X: Broken pipe
Tue Jun 26 19:32:48 EDT 2018

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.

switch(config)# line ssh
switch(config-line)# exec-timeout 2
switch(config-line)# exit
switch(config)# exit
switch# show clock 
 20:26:33 EDT(UTC-4)  Jun 26 2018
Time source is sntp
switch# Connection to switch closed.
Tue Jun 26 20:28:33 EDT 2018

versus the other close message:

switch# packet_write_wait: Connection to 192.168.2.X: Broken pipe

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.

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.

 

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:

Host switch
     ServerAliveInterval 60

and that worked. I am no longer logged out of the switch unless I explicitly close the connection. Thank you again for your help.