10-06-2013 02:41 AM
Hi
I upgraded failover pair of ACE30 modules.
There is this steps in UPGRADE GUIDE
Step 8
Configure ACE-1 to autoboot from the latest ACE image. To set the boot variable and configuration register to1 (perform auto boot and use startup-config file), use the
boot system image:
and
config-register
commands in configuration mode. For example, enter:
ACE-1/Admin(config)# boot system image:c6ace-t1k9-mz.A5_2_0.bin
ACE-1/Admin(config)# config-register 1
ACE-1/Admin(config)# exit
ACE-1/Admin# show bootvar
BOOT variable = "image:c6ace-t1k9-mz.A5_2_0.bin"
Configuration register is 1
Step 9 On the standby ACE module (ACE-2), perform the following:
•Enter the show running-config command and ensure that all the changes made in the active ACE (ACE-1) are also reflected on the standby ACE.
•Enter the show bootvar command to verify that the boot variable was synchronized with ACE-1.
But my experience is that replication between Admin context does not work.
I must to change boot variable on both Admin contexts.
Is it OK?
Peter
Solved! Go to Solution.
10-08-2013 03:27 AM
I have ft group created for Admin context.
ft group 1
peer 1
priority 150
associate-context Admin
inservice
Petr
10-07-2013 06:12 AM
Hi Peter,
could you please provide output of "sh ft group brief" command?
Petr
10-07-2013 07:00 AM
acedc3-01/Admin# sh ft group brief
FT Group ID: 1 My State:FSM_FT_STATE_ACTIVE Peer State:FSM_FT_STATE_STANDBY_
HOT
Context Name: ssl-dc3-acc Context Id: 1
Running Cfg Sync Status:Running configuration sync has completed
FT Group ID: 2 My State:FSM_FT_STATE_ACTIVE Peer State:FSM_FT_STATE_STANDBY_
COLD
Context Name: ssl-dc3-app Context Id: 2
Running Cfg Sync Status:Peer in Cold State. Error on Standby dev
ice when applying configuration file replicated from active
FT Group ID: 3 My State:FSM_FT_STATE_ACTIVE Peer State:FSM_FT_STATE_STANDBY_
HOT
Context Name: ssl-dc3-dat Context Id: 3
Running Cfg Sync Status:Running configuration sync has completed
acedc3-01/Admin#
10-08-2013 03:27 AM
I have ft group created for Admin context.
ft group 1
peer 1
priority 150
associate-context Admin
inservice
Petr
10-07-2013 09:26 PM
Peter,
It should do it as described here:
What version do you run?
You need to make sure you have certs, keys, licenses, etc in the same way on both.
You can force the synchronization with:
host1/Admin(config)# no ft auto-sync running-config
host1/Admin(config)# no ft auto-sync startup-config
host1/Admin(config)# ft auto-sync running-config
host1/Admin(config)# ft auto-sync startup-config
Jorge
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