Cisco ASA lab 11 of 15
High availability: Active/Standby failover with stateful replication
Pair HQ-FW with a second ASAv as an Active/Standby failover pair: standby addresses, a dedicated failover link and a stateful link, configuration replication, interface monitoring, a controlled failover and the commands to read the pair's health.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 5,120 MB in total. That fits the free demo too.
In your workspace: Shared, then Cisco ASA Firewall SCOR 350-701 guided labs, then 11 - High availability - Active-Standby failover with stateful replication
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 4 vCPU, 5,120 MB
- Smallest plan
- Lite
The scenario
HQ-FW (now called HQ-FW1) is a single point of failure. A second ASAv, HQ-FW2, has been racked and cabled exactly like it: Gi0/0 to the inside switch, Gi0/1 to the outside switch, and two direct cables, Gi0/2 for the failover link and Gi0/3 for the stateful link. HQ-FW2 is factory fresh apart from a temporary hostname. Make the two units an Active/Standby pair with HQ-FW1 as primary.
| Item | Value |
|---|---|
| inside | active 10.10.10.1, standby 10.10.10.2 |
| outside | active 203.0.113.2, standby 203.0.113.3 |
| Failover link | Gi0/2 named FOLINK, 172.16.255.1 (primary) / .2 (secondary), /30 |
| Stateful link | Gi0/3 named STATELINK, 172.16.254.1 / .2, /30 |
| Failover key | Kestrel-FO-26 (encrypts and authenticates failover messages) |
What you’ll practise
- Explain Active/Standby failover roles, the failover link and the stateful link
- Add standby addresses and configure LAN failover on the primary and secondary units
- Verify replication with show failover and failover exec mate
- Monitor interfaces and run a controlled failover, then fail back
The tasks
- Prepare the primary
- Failover on the primary
- Bootstrap the secondary
- Check the pair
- Fail over and fail back
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- HQ-FW1
Gi0/0to Inside-LAN (network) - HQ-FW2
Gi0/0to Inside-LAN (network) - PC1
Gi0/0to Inside-LAN (network) - HQ-FW1
Gi0/1to Outside-Net (network) - HQ-FW2
Gi0/1to Outside-Net (network) - ISP
Gi0/0to Outside-Net (network) - HQ-FW1
Gi0/2to HQ-FW2Gi0/2 - HQ-FW1
Gi0/3to HQ-FW2Gi0/3
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| HQ-FW1 | Cisco ASAv | asav-9.22.1.1-PLR-Licensed | 1 vCPU, 2,048 MB |
| HQ-FW2 | Cisco ASAv | asav-9.22.1.1-PLR-Licensed | 1 vCPU, 2,048 MB |
| PC1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| ISP | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Cisco ASA Firewall SCOR 350-701 guided labs.Open
11 - High availability - Active-Standby failover with stateful replicationand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More Cisco ASA labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.