[c-nsp] SSH no longer functions after hostname change

[Paul Stewart]

Normally all we do is a "crypto key gen rsa" if a hostname changes and we
continue on... this regens the keys and stops/starts the SSH process....

Paul



-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jon Wolberg
Sent: Monday, August 10, 2009 11:53 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] SSH no longer functions after hostname change

Hello-

We recently changed some of our hostnames on various legacy switches to
follow our naming convention, and after one change I can no longer SSH to
the switch.

I get the below errors on the console with debug ip ssh client running:

Aug 10 11:23:44 EST: SSH5: sent protocol version id SSH-2.0-Cisco-1.25
Aug 10 11:23:44 EST: SSH5: protocol version id is - SSH-2.0-OpenSSH_4.3
Aug 10 11:23:44 EST: SSH2 5: RSA_sign: private key not found
Aug 10 11:23:44 EST: SSH2 5: signature creation failed, status -1
Aug 10 11:23:44 EST: SSH5: Session disconnected - error 0x00

I zero'ized the old keys and re-generated as well as set the hostname back
to the original and zero'ized and re-generated to no avail.  Nothing shows
up on Google and I can find no errata related to SSH access on the version
of code we are running.

Has anyone encountered this before?  This is a 3750 running 12.2(44)SE2


Jon Wolberg
Systems Engineer
Virtacore Systems Inc.
"We Virtualize IT!"
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/