zNetLaB › Guided labs › Security
Troubleshoot: Palo Alto LAN that routes nowhere
Security Advanced 4 devices 1 checked tasks 100 points Plan lab
The rule from trust to untrust is there, OSPF with the router is up, and still the trust LAN cannot reach the far side. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
The rule from trust to untrust is there, OSPF with the router is up, and still the trust LAN cannot reach the far side.
Your role: a security engineer. Level: Advanced Done when: all 1 goals show as passed (100 points).
Network status
Devices: 2 routers, 2 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R1 starts with addresses (G0/0 10.2.0.1/24, G0/1 10.0.12.1/30) and static routes, OSPF 1 already configured. H1 is a host with 192.168.1.10/24, gateway 192.168.1.1. H2 is a host with 10.2.0.10/24, gateway 10.2.0.1. PA starts with an empty configuration.
Known problems
The network worked and now does not: the scenario above says what users report. The cause is a configuration fault, not a cable. Find it with show commands (interfaces, routes, neighbours, running-config) before you change anything; fix only what is wrong.
Goals
H1 reaches H2, and untrust still cannot open to H1 (100 pts)
The activity, in order
H1 reaches H2, and untrust still cannot open to H1 ethernet1/2 is not in virtual router default. Add it and commit.Why: Each goal is a state the lab can check on the running device. Verify with: show interface all
Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong.
Why this matters
The rule from trust to untrust is there, OSPF with the router is up, and still the trust LAN cannot reach the far side.
What you will be able to do
H1 reaches H2, and untrust still cannot open to H1
The network
ISR 2911, PA-VM, PC — 4 devices in all, already cabled.
Gi0/1 10.0.12.1/30 ethernet1/1 ethernet1/2 Fa0 Gi0/0 10.2.0.1/24 Fa0 R1 PA H1 192.168.1.10/24 · gw 192.168.1.1 H2 10.2.0.10/24 · gw 10.2.0.1 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
R1 ISR 2911 configure it
PA PA-VM configure it
H1 PC 192.168.1.10 / 255.255.255.0 gw 192.168.1.1
H2 PC 10.2.0.10 / 255.255.255.0 gw 10.2.0.1
Cabling
R1 Gi0/1 ↔ PA ethernet1/1
PA ethernet1/2 ↔ H1 Fa0
R1 Gi0/0 ↔ H2 Fa0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
R1 interface GigabitEthernet0/0
ip address 10.2.0.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/1
ip address 10.0.12.1 255.255.255.252
no shutdown
exit
ip route 192.168.1.0 255.255.255.0 10.0.12.2
router ospf 1
router-id 1.1.1.1
network 10.0.0.0 0.255.255.255 area 0
exit
PA configure
set network interface ethernet ethernet1/1 layer3 ip 10.0.12.2/30
set network interface ethernet ethernet1/2 layer3 ip 192.168.1.1/24
set zone untrust network layer3 ethernet1/1
set zone trust network layer3 ethernet1/2
set network virtual-router default interface ethernet1/1
set rulebase security rules allow-out from trust to untrust source any destination any application any service any action allow
set network virtual-router default protocol ospf enable yes
set network virtual-router default protocol ospf router-id 2.2.2.2
set network virtual-router default protocol ospf area 0.0.0.0 interface ethernet1/1 enable yes
commit
exit
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 H1 reaches H2, and untrust still cannot open to H1 100 On H1: ping 10.2.0.10 must succeed. and On H2: ping 192.168.1.10 must fail — the policy blocks it.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
PA configure
set network virtual-router default interface ethernet1/2
commit
exit
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.
Try the simulator in your browser, no sign-up