Unsolved
This post is more than 5 years old
4 Posts
0
33231
May 29th, 2009 04:00
PowerConnect 5324 close telnet session
Hello,
First of all, excuse me for my english.
I have a problem with my PowerConnect 5324.
I have too many opened telnet session and I can not open a new telnet connection.
I can connect with the console port and serial cable.
I can see the telnet session with this command line :
SW-1-C#show user
Username Protocol Location
--------------- ------------ -----------------------
Serial 0.0.0.0
administrateur HTTP 172.16.0.246
administrateur HTTP 172.16.0.246
administrateur Telnet 172.16.0.246
administrateur Telnet 172.16.0.246
administrateur Telnet 172.16.0.246
administrateur Telnet 172.16.0.246
SW-1-C#show session
Connection Host Address Port Byte
----------- ---------------------------- ------------------- ------ ------
What is the command line for logout the telnet session?
Thanks for your help!


bh1633
909 Posts
0
May 29th, 2009 05:00
What firmware are you running? Some PowerConnect switches had this issue, but running the latest firmware fixed it.
taarka
4 Posts
0
May 29th, 2009 06:00
SW version 1.0.0.45 ( date 07-Jun-2004 time 14:34:51 )
Boot version 1.0.0.21 ( date 10-Aug-2004 time 13:33:06 )
HW version 00.00.02
:emotion-6:
taarka
4 Posts
0
May 29th, 2009 06:00
Thanks for your help.
After update what is the command line for logout telnet session ?
bh1633
909 Posts
0
May 29th, 2009 06:00
http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R183225&SystemID=PWC_5324&servicetag=&os=WNET&osl=en&deviceid=7994&devlib=0&typecnt=0&vercnt=5&catid=-1&impid=-1&formatcnt=2&libid=5&fileid=250308
The link above is to the latest firmware. Update your firmware AND the bootcode and this issue should go away. Be sure and update the bootcode also.
taarka
4 Posts
0
May 29th, 2009 08:00
OK thanks
bh1633
909 Posts
0
May 29th, 2009 08:00
The latest firmware will not have the issue. There is no command for logging out telnet sessions.
Be sure and upgrade the bootcode at the same time. If you do not, you will have to use XMODEM from the bootcode to get your system working again.
- update firmware
- update bootcode
- set bootvar to use new firmware
- reload