Académique Documents
Professionnel Documents
Culture Documents
connected to each other through a dedicated failover link and, optionally, a stateful
failover link. The health of the active interfaces and units is monitored to determine
if specific failover conditions are met. If those conditions are met, failover occurs. In
case of Active/active configuration both Units carry traffic. For creating active/active
Failover, configuring both ASA devices in Multiple context mode is required.
For ASA redundancy scenario the two devices must be the same models, must have
the same number and type of interfaces and the same license is required. ASA 5505
and 5510 do not support active/active failover without license upgrade.
For active/active configuration, Failover Contexts and Failover groups need to be
created. The Failover group is then applied to Primary or Secondary physical ASA unit.
After this, the particular Failover group is applied to a Context. For example, primary
unit is active ASA of Failover group1, but Secondary unit is Standby ASA of Failover
group1. If primary ASA is out of order, Secondary ASA will become Active of Failover
group1.
For explaining Active/Active Failover configuration in details, lets do the following
LAB.
Determine Failover and State interfaces. These two interfaces can be the same
physical interface if you dont need to consume one extra port. In our example here
we use two separate physical interfaces.
In this article, the failover (interface name for GigabitEthernet0/2) is used as a
failover
interface.
!Define Failover Interface
asa(config)#failover lan interface failover Ge0/2
!assign IP address on Failover Interface. MUST be in same Subnet as the standby on
the other unit.
asa(config)#failover interface ip failover 192.168.3.1 255.255.255.0 standby
192.168.3.2
In this documentation, the state (interface name for GigabitEthernet0/3) is used as
a state
interface.
!Define stateful Failover interface
asa(config)#failover link state Ge0/3
!assign IP address on Stateful Failover interface
asa(config)#failover interface ip state 192.168.4.1
192.168.4.2
255.255.255.0 standby
!Create Failover groups, where Failover group1 will be the Primary, i.e. active on
Primary Unit and Failover group2 will be the Standby on Primary Unit. Configure also
HTTP Replication, after which occurs HTTP Connection state replication between
active and Standby ASAs. Also determine Preempt Delay. Preempt Delay means in
what time to regain role of Active after Fail Recovery.
asa(config)#failover group 1
asa(config-fover-group)#primary
asa(config-fover-group)#preempt 120
asa(config-fover-group)# replication http
asa(config)#failover group 2
asa(config-fover-group)#secondary
asa(config-fover-group)#preempt 120
asa(config-fover-group)# replication http
Now lets start creating Contexts and assigning interfaces in each Context.
!Configure the admin context
asa(config)# admin-context admin
Recv Q:
Xmit Q:
0
0
49
7
90335543
2405585244