CloudLabBox
Try the free demo

Palo Alto NGFW lab 24 of 30

Troubleshooting: the broken branch firewall

A contractor configured the Wakefield depot firewall and left. Nothing works. Work through four user tickets with the troubleshooting method from lab 23 and find the six faults hidden in the configuration: in the management profile, routing, the virtual router, a mis-scoped deny rule, a wrong service and a NAT translation.

Run this lab

It needs Lite: its 4 nodes are set to 5 vCPU and 7,680 MB in total. That fits the free demo too.

In your workspace: Shared, then Palo Alto NGFW PAN-OS 11 guided labs, then 24 - Troubleshooting - the broken branch firewall

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 60 minutes
Nodes need
5 vCPU, 7,680 MB
Smallest plan
Lite

The scenario

The Wakefield depot firewall was configured by a contractor who has since left. It commits without errors, but the depot is down. The intended design is the same as Leeds:

ZoneInterfaceAddressHosts
Outsideethernet1/1203.0.113.2/24ISP gateway 203.0.113.1, test sites 198.51.100.0/24
Insideethernet1/210.1.1.1/24 (answers ping)Client-PC 10.1.1.10, management 10.1.1.254
DMZethernet1/3172.16.1.1/24web01 172.16.1.10 (HTTP and HTTPS)

The policy should be:

  • depot users browse the internet with PAT on 203.0.113.2;
  • depot users reach the intranet on web01 (web, HTTPS, ping);
  • guest Wi-Fi (10.1.99.0/24) is blocked from the internet.

Four tickets are open:

  1. "Monitoring says the depot gateway 10.1.1.1 is down."
  2. "The intranet (http://172.16.1.10) is unreachable."
  3. "Nobody can browse the internet."
  4. "Whatever you change, guest Wi-Fi must stay blocked."

There are six faults. Find each one, fix it with the smallest correct change, and keep a note of the evidence. Logins: FW1 admin / Lab-Access-1 (console or https://10.1.1.254).

What you’ll practise

  • Work a structured troubleshooting method from symptom to root cause
  • Find interface, routing, NAT and policy faults with show, test, counters and logs
  • Fix each fault with the smallest correct change
  • Prove the fix and confirm nothing else broke

The tasks

  1. Ticket 1, the gateway doesn't answer ping
  2. Ticket 2, the intranet is unreachable
  3. Ticket 3, no internet
  4. Ticket 4, keep the guests out
  5. Write it up

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.

Topology of Troubleshooting - the broken branch firewall4 nodes and 3 networks, 7 links. Every link is listed as text below the diagram.FW1Client-PCweb01InternetInsideOutsideDMZeth0ethernet1/3eth0mgmtethernet1/2eth0ethernet1/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
  • FW1 mgmt to Inside (network)
  • FW1 ethernet1/1 to Outside (network)
  • FW1 ethernet1/2 to Inside (network)
  • FW1 ethernet1/3 to DMZ (network)
  • Client-PC eth0 to Inside (network)
  • web01 eth0 to DMZ (network)
  • Internet eth0 to Outside (network)
Nodes in Troubleshooting: the broken branch firewall, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
FW1Palo Alto Networks VM-Series (PAN-OS)paloalto-11.2.52 vCPU, 5,632 MB
Client-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
web01EVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 512 MB
InternetEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 512 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 24 - Troubleshooting - the broken branch firewall 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.