Header Only - DO NOT REMOVE - Extreme Networks

Cannot Disconnect Telnet Session on S-Series , Firmware 7.71.02.0005


The current equipment has four users Telnet landing, one of which is the current user, the other three are unknown telnet users, but I can not use the disconnect command to play out the other three users, the equipment is S series switches, the version is 7.71.02.0005 , How can I clear out other telnet sessions?

9 replies

Userlevel 7
# disconnect [i]

Ron wrote:

# disconnect [i]


thank you,but I have tried this method, but I can not clear the telnet session with the disconnect command,The disconnect command has no effect
Userlevel 4
Unfortunately , on older codes there have been rare situations where telnet sessions can become "locked" and do not release when using the disconnect command.

The only way to recover this on that firmware is to reset the blade.

i would recommend upgrading to version 8.42.04 as a minimum to take advantage of fixes which make this situation much less likely to occur and also this adds the ability to recover the situation without resetting the blade in the unlikely event that it should happen again.

This article describes the fix:

https://gtacknowledge.extremenetworks.com/articles/Solution/S-Series-Telnet-SSH-connections-for-mana...

Best Regards
Glyn
Straw, Glyn wrote:

Unfortunately , on older codes there have been rare situations where telnet sessions can become "locked" and do not release when using the disconnect command.

The only way to recover this on that firmware is to reset the blade.

i would recommend upgrading to version 8.42.04 as a minimum to take advantage of fixes which make this situation much less likely to occur and also this adds the ability to recover the situation without resetting the blade in the unlikely event that it should happen again.

This article describes the fix:

https://gtacknowledge.extremenetworks.com/articles/Solution/S-Series-Telnet-SSH-connections-for-mana...

Best Regards
Glyn


Thank you very much for your reply, thank you Glyn, but this switch is the IDC Core switches, Firmware can not do the upgrade and restart operation, otherwise it will affect the business, is there any other way to temporarily fix the fault code, clear the telnet session?
Straw, Glyn wrote:

Unfortunately , on older codes there have been rare situations where telnet sessions can become "locked" and do not release when using the disconnect command.

The only way to recover this on that firmware is to reset the blade.

i would recommend upgrading to version 8.42.04 as a minimum to take advantage of fixes which make this situation much less likely to occur and also this adds the ability to recover the situation without resetting the blade in the unlikely event that it should happen again.

This article describes the fix:

https://gtacknowledge.extremenetworks.com/articles/Solution/S-Series-Telnet-SSH-connections-for-mana...

Best Regards
Glyn

glyn,how to do reset the blade?and Can you give me your email me?i send you an email
Straw, Glyn wrote:

Unfortunately , on older codes there have been rare situations where telnet sessions can become "locked" and do not release when using the disconnect command.

The only way to recover this on that firmware is to reset the blade.

i would recommend upgrading to version 8.42.04 as a minimum to take advantage of fixes which make this situation much less likely to occur and also this adds the ability to recover the situation without resetting the blade in the unlikely event that it should happen again.

This article describes the fix:

https://gtacknowledge.extremenetworks.com/articles/Solution/S-Series-Telnet-SSH-connections-for-mana...

Best Regards
Glyn

Workaround:

Prior to version 8.42.04 the only workaround is to Reset the management blade

Hi Glyn,I did not understand,How to do reset the management blade ? Thanks
Userlevel 4
Straw, Glyn wrote:

Unfortunately , on older codes there have been rare situations where telnet sessions can become "locked" and do not release when using the disconnect command.

The only way to recover this on that firmware is to reset the blade.

i would recommend upgrading to version 8.42.04 as a minimum to take advantage of fixes which make this situation much less likely to occur and also this adds the ability to recover the situation without resetting the blade in the unlikely event that it should happen again.

This article describes the fix:

https://gtacknowledge.extremenetworks.com/articles/Solution/S-Series-Telnet-SSH-connections-for-mana...

Best Regards
Glyn

unfortunately the only way to workaround this issue on the older firmware is to reset the host master blade ( one with the cpu led lit )

this can be achieved using front panel button or by typing "reset x" where x is the module number of the host master blade. Dependent on connections this could cause some interruption.

Best Regards
Glyn
Straw, Glyn wrote:

Unfortunately , on older codes there have been rare situations where telnet sessions can become "locked" and do not release when using the disconnect command.

The only way to recover this on that firmware is to reset the blade.

i would recommend upgrading to version 8.42.04 as a minimum to take advantage of fixes which make this situation much less likely to occur and also this adds the ability to recover the situation without resetting the blade in the unlikely event that it should happen again.

This article describes the fix:

https://gtacknowledge.extremenetworks.com/articles/Solution/S-Series-Telnet-SSH-connections-for-mana...

Best Regards
Glyn

Thanks Glyn,Is it a reboot switch?
Userlevel 4
Straw, Glyn wrote:

Unfortunately , on older codes there have been rare situations where telnet sessions can become "locked" and do not release when using the disconnect command.

The only way to recover this on that firmware is to reset the blade.

i would recommend upgrading to version 8.42.04 as a minimum to take advantage of fixes which make this situation much less likely to occur and also this adds the ability to recover the situation without resetting the blade in the unlikely event that it should happen again.

This article describes the fix:

https://gtacknowledge.extremenetworks.com/articles/Solution/S-Series-Telnet-SSH-connections-for-mana...

Best Regards
Glyn

yes, it will reboot the blade , not the entire chassis. If there is only one blade installed then effectively its the whole switch

Reply