Cisco ASA lab 6 of 15
Routing on the ASA: authenticated OSPF, dual ISPs and SLA-tracked default routes
Run OSPF with MD5 authentication between HQ-FW and the core router, add a second ISP, and make the default route fail over automatically when an SLA probe through ISP1 stops answering, with PAT on both ISP links.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 4,096 MB in total. That fits the free demo too.
In your workspace: Shared, then Cisco ASA Firewall SCOR 350-701 guided labs, then 06 - Routing on the ASA - authenticated OSPF dual ISPs and SLA-tracked default routes
- Level
- Intermediate
- Time
- About 75 minutes
- Nodes need
- 5 vCPU, 4,096 MB
- Smallest plan
- Lite
The scenario
Kestrel HQ has grown: a core router (CORE) now sits behind HQ-FW with the staff and server VLANs, and a second internet line from ISP2 has been installed on Gi0/2. Management wants:
- HQ-FW to learn the internal VLANs dynamically from CORE with OSPF area 0, authenticated with MD5 key 1
Kestrel-OSPF-26, and to give CORE its default route through OSPF. - ISP1 to stay the primary internet path, and ISP2 to take over automatically when ISP1 stops forwarding, even if HQ-FW's own link to ISP1 stays up.
- Internet access to work through both ISPs with interface PAT.
| Item | Value |
|---|---|
| Gi0/2 | name outside2, security level 0, 100.64.20.2/24, gateway 100.64.20.1 |
| OSPF | process 1, router ID 10.255.255.1, area 0 on 10.10.10.0/24 |
| SLA probe | ICMP echo to 198.18.1.2 (ISP1's upstream neighbour) out of outside, every 5 seconds |
What you’ll practise
- Configure OSPF on the ASA with MD5 authentication and originate a default route
- Add a second outside interface and a floating static default route
- Track reachability through ISP1 with an SLA monitor and a tracked static route
- Configure PAT on both ISP interfaces
- Test the failover and read show track, show route and show xlate
The tasks
- OSPF with CORE
- The default route for CORE
- The second ISP
- SLA-tracked primary, floating backup
- Test the failover
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-FW
Gi0/0to COREGi0/0 - HQ-FW
Gi0/1to ISP1Gi0/0 - HQ-FW
Gi0/2to ISP2Gi0/0 - ISP1
Gi0/1to NETGi0/0 - ISP2
Gi0/1to NETGi0/1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| HQ-FW | Cisco ASAv | asav-9.22.1.1-PLR-Licensed | 1 vCPU, 2,048 MB |
| CORE | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| ISP1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| ISP2 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| NET | 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
06 - Routing on the ASA - authenticated OSPF dual ISPs and SLA-tracked default routesand 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.