Cisco 500 Series, Configuration Manual

Page: 253 / 1140

14-33
Cisco Security Appliance Command Line Configuration Guide
OL-12172-03
Chapter 14 Configuring Failover
Configuring Failover
hostname(config)# 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 5 After the running configuration has completed replication, enter the following command to save the
configuration to Flash memory:
hostname(config)# copy running-config startup-config
Step 6
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 the following command in
the system execution space on the primary unit:
hostname# no failover active group group_id
The group_id argument specifies the group you want to become active on the secondary unit.
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 14-33
•
Enabling HTTP Replication with Stateful Failover, page 14-34
•
Disabling and Enabling Interface Monitoring, page 14-34
• Configuring Interface Health Monitoring, page 14-34
•
Configuring Failover Criteria, page 14-34
• Configuring Virtual MAC Addresses, page 14-35
•
Configuring Support for Asymmetrically Routed Packets, page 14-35
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, a failover
occurs, or the failover group is configured with the
preempt command. The preempt command causes
a failover group to become active on the designated unit automatically when that unit becomes available.
Enter the following commands to configure preemption for the specified failover group:
hostname(config)# failover group { 1 | 2 }
hostname(config-fover-group)# preempt [ delay ]
You can enter an optional delay value, which specifies the number of seconds the failover group remains
active on the current unit before automatically becoming active on the designated unit.