08-23-2011 07:32 PM
Hi,
Does anyone know of a document that details the steps to chenge the FT ip addresses of a pair of Cisco 4710 whilst they are running in a production environment without causing an outage?
Would the steps be:
On the secondary unit:
hbs-syd04-lb01
ft interface vlan 417
ip address 172.30.254.221 255.255.255.252
peer ip address 172.30.254.222 255.255.255.252
Then on the primary unit:
hbs-syd04-lb01
ft interface vlan 417
ip address 172.30.254.221 255.255.255.252
peer ip address 172.30.254.222 255.255.255.252
Or Vice Versa?
Thanks
Solved! Go to Solution.
08-24-2011 02:36 AM
To avoid any risk, i would proceed as following:
1/ Make sure that all contexts on primary have higher priority. Make sure preemption is enabled for all contexts.
2/ Isolate secondary ACE (eg shutdown ports on the switch). From that moment, both ACEs should be active
3/ Perform the config changes
4/ Restore connectivity with secondary ACE. Context on secondary should become FSM_FT_STATE_STANDBY_HOT
--Olivier
08-24-2011 02:36 AM
To avoid any risk, i would proceed as following:
1/ Make sure that all contexts on primary have higher priority. Make sure preemption is enabled for all contexts.
2/ Isolate secondary ACE (eg shutdown ports on the switch). From that moment, both ACEs should be active
3/ Perform the config changes
4/ Restore connectivity with secondary ACE. Context on secondary should become FSM_FT_STATE_STANDBY_HOT
--Olivier
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