1-13
Cisco ASA Series CLI Configuration Guide
Chapter 1 Configuring Active/Active Failover
Configuring Active/Active Failover
Configuring Optional Active/Active Failover Settings
The following optional Active/Active failover settings can be configured when you are initially
configuring failover or after you have already established failover. Unless otherwise noted, the
commands should be entered on the unit that has failover group 1 in the active state.
This section includes the following topics:
• Configuring Failover Group Preemption, page 1-13
• Enabling HTTP Replication with Stateful Failover, page 1-15
• Disabling and Enabling Interface Monitoring, page 1-15
• Configuring Interface Health Monitoring, page 1-16
• Configuring Failover Criteria, page 1-17
• Configuring Virtual MAC Addresses, page 1-17
• Configuring Support for Asymmetrically Routed Packets, page 1-19
Configuring Failover Group Preemption
Assigning a primary or secondary priority to a failover group specifies which unit the failover group
becomes active on when both units boot simultaneously. However, if one unit boots before the other, then
both failover groups become active on that unit. When the other unit comes online, any failover groups
that have the unit as a priority do not become active on that unit unless manually forced over, unless a
Step 4
failover lan unit secondary
Example:
hostname(config)# failover lan unit
secondary
(Optional) Designates this unit as the secondary unit:
Note This step is optional because, by default, units are
designated as secondary unless previously configured.
Step 5
failover
Example:
hostname(config)# failover
Enables failover.
After you enable failover, the active unit sends the configuration
in running memory to the standby unit. As the configuration
synchronizes, the messages “Beginning configuration replication:
Sending to mate” and “End Configuration Replication to mate”
appear on the active unit console.
Step 6
copy running-config startup-config
Example:
hostname(config)# copy running-config
startup-config
Saves the configuration to flash memory.
Enter the command after the running configuration has completed
replication.
Step 7
no failover active group group_id
Example:
hostname(config)# no failover active group
1
If necessary, force any failover group that is active on the primary
to the active state on the secondary unit. To force a failover group
to become active on the secondary unit, enter this command in the
system execution space on the primary unit.
The group_id argument specifies the group you want to become
active on the secondary unit.
Command Purpose
To Next Page
Loading...
Need help?
General
