Firewalls and VPNs lab 13 of 16
Troubleshooting phase 1 across four vendors
An IOS hub has three IKEv2 spokes, an ASA, a FortiGate and a vSRX, and none of them comes up. Find the proposal, pre-shared key, IKE version and identity faults from each vendor's own IKE output and logs, fix each on the right device and bring all three tunnels up.
Run this lab
It needs Standard: its 7 nodes are set to 8 vCPU and 10,240 MB in total.
In your workspace: Shared, then Firewalls and VPNs multi-vendor guided labs, then 13 - Troubleshooting phase 1 across four vendors
- Level
- Advanced
- Time
- About 100 minutes
- Nodes need
- 8 vCPU, 10,240 MB
- Smallest plan
- Standard
The scenario
Corran Engineering has just cut over three sites to a new IOS hub. Each site is a different firewall (the result of three acquisitions), and the hub team wrote a standard for each tunnel. Nothing has come up. Four faults stand between you and three working tunnels, all of them in phase 1 (the IKE SA). Fix each one on the device that breaks the standard.
| Tunnel | Standard | Pre-shared key | Identities |
|---|---|---|---|
| HQ to A-FW | IKEv2, AES-256-GCM, PRF SHA-384, DH 20; crypto map 10.0.0.0/24 to 10.1.0.0/24 | Corran-A-27 | IP addresses |
| HQ to B-FW | IKEv2, DES with SHA-256, DH 14 (FortiGate evaluation limit); route-based | Corran-B-27 | IP addresses |
| HQ to C-SRX | IKEv2, AES-256-CBC, SHA-256, DH 20; route-based | Corran-C-27 | IP addresses |
| Device | Address | LAN |
|---|---|---|
| HQ | 203.0.113.2/30 (Tunnel2 169.254.13.1, Tunnel3 169.254.13.5) | 10.0.0.0/24 (Lo0) |
| A-FW | 198.51.100.2/30 | 10.1.0.0/24 (A-PC 10.1.0.10) |
| B-FW | 192.0.2.2/30 (to-HQ 169.254.13.2) | 10.2.0.0/24 (lo1 10.2.0.1) |
| C-SRX | 203.0.113.6/30 (st0.0 169.254.13.6) | 10.3.0.0/24 (C-PC 10.3.0.10) |
What you’ll practise
- Read IKE SA state on IOS, ASA, FortiGate and Junos
- Recognise NO_PROPOSAL_CHOSEN, AUTHENTICATION_FAILED, an IKE version mismatch and an identity mismatch from the evidence
- Use each vendor's IKE debug or log safely and turn it off again
- Decide which side to fix by comparing each device with the written standard
- Verify all tunnels from the hub
The tasks
- Survey the IKE state everywhere
- Site A
- Site B
- Site C (two faults)
- Prove all three
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
- ISP
Gi0/0to HQGi0/0 - ISP
Gi0/1to A-FWGi0/1 - ISP
Gi0/2to B-FWport1 - ISP
Gi0/3to C-SRXge-0/0/0 - A-FW
Gi0/0to A-PCGi0/0 - C-SRX
ge-0/0/1to C-PCGi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| ISP | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| HQ | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| A-FW | Cisco ASAv | asav-9.22.1.1-PLR-Licensed | 1 vCPU, 2,048 MB |
| A-PC | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| B-FW | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| C-SRX | Juniper vSRX NextGen template | vsrxng-23.4R2-S3.9 | 2 vCPU, 4,096 MB |
| C-PC | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 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
Firewalls and VPNs multi-vendor guided labs.Open
13 - Troubleshooting phase 1 across four vendorsand 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 Firewalls and VPNs labs
Related labs in other courses
CloudLabBox is independent of Check Point, Cisco, CompTIA, Fortinet, Juniper Networks, MikroTik, Netgate and Palo Alto Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.