Jun 28, 2007 Make sure you have specified a host name and domain. Then use the crypto key generate rsa command to generate an RSA key pair and enable the SSH server. When you configure the RSA key pair, you might encounter these error messages: No hostname specified. You must configure a host name for the router using the hostname global configuration command. Jun 11, 2019 SW1 ( config)# crypto key generate rsa. How many bits in the modulus 512: 1024% Generating 1024 bit RSA keys, keys will be non-exportableOK Set the size of key to 1024 bits. If your Cisco Switch is running an older version of Cisco IOS image, then it is extremely recommended that you upgrade to latest Cisco IOS.
This document gives step-by-step instructions to configure Secure Shell (SSH) Version 1 on Catalyst switches running Catalyst OS (CatOS). The version tested is cat6000-supk9.6-1-1c.bin.
This table shows the status of SSH support in the switches. Registered users can access these software images by visiting the Software Center.
I found a notable exception that in Windows 10, using the described route only wrote the files to the folder if the file names where not specified in the ssh-keygen generator. Giving a custom key name caused the files containing the RSA public and private keys not to be written to the folder. Open the windows command line; Type ssh-keygen. Windows 10 generate ssh key powershell download.
CatOS SSH | |
---|---|
Device | SSH Support |
Cat 4000/4500/2948G/2980G (CatOS) | K9 images as of 6.1 |
Cat 5000/5500 (CatOS) | K9 images as of 6.1 |
Cat 6000/6500 (CatOS) | K9 images as of 6.1 |
IOS SSH | |
Device | SSH Support |
Cat 2950* | 12.1(12c)EA1 and later |
Cat 3550* | 12.1(11)EA1 and later |
Cat 4000/4500 (Integrated Cisco IOS Software)* | 12.1(13)EW and later ** |
Cat 6000/5500 (Integrated Cisco IOS Software)* | 12.1(11b)E and later |
Cat 8540/8510 | 12.1(12c)EY and later, 12.1(14)E1 and later |
No SSH | |
Device | SSH Support |
Cat 1900 | no |
Cat 2800 | no |
Cat 2948G-L3 | no |
Cat 2900XL | no |
Cat 3500XL | no |
Cat 4840G-L3 | no |
Cat 4908G-L3 | no |
* Configuration is covered in Configuring Secure Shell on Routers and Switches Running Cisco IOS.
** There is no support for SSH in 12.1E train for Catalyst 4000 running Integrated Cisco IOS Software.
Refer to Encryption Software Export Distribution Authorization Form in order to apply for 3DES.
This document assumes that authentication works prior to implementation of SSH (through the Telnet password, TACACS+) or RADIUS. SSH with Kerberos is not supported prior to the implementation of SSH.
This document addresses only the Catalyst 2948G, Catalyst 2980G, Catalyst 4000/4500 series, Catalyst 5000/5500 series, and Catalyst 6000/6500 series running the CatOS K9 image. For more details, refer to the Requirements section of this document.
The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.
For more information on document conventions, see the Cisco Technical Tips Conventions.
In some situations it may be neccessary to disable SSH on the switch. You must verify whether SSH is configured on the switch and if so, disable it.
To verify if SSH has been configured on the switch, issue the show crypto key command. If the output displays the RSA key, then SSH has been configured and enabled on the switch. An example is shown here.
To remove the crypto key, issue the clear crypto key rsa command to disable SSH on the switch. An example is shown here.
To turn on debugs, issue the set trace ssh 4 command.
To turn off debugs, issue the set trace ssh 0 command.
This section deals with different troubleshooting scenarios related to SSH configuration on Cisco switches.
Problem:
Cannot connect to the switch using SSH.
The debug ip ssh command shows this output:
Solution:
This problem occurs because of either of these reasons:
New SSH connections fail after changing the hostname.
SSH configured with non-labeled keys (having the router FQDN). Openssl generate private key.
The workarounds for this problem are:
If the hostname was changed and SSH is no longer working, then zeroize the new key and create another new key with the proper label.
Do not use anonymous RSA keys (named after the FQDN of the switch). Use labeled keys instead.
In order to resolve this problem forever, upgrade the IOS software to any of the versions in which this problem is fixed.
A bug has been filed about this issue. For more information, refer to Cisco bug ID CSCtc41114 (registered customers only) .