04-11-2004 04:23 PM - edited 03-02-2019 02:56 PM
IOS - Ver 12.2(14)SY1
ROM: System Bootstrap, Version 12.1(11r)E1, RELEASE SOFTWARE (fc1)
BOOTLDR: c6sup2_rp Software (c6sup2_rp-JK9SV-M), Version 12.2(14)SY1
___________________________________________________
Attempted to generate RSA key to use ssh and recieved following error message:[% Failed syncing (crypto key generate RSA)]. From that moment on, attempted to come out of config t and recieved follwing error: [Unable to sync config-changed command to standby]. Tried again to exit out of config t by using exit command and recieved:[Unable to sync config-exited command to standby.] Each time, the system will hang for 1 - 3 minutes and then show the error message. I can issue sh run and the speed is up normal but what is going on with syncing to the standby module? Also, one other warning:[Cannot display standby stack due to IPC error]. What is an IPC? I would prefer not to reload the system if possible. It appears that the system is running normally otherwise. Help will be appreciated.
Solved! Go to Solution.
04-18-2004 04:36 PM
We had few bugs for this issue. Here is one
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCed28202
The workaround is to reset the standby Supervisor engine. 122-17d.SXB which is now on CCO has a fix
Hope this helps
04-16-2004 06:22 AM
The reason for all the above error messages is your standby might not come up properly after the switch was reloaded. So, there is most probably communication break between Active and standby. So, please re-seat the standby and for your switch, it's hot-swappable for all devices except active supervisor. So, you can directly pull standby and re-seat perfectly.
04-16-2004 02:30 PM
Thanks for replying!
To begin with, prior to attempting to generate the RSA key, all previous changes were updating to the standby with no problems. It was only after the RSA attempt that any command that was issued showed sync problems.
The following is an output of the 6513 sh module - hope this helps in troubleshooting:
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 2 Catalyst 6000 supervisor 2 (Active) WS-X6K-SUP2-2GE SAL0711AG5U
2 2 Catalyst 6000 supervisor 2 (Standby) WS-X6K-SUP2-2GE SAL0711AA6D
3 16 16 port GE RJ45 WS-X6316-GE-TX SAD071301X7
4 16 16 port 1000mb GBIC ethernet WS-X6416-GBIC SAL0711A8K3
5 16 16 port 1000mb GBIC ethernet WS-X6416-GBIC SAL0711A8KQ
6 2 IPSec VPN Accelerator WS-SVC-IPSEC-1 SAD071801YS
9 48 48-port 10/100 mb RJ45 WS-X6148-RJ-45 SAL0710051W
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 0006.d65c.ab9c to 0006.d65c.ab9d 4.2 6.1(3) 7.5(0.94) Ok
2 0008.7dc9.1160 to 0008.7dc9.1161 4.2 6.1(3) 7.5(0.94) Ok
3 0002.7ee5.1420 to 0002.7ee5.142f 1.3 5.4(2) 7.5(0.94) Ok
4 000c.8515.c7d0 to 000c.8515.c7df 2.4 5.4(2) 7.5(0.94) Ok
5 000b.fdf1.8850 to 000b.fdf1.885f 2.4 5.4(2) 7.5(0.94) Ok
6 0003.feab.5d1a to 0003.feab.5d1d 1.2 7.2(1) 7.5(0.94) Ok
9 000c.30a3.ea30 to 000c.30a3.ea5f 1.1 5.4(2) 7.5(0.94) Ok
Mod Sub-Module Model Serial Hw Status
--- --------------------------- --------------- --------------- ------- -------
1 Policy Feature Card 2 WS-F6K-PFC2 SAL0712AGL6 3.3 Ok
1 Cat6k MSFC 2 daughterboard WS-F6K-MSFC2 SAL0705CFH6 2.5 Ok
2 Policy Feature Card 2 WS-F6K-PFC2 SAL0712AHLM 3.3 Ok
2 Cat6k MSFC 2 daughterboard WS-F6K-MSFC2 SAL0706CLFM 2.5 Ok
Mod Online Diag Status
--- -------------------
1 Pass
2 Pass
3 Pass
4 Pass
5 Pass
6 Pass
9 Pass
Wash_Metro#sh redun states
my state = 13 -ACTIVE
peer state = 8 -STANDBY HOT
Mode = Duplex
Unit = Primary
Unit ID = 1
Redundancy Mode (Operational) = Route Processor Redundancy Plus
Redundancy Mode (Configured) = Route Processor Redundancy Plus
Split Mode = Disabled
Manual Swact = Enabled
Communications = Up
client count = 11
client_notification_TMR = 30000 milliseconds
keep_alive TMR = 9000 milliseconds
keep_alive count = 1
keep_alive threshold = 18
RF debug mask = 0x0
tia - willfachi
04-18-2004 04:36 PM
We had few bugs for this issue. Here is one
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCed28202
The workaround is to reset the standby Supervisor engine. 122-17d.SXB which is now on CCO has a fix
Hope this helps
04-18-2004 08:26 PM
Thanks for the help - it is as we thought!
regards - willfachi
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide