cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
1514
Views
0
Helpful
3
Replies

after power failure SSH does not work

Jozef Staruch
Level 1
Level 1

Hi all,

We had power failure catalyst 6509 and after the device boot up ssh does not work any more 

below is error messages

Any ideas?

thank you

line con 0

access-class 90 out

logging synchronous

line vty 0 4

access-class 90 in

exec-timeout 60 0

logging synchronous

transport input telnet

transport input ssh

transport output telnet

line vty 5 15

access-class 90 in

exec-timeout 60 0

logging synchronous

transport input ssh

transport output ssh

! line con 0
access-class 90 out
logging synchronous
!

------------------ show version ------------------

Cisco IOS Software, s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(33)SXI3, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Tue 27-Oct-09 11:11 by prod_rel_team

ROM: System Bootstrap, Version 12.2(17r)SX5, RELEASE SOFTWARE (fc1)

G-L-L0.10-1-CS01 uptime is 1 week, 21 hours, 17 minutes
Uptime for this control processor is 1 week, 21 hours, 14 minutes
Time since G-L-L0.10-1-CS01 switched to active is 1 week, 21 hours, 13 minutes
System returned to ROM by  power cycle at 16:55:08 MESZ Fri May 14 2010 (SP by power on)
System restarted at 12:28:15 UTC Tue Nov 20 2012
System image file is "sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXI3.bin"
Last reload reason: Reason unspecified

cisco WS-C6509-E (R7000) processor (revision 1.4) with 458720K/65536K bytes of memory.

         

error messages in log:

Nov 27 20:01:09.364 UTC: SSH2 6: RSA_sign: private key not found

Nov 27 20:01:09.364 UTC: SSH2 6: signature creation failed, status -1

Nov 27 20:01:10.060 UTC: SSH2 5: RSA_sign: private key not found

Nov 27 20:01:10.060 UTC: SSH2 5: signature creation failed, status -1

Nov 27 20:01:10.692 UTC: SSH2 5: RSA_sign: private key not found

Nov 27 20:01:10.692 UTC: SSH2 5: signature creation failed, status -1

3 Replies 3

glen.grant
VIP Alumni
VIP Alumni

Try zeroizing then recreating the crypto key and see what happens .  Possibly the key got corrupted or blown away with the power outage.

Thank you ,

do you think following command would be enough?

crypto key zeroize rsa

(make changes)

crypto key generate rsa

(verify ssh then remove telnet) ?

  Yes , that would be the first thing I try .

Review Cisco Networking for a $25 gift card