06-03-2014 04:35 AM
Hi,
I have two ACE 20's in two 6500's. I have an Admin context with a number of contexts. Unfortunately one context has the backup as FSM_FT_STATE_STANDBY_COLD not Standby_Hot.
I have checked its configuration and noticed a number of lines missing from the correct active context. I know now I have to force the config across by taking the ft-group out of service.
My question is do I do this on the working ACE or do it on both ACE's admin groups?
I think this is what I do.
config ft group X
no inservice
Give it a few mins to sync across to broken ACE and then put it back inservice?
Or do I need to do this on the broken ACE? I don't want to lose the good config and the broken config to copy across.
Solved! Go to Solution.
06-04-2014 08:57 AM
It went into cold state straight away. I went on active and did no ft-auto sync runn and then ft-auto sync runn. Unfortunately still getting the sticky error but a shorter one than last one.
sh ft config-error
Wed Jun 4 14:50:48 UTC 2014
`sticky ip-netmask 255.255.255.255 address source STICKY-SSL-****-FARM`
Error: sticky resource not available
--
`serverfarm ****-FARM`
Error(s) while applying config.
I have removed the stickyfarm and put in a test probe and it works fine. Very minute i put in sticky farm it breaks. How do you mean remove sticky group?
06-04-2014 09:26 AM
Hi Kanwalsi,
Just fixed it. resources not fully allocated on standby ace. Thanks for your help on this.
06-04-2014 09:37 AM
Hi Netter,
I thought you had already applied. But i am glad issue is resolved.
Regards,
Kanwal
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