Browse Community
Help
Log In
Responses(3)
Solutions(0)
R_Heibel
4 Posts
0
October 12th, 2015 13:00
output from #show ip ssh
SSH Server enabled. Port: 22
Protocol Levels: Versions 1 and 2.
SSH Connections Currently in Use: ............. 0
Maximum number of SSH Sessions Allowed: ....... 5
SSH Session Timeout: .......................... 600
RSA key was generated.
DSA key was generated.
SSH Public Key Authentication is enabled.
Active Incoming Sessions.
Ip Address User Name Idle Time Session Time
--------------- --------------- ------------ ------------
when i try to run (config)#no crypto key generate dsa i get
#no crypto key generate dsa
^
% Invalid input detected at '^' marker.
same with rsa
through http i could disable ssh then delete the dsa and rsa key. port 22 is not allowed only 1025+ but even set to 1777 i get the same behavior.
October 13th, 2015 06:00
will report back once i have worked through the list.
p.s we have a second stack that will be upgraded tonight(poe phone fix needed) It will be interesting to see if we get the same issue.
1
October 14th, 2015 02:00
Stack's 8 and 7 updated without issue last night so I downgraded and re-updated stack 1 and now SSH work's fine. Will put it down to some glitch.
Thanks Daniel C for the time you have spent on this issue.
Dell Support Resources
View All
Top
R_Heibel
4 Posts
0
October 12th, 2015 13:00
output from #show ip ssh
SSH Server enabled. Port: 22
Protocol Levels: Versions 1 and 2.
SSH Connections Currently in Use: ............. 0
Maximum number of SSH Sessions Allowed: ....... 5
SSH Session Timeout: .......................... 600
RSA key was generated.
DSA key was generated.
SSH Public Key Authentication is enabled.
Active Incoming Sessions.
Ip Address User Name Idle Time Session Time
--------------- --------------- ------------ ------------
when i try to run (config)#no crypto key generate dsa i get
#no crypto key generate dsa
^
% Invalid input detected at '^' marker.
same with rsa
through http i could disable ssh then delete the dsa and rsa key. port 22 is not allowed only 1025+ but even set to 1777 i get the same behavior.
R_Heibel
4 Posts
0
October 13th, 2015 06:00
will report back once i have worked through the list.
p.s we have a second stack that will be upgraded tonight(poe phone fix needed) It will be interesting to see if we get the same issue.
R_Heibel
4 Posts
1
October 14th, 2015 02:00
Stack's 8 and 7 updated without issue last night so I downgraded and re-updated stack 1 and now SSH work's fine. Will put it down to some glitch.
Thanks Daniel C for the time you have spent on this issue.