zNetLaB › Guided labs › Security
ASA: PAT, a static for the DMZ and the ACL that goes with it
Security Advanced 4 devices 4 checked tasks 100 points Plan lab
An ASAv with inside, outside and DMZ. The provider router knows nothing about your private addresses: give the inside users PAT on the outside interface, publish the DMZ server on 203.0.113.50 and let only ICMP reach it. 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
An ASAv with inside, outside and DMZ. The provider router knows nothing about your private addresses: give the inside users PAT on the outside interface, publish the DMZ server on 203.0.113.50 and let only ICMP reach it.
Your role: a security engineer. Level: Advanced Done when: all 4 goals show as passed (100 points).
Network status
Devices: 3 routers, 1 firewall, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. IN, FW, OUT, DMZ start with an empty configuration.
Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure.
Goals
The inside host reaches the provider (30 pts) The ASA shows the inside host translated (20 pts) The provider reaches the DMZ server on its public address (30 pts) show nat counts hits on the rules (20 pts)
The activity, in order
The inside host reaches the provider Name the three interfaces (inside 100, outside 0, dmz 50), add an object for 10.1.0.0/24 with nat (inside,outside) dynamic interface, a default route outside and inspect icmp in the global policy.Why: Each goal is a state the lab can check on the running device. Verify with: ping 203.0.113.9 The ASA shows the inside host translated After the ping the translation stays in the table for a while.Why: Each goal is a state the lab can check on the running device. Verify with: show xlate The provider reaches the DMZ server on its public address Object host 10.2.0.5 with nat (dmz,outside) static 203.0.113.50, and an outside ACL that permits icmp to the real address 10.2.0.5.Why: Each goal is a state the lab can check on the running device. Verify with: ping 203.0.113.50 show nat counts hits on the rules Both rules have been used once the two pings pass.Why: Each goal is a state the lab can check on the running device. Verify with: show nat
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
An ASAv with inside, outside and DMZ. The provider router knows nothing about your private addresses: give the inside users PAT on the outside interface, publish the DMZ server on 203.0.113.50 and let only ICMP reach it.
What you will be able to do
The inside host reaches the provider
The ASA shows the inside host translated
The provider reaches the DMZ server on its public address
show nat counts hits on the rules
The network
Catalyst 8000V, ASAv (simulated) — 4 devices in all, already cabled.
Gi1 Gi0/0 Gi0/1 Gi1 Gi0/2 Gi1 IN FW OUT DMZ Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
IN Catalyst 8000V configure it
FW ASAv (simulated) configure it
OUT Catalyst 8000V configure it
DMZ Catalyst 8000V configure it
Cabling
IN Gi1 ↔ FW Gi0/0
FW Gi0/1 ↔ OUT Gi1
FW Gi0/2 ↔ DMZ Gi1
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
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 The inside host reaches the provider 30 On IN: ping 203.0.113.9 must succeed.
2 The ASA shows the inside host translated 20 On FW: show xlate output matches 10\.1\.0\.5.
3 The provider reaches the DMZ server on its public address 30 On OUT: ping 203.0.113.50 must succeed.
4 show nat counts hits on the rules 20 On FW: show nat output matches translate_hits = [1-9].
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:
FW
interface GigabitEthernet0/0
nameif inside
security-level 100
ip address 10.1.0.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/1
nameif outside
security-level 0
ip address 203.0.113.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/2
nameif dmz
security-level 50
ip address 10.2.0.1 255.255.255.0
no shutdown
exit
object network LAN
subnet 10.1.0.0 255.255.255.0
nat (inside,outside) dynamic interface
exit
object network SRV
host 10.2.0.5
nat (dmz,outside) static 203.0.113.50
exit
policy-map global_policy
class inspection_default
inspect icmp
exit
exit
access-list O extended permit icmp any host 10.2.0.5
access-group O in interface outside
route outside 0.0.0.0 0.0.0.0 203.0.113.9
IN interface GigabitEthernet1
ip address 10.1.0.5 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 10.1.0.1
OUT interface GigabitEthernet1
ip address 203.0.113.9 255.255.255.0
no shutdown
exit
DMZ interface GigabitEthernet1
ip address 10.2.0.5 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 10.2.0.1
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