In Cisco ACE the redundancy feature provides seamless switchover in case an ACE becomes unresponsive or a critical host or interface fails. ACE has robust software and hardware that makes it possible to handle high volume of traffic at real time. Cisco ACE supports virtualized architecture to increase datacenter scalability. Two ACEs, properly configured, form a failover pair. Each appliance can contain one or more fault-tolerant (FT) groups. Each FT group consists of one active context and one standby context. Each FT group acts as an independent redundancy instance. When a switchover occurs, the active member in the FT group becomes the standby member and the original standby member becomes the active member. To achieve active-active redundancy, a minimum of two contexts and two FT groups are required on each ACE.
A failed ACE appliance is required to be replaced. The configuration should be preserved and the primary switchover need to happen.
Stateful Failover and Config sync
Cisco ACE replicates flows on the active FT group member to the standby group member per connection for each context. The replicated flows contain all the flow-state information necessary for the standby member to take over the flow if the active member becomes unresponsive. Note that ACE does not support the stateful failover of any connections that are proxied. Such connections include Layer 7 connections (including SSL), inspection, and HTTP compression.
Redundancy uses a dedicated FT VLAN between redundant ACEs to transmit flow-state information and the redundancy heartbeat. You must configure this same VLAN on both peer ACEs. You also must configure a different IP address within the same subnet on each ACE for the FT VLAN.
The ACE automatically replicates the active configuration on the standby member during config sync. This process automatically replicates any changes in the configuration from active to standby peer.
Follow these steps to swap the failed device and get it back in sync with the primary:
a) Complete all the physical network connectivity.
b) Disable config auto-sync in the primary ACE.
c) Configure the management Vlan for basic network connectivity.
d) Make sure the new device has the same code as the primary; if not you'll need to upgrade it.
e) Install the license (if used).
f) Copy all the SSL files stored in the primary APP. (If any)
g) Copy the scripted keepalives (If any)
h) Configure the FT interface Vlan, FT peer, FT group for the Admin context. (Be careful about the priority you assign).
i) Re-enable config auto-sync on the primary APP in order to replicate the config to the standby.
Hi all,[Edit: I've just figured out that attributesnapshot.alwaysAllowNative=TRUE. as referred to in the release notes really SHOULD be attribute snapshot.alwaysAllowNative=TRUE- which makes much more sense, but I still have questions]I'm h...
Hi ACI board,I integrated a standby APIC into my fabric.When using the command "show controller" on a APIC within my fabric, the standby APIC is listed in the output with the status "data-layer-partially-diverged".Is this the normal behavior? Can anybody ...
Hi ACI professionals,I added a standby APIC to my fabric (which worked like a charm).When checking the context menu of the standby APIC in the GUI (Controllers > APIC > Cluster as Seen by Node > Standby APIC) I can see the options "Accept Control...