CCNP ENCOR lab 18 of 36

NAT and PAT at the internet edge

Publish a web server with static NAT and a port forward, give staff addresses from a public pool and put guests behind PAT, then read and clear the translation table like an operator.

Run this lab

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

In your workspace: Shared, then CCNP ENCOR 350-401 guided labs, then 18 - NAT and PAT at the internet edge

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
Intermediate
Time
About 60 minutes
Nodes need
5 vCPU, 3,584 MB
Smallest plan
Lite

The scenario

Fernhill Freight's Leeds edge router (R1) has three inside networks and one public block, 192.0.2.0/24, which the provider routes to R1's outside address. Right now nothing inside can reach the internet. The requirements:

  • The track-and-trace web server SRV1 must be reachable from the internet as 192.0.2.10 (all traffic) and also as 192.0.2.11 port 8080, for a partner whose firewall only allows outbound port 8080.
  • Staff (10.10.10.0/24) get addresses from the pool 192.0.2.32–192.0.2.47, one public address per user, so partner sites can whitelist them.
  • Guests (10.10.50.0/24) all share R1's outside address with PAT.
DeviceInterfaceAddressRole
R1Gi0/0203.0.113.2/30outside, to ISP 203.0.113.1
R1Gi0/1 / Gi0/2 / Gi0/310.10.10.1/24 / 10.10.50.1/24 / 10.10.30.1/24inside: staff / guests / servers
SRV1Gi0/010.10.30.10/24, gateway 10.10.30.1web server (ip http server)
PC1 / PC2eth010.10.10.10/24 / 10.10.50.10/24staff / guest
ISPLo0198.51.100.1/24an internet host

R1 has a default route to the ISP. Don't change the ISP router.

Topology: PC1, PC2 and SRV1 connect to R1; R1 Gi0/0 — ISP.

What you’ll practise

  • Use the four NAT address terms correctly and mark inside and outside interfaces
  • Configure static NAT and static PAT (port forwarding) for an internal server
  • Configure dynamic NAT from a pool and PAT overload on the outside interface
  • Verify, debug and clear translations, and explain NAT's order of operations

The tasks

  1. Mark the boundary
  2. Publish the web server with static NAT
  3. Add the partner port forward
  4. Give staff addresses from a pool
  5. Put guests behind PAT
  6. Operate NAT

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 NAT and PAT at the internet edge5 nodes, 4 links. Every link is listed as text below the diagram.R1ISPSRV1PC1PC2Gi0/3Gi0/0Gi0/1eth0Gi0/2eth0Gi0/0Gi0/0
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in NAT and PAT at the internet edge, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
ISPCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
SRV1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC2VPCS hostBuilt in to EVE-NGCounted as 1 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 CCNP ENCOR 350-401 guided labs.

  3. Open 18 - NAT and PAT at the internet edge 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 CCNP ENCOR labs

All CCNP ENCOR labs

Related labs in other courses

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