CloudLabBox
Try the free demo

Palo Alto NGFW lab 25 of 30

Troubleshooting: the VPN that stays down

The Leeds to York VPN was built over the weekend and has never passed a packet. Work through IKE, IPsec, routing, policy and NAT on both firewalls with the system log, the VPN test commands and the session table, and fix five faults so the depots can talk.

Run this lab

It needs Standard: its 4 nodes are set to 6 vCPU and 13,312 MB in total.

In your workspace: Shared, then Palo Alto NGFW PAN-OS 11 guided labs, then 25 - Troubleshooting - the VPN that stays down

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 6 vCPU and 13,312 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 60 minutes
Nodes need
6 vCPU, 13,312 MB
Smallest plan
Standard

The scenario

Over the weekend a colleague built the Leeds-York VPN from the change ticket, the same design you built in lab 19. On Monday nothing passes between the depots, and both firewalls commit cleanly. You have the change ticket (the amber note on the canvas) and console access to both firewalls.

There are five faults, spread across both sites and across:

  • phase 1;
  • authentication;
  • routing;
  • security policy;
  • NAT.

Find them in a logical order: each fault hides the next.

What you’ll practise

  • Read IKE and IPsec failures in the system log and the VPN show commands
  • Fix proposal, authentication, routing and policy faults on a route-based VPN
  • Recognise a NAT rule that captures VPN traffic and correct its scope
  • Verify the tunnel end to end from both sites

The Lab Tasks pane has the scenario, the 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.

Topology of Troubleshooting - the VPN that stays down4 nodes and 3 networks, 8 links. Every link is listed as text below the diagram.FW-LEEDSFW-YORKLeeds-PCYork-PCLeeds-LANInternetYork-LANmgmtethernet1/2mgmtethernet1/2eth0eth0ethernet1/1ethernet1/1
4 nodes and 3 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • FW-LEEDS mgmt to Leeds-LAN (network)
  • FW-LEEDS ethernet1/2 to Leeds-LAN (network)
  • FW-LEEDS ethernet1/1 to Internet (network)
  • FW-YORK mgmt to York-LAN (network)
  • FW-YORK ethernet1/2 to York-LAN (network)
  • FW-YORK ethernet1/1 to Internet (network)
  • Leeds-PC eth0 to Leeds-LAN (network)
  • York-PC eth0 to York-LAN (network)
Nodes in Troubleshooting: the VPN that stays down, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
FW-LEEDSPalo Alto Networks VM-Series (PAN-OS)paloalto-11.2.52 vCPU, 5,632 MB
FW-YORKPalo Alto Networks VM-Series (PAN-OS)paloalto-11.2.52 vCPU, 5,632 MB
Leeds-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
York-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Palo Alto NGFW PAN-OS 11 guided labs.

  3. Open 25 - Troubleshooting - the VPN that stays down and 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 Palo Alto NGFW labs

All Palo Alto NGFW labs

Related labs in other courses

CloudLabBox is independent of Palo Alto Networks and Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.