I'm new to the ACE modul and trying to set up some szenarios and i run already into some troubles.
I configured redundancy to another module - virtulised mode. Config sync between the context worked fine. If i change s'thing in the activ context it was copied to the standby context. But if i changed something in the active Admin context it was not copied to the standby Admin context.
FT Switchover in the Admin context is not possible returns the following fault:
ACE_Switch08/Admin# ft switchover
This command will cause card to switchover (yes/no)? [no] yes
Invalid FT group. FT switchover command will be ignored.
If I switch a single FT group it works. But how is it possible to switch all FT groups a the same time? Do i have to switch each context by itself?
After i have switched the active context to the standby context, the ft group x command shows both peers as active. After i take the standby ft group no inservice and back inservice it shows correctly Active and standby_HOT.
boot system image:c6ace-t1k9-mz.3.0.0_A1_4a.bin
limit-resource all minimum 10.00 maximum equal-to-min
class-map type management match-any REMOTE_ACCESS
description -- Remote Access traffic match --
2 match protocol telnet any
3 match protocol ssh any
4 match protocol icmp any
policy-map type management first-match REMOTE_MGMT_ALLOW_POLICY
for my config i just put the "user" or "backend" contexts into ft groups. I don't sync the admin contexts on both aces. I am not even sure if that makes sense or is "best practicse".
So if you don't put the admin context into an extra ft group it won't be synced. you have to configure the admin contexts on each physical ace separately.
Putting the contexts sf0-2200 & sf0-2220 into an ft group and not having an ft group for admin is the way to go IMHO.
If you do a switchover you always have to specify which context you want to switchover. I don't think that you can actually switchover a whole bunch of contexts with this command. If you want to do that a reload is the only way AFAIK.
ft switchover 1
ft switchover 2
This could be because you have not configured the other ACE's admin context to participate in the ft properly.
Thanks for your replay. We solved the problem earlier that day and it was exactly as you described. Sadly the documents on CCO from Cisco doesn't mention the fact, that the admin has also to be in a ft group.
And whats even worse, that you cannot switch all ft groups together... we have 50 context in our serverfarm... will be a lot of work if i have to switch them all -> reboot could be the solution, but a bad one....
So you have the admin group in an ft group now and sync the configs between both?
In my opinion you might encounter some problems because the second ace needs some "unique" configuration settings like ip address and other stuff which will probably get overwritten by a sync.
I tried the "admin context in a ft group" approach with an earlier A2 release of the ACE and always ran into this problem. Afterwards i never bothered with it again. Anyhow good to hear you solved your issues.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...