Firewalls and VPNs lab 5 of 16
PAN-OS to vSRX - IKE gateways crypto profiles and proxy IDs
Connect a Palo Alto Networks firewall to a Juniper vSRX with a route-based IKEv2 tunnel, then narrow the SRX to specific traffic selectors and match them on PAN-OS with a proxy ID, reading each vendor's own view of the SAs.
Run this lab
It needs Standard: its 5 nodes are set to 7 vCPU and 11,264 MB in total.
In your workspace: Shared, then Firewalls and VPNs multi-vendor guided labs, then 05 - PAN-OS to vSRX - IKE gateways crypto profiles and proxy IDs
- Level
- Advanced
- Time
- About 100 minutes
- Nodes need
- 7 vCPU, 11,264 MB
- Smallest plan
- Standard
The scenario
Larkfield Media's head office runs a Palo Alto Networks firewall. Its new recording studio has a Juniper SRX. Connect the two with IKEv2. Later in the lab, Larkfield's auditors ask that the tunnel carry only the two office subnets, not "anything routed into it", so you will narrow both ends to exact traffic selectors.
| Device | Interface | Address | Notes |
|---|---|---|---|
| ISP | Gi0/0 / Gi0/1 | 203.0.113.1/30 / 198.51.100.1/30 | |
| FW-HQ | ethernet1/1 untrust / ethernet1/2 trust | 203.0.113.2/30 / 10.1.0.1/24 | PAT for the HQ LAN |
| FW-HQ | tunnel.1 (zone vpn) | 172.16.5.1/30 | You create it |
| HQ-PC | Gi0/0 | 10.1.0.10/24 | |
| SRX-ST | ge-0/0/0 untrust / ge-0/0/1 trust | 198.51.100.2/30 / 10.2.0.1/24 | Source NAT trust to untrust |
| SRX-ST | st0.0 (zone vpn) | 172.16.5.2/30 | You create it |
| ST-PC | Gi0/0 | 10.2.0.10/24 |
| Setting | Value |
|---|---|
| IKE SA | IKEv2, AES-256-CBC, SHA-256, DH group 20, 8 hours, key Larkfield-27 |
| IPsec SA | ESP AES-256-CBC with SHA-256, PFS group 20, 1 hour |
| Selectors (Task 4) | 10.1.0.0/24 to and from 10.2.0.0/24 |
What you’ll practise
- Build PAN-OS IKE and IPsec crypto profiles, an IKE gateway, a tunnel interface and an IPsec tunnel
- Build the matching SRX IKE gateway and route-based VPN on st0
- Explain proxy IDs and traffic selectors, and why a route-based PAN-OS tunnel offers 0.0.0.0/0 by default
- Add SRX traffic selectors and the matching PAN-OS proxy ID
- Verify with show vpn ike-sa, show vpn ipsec-sa, show security ike security-associations and show security ipsec security-associations
The tasks
- Read the starting point
- PAN-OS side
- SRX side
- Narrow the selectors with a proxy ID
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 FW-HQethernet1/1 - ISP
Gi0/1to SRX-STge-0/0/0 - FW-HQ
ethernet1/2to HQ-PCGi0/0 - SRX-ST
ge-0/0/1to ST-PCGi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| ISP | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| FW-HQ | Palo Alto Networks VM-Series (PAN-OS) | paloalto-11.2.5 | 2 vCPU, 5,632 MB |
| HQ-PC | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| SRX-ST | Juniper vSRX NextGen template | vsrxng-23.4R2-S3.9 | 2 vCPU, 4,096 MB |
| ST-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
05 - PAN-OS to vSRX - IKE gateways crypto profiles and proxy IDsand 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.